@mcplookup-org/mcp-server

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

@MCPLookup-org

Repository

About @mcplookup-org/mcp-server

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

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

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

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

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

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.

What transports and modes are available?

The bridge can run in stdio mode (as an MCP server) or as an HTTP server (with --http and optional port).

Comments

More Other MCP servers

🚀 Model Context Protocol (MCP) Curriculum for Beginners

microsoft

This open-source curriculum introduces the fundamentals of Model Context Protocol (MCP) through real-world, cross-language examples in .NET, Java, TypeScript, JavaScript, Rust and Python. Designed for developers, it focuses on practical techniques for building modular, scalable,

16.7K