@mcplookup-org/mcp-server

Name: @mcplookup-org/mcp-server
Author: MCPLookup-org

@MCPLookup-org

代码仓库

关于 @mcplookup-org/mcp-server

MCP Bridge Server - Universal MCP client with dynamic discovery and tool management

#mcp-server #mcp-bridge #dynamic-discovery

基本信息

分类

其他

运行时

node

传输方式

stdio

发布者

MCPLookup-org

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "gmail": {
      "command": "node",
      "args": [
        "gmail-server"
      ]
    },
    "github": {
      "command": "node",
      "args": [
        "github-server"
      ]
    },
    "slack": {
      "command": "node",
      "args": [
        "slack-server"
      ]
    }
  }
}

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is @mcplookup-org/mcp-server?

The MCP Bridge Server is a universal MCP client that provides dynamic discovery and management of other MCP servers. It eliminates hardcoded server lists, allowing AI agents to discover and connect to any MCP server in real-time through a single bridge.

How to use @mcplookup-org/mcp-server?

Install globally via npm install -g @mcplookup-org/mcp-server, set the required environment variable MCPLOOKUP_API_KEY (get yours from mcplookup.org/dashboard), and run as a stdio server with mcp-bridge or as an HTTP server with mcp-bridge --http --port <port>. Integrate with Claude Desktop by adding an entry to mcpServers configuration with the command mcp-bridge.

Key features of @mcplookup-org/mcp-server

Dynamic server discovery with natural language search.
Install and manage MCP servers locally or in Docker.
Invoke tools from any discovered or managed server.
Real‑time health monitoring and auto‑recovery.
Docker isolation with resource limits and security hardening.
Connection pooling, response caching, and lazy loading.

Use cases of @mcplookup-org/mcp-server

AI agents dynamically finding and calling tools from multiple MCP servers.
Replacing hardcoded mcpServers lists with a single universal bridge.
Securely running third‑party MCP servers in isolated containers.
Monitoring and managing the lifecycle of many servers from one interface.

FAQ from @mcplookup-org/mcp-server

What is the main benefit over hardcoded MCP server lists?

Instead of manually adding every server to the client configuration, one universal bridge entry gives dynamic access to all registered MCP servers via the MCPLookup registry.

What runtime or dependencies are required?

Node.js with TypeScript 5.8+ is required. Docker installation is optional but recommended for server isolation.

Where does server discovery data come from?

Discovery queries use the MCPLookup.org API (default https://mcplookup.org/api/v1). An API key is required.

Does the bridge support authentication or environment injection?

Yes, container environments support safe injection of variables, and the bridge automatically escapes and validates sensitive credentials. Bridge credentials are never exposed to managed servers.