Skip to main content
Glama

Related Servers

Alternatives to mcp-llm-bridge

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      One local gateway for all your MCP servers — shared by every AI coding tool (Claude, Cursor, VS Code, Codex). Set up each server once; keys stay in the OS keychain; lazy discovery keeps agent context small. Local-first, open source.
      4
      0
      233
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Open-source MCP and LLM gateway that aggregates MCP tools behind a unified endpoint with governance, observability, and explicit execution controls.
      9,123
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes an OpenAI- and Anthropic-compatible HTTP, SSE, and stdio gateway that wraps multiple subscription CLIs, adding prompt-injection defense, PII redaction, cost-aware routing, and reasoning-trace capture for MCP-compatible clients like Claude Desktop and Cursor.
      19 npm
      16
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      An encrypted secret vault and MCP gateway that securely stores API keys and injects them into upstream MCP servers, so AI IDEs never see raw credentials.
      10
      AGPL 3.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Unified local MCP AI Gateway that routes across Groq, OpenRouter, Mistral, and local Ollama providers, with OpenAI-compatible APIs, MCP tools, fallback/racing router, monitoring, and web dashboard.
      -
    • F
      license
      Not graded
      quality
      C
      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.
      9 npm
      1,199
      -

    TDQS

    A3.6/5.0

    Scored across 30 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose due to domain-specific prefixes and action verbs. Overlaps like llm_generate and local_llm_generate are well-differentiated by descriptions indicating local vs. cloud routing.

    Naming Consistency5/5

    All tools follow a consistent snake_case pattern with a domain prefix (e.g., vault_, conversation_) followed by a verb_noun combination. No mixing of conventions or ambiguous names.

    Tool Count4/5

    30 tools is on the higher side but each domain (approval, circuit breakers, code search, conversation, groups, LLM generation, shared state, usage, vault) has a reasonable number of tools. The count reflects the server's broad scope without excessive bloat.

    Completeness4/5

    Most domains have adequate CRUD coverage (e.g., vault store/list/delete, conversation pagination, usage query/summary). Minor gaps exist (no group update, no approval request creation), but core workflows are supported.

    Maintenance

    ActivitySlowing
    ResponsivenessSlow