Skip to main content
Glama

Related Servers

Alternatives to Toolport

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      A local AI gateway that connects multiple AI providers (ChatGPT, Claude, Gemini, Perplexity) to your development environment via MCP tools, enabling coding, search, analysis, and more without API keys.
      50 npm
      1,173
      -
    • A
      license
      A
      quality
      C
      maintenance
      One MCP that turns Claude Code into your whole dev stack by swallowing other MCP servers, delegating to Codex & Gemini on your CLI subscriptions, remembering projects in a searchable knowledge graph, and carrying setup across sessions — secret-free by design.
      23
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Unifies local MCP servers into a single secure Cloudflare Tunnel endpoint, making them accessible to MCP clients like Notion and Claude. Supports HTTP/SSE/stdio servers, built-in file system tools, bearer authentication, and one-click Windows setup.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Centralized encrypted gateway that routes requests to 11+ LLM providers (API keys and CLI subscriptions) through a single OpenAI-compatible endpoint, with MCP tools for vault operations, code search, and shared state.
      30
      17 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that connects AI coding agents (Claude Code, Codex, Cursor, etc.) on the same machine via a shared message bus, enabling them to chat, delegate tasks, and collaborate privately without cloud or internet.
      54 npm
      18
      MIT

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: status reports server state, search_tools discovers tools, call_tool invokes them, and fetch_result pages through truncated results. There is no meaningful overlap between any two tools.

    Naming Consistency4/5

    All tools share the consistent toolport_ prefix and most follow a verb_noun pattern (search_tools, call_tool, fetch_result). toolport_status is slightly less consistent because it uses a noun without an explicit action verb, but the pattern remains predictable.

    Tool Count5/5

    Four tools is a well-scoped size for a gateway/meta-server: discovery, invocation, result pagination, and status reporting each earn their place. The set is neither bloated nor thin for its purpose.

    Completeness5/5

    The tool set covers the full lifecycle of using a unified MCP gateway: finding tools, invoking them, retrieving large results, and checking server status. There are no obvious dead ends or missing operations for the stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessResponsive