Skip to main content
Glama
Citrus086

mcporter-bridge

by Citrus086
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcporter-bridge

No user-submitted related servers found.

    Related Servers

    • MCP Hub

      Cai-Chang
      F
      license
      Not graded
      quality
      D
      maintenance
      Aggregates multiple MCP servers into a single standard MCP interface for agents like Claude Code, with automatic tool prefixing and hot-reload.
      2
      -

    • mcpreg

      prasad-a-abhishek
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables introspection of any MCP server's registered tools by exposing mcpreg/list, mcpreg/get, and mcpreg/query tools, making tool registry accessible even when the underlying SDK lacks list_tools().
      MIT

    • Magg

      louiseriksson239
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables LLMs and clients to discover, add, configure, enable or disable, and aggregate tools from multiple MCP servers under unified prefixes. It also proxies other MCP servers and persists configurations across sessions.
      -

    • mcp-router-local

      codespriha
      A
      license
      Not graded
      quality
      C
      maintenance
      Aggregates multiple MCP servers behind a single local endpoint, letting LLM clients connect to one router that exposes a unified set of tools, resources, and prompts.
      6 npm
      MIT

    • codex-connectors-mcp

      wileai
      A
      license
      Not graded
      quality
      A
      maintenance
      Bridges authenticated Codex connector apps into any MCP-compatible harness over stdio or Streamable HTTP, exposing connector tools for listing, schema inspection, and calling without a Codex model turn or API key.
      14 npm
      5
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool maps to a distinct phase of the MCP lifecycle: listing, exploring, calling, status checking, and activation/deactivation. There is no functional overlap between them, making selection unambiguous.

    Naming Consistency4/5

    All tools share the mcporter_ prefix and most follow a verb_noun pattern (list_servers, call_tool, activate_mcp, deactivate_mcp). However, 'help' and 'status' are single verbs/nouns that deviate slightly from the pattern.

    Tool Count5/5

    Six tools is an ideal number for a bridge server, covering the full management lifecycle without unnecessary bloat. Each tool has a clear and necessary role.

    Completeness5/5

    The tool set provides a complete workflow: discover available MCPs, activate large ones on demand, inspect tool schemas, call tools, and deactivate to free context. Status diagnostics round out the surface, so no critical operations are missing.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources