Skip to main content
Glama
libragik

universal-ai-agent-bridge

by libragik

Related Servers

Alternatives to universal-ai-agent-bridge

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables agents to dynamically switch between multiple AI models (OpenAI, Anthropic, Google, etc.) with unified protocol-driven configuration and capability discovery.
      Apache 2.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Exposes an MCP interface that lets agents route chat requests across a pooled catalog of free LLM provider routes through a single OpenAI-compatible endpoint, with automatic failover, usage tracking, and keyless start when an enabled route is available. It also lets clients query live capacity and provider health, capacity status, and available models without leaving the agent workflow.
      -
    • F
      license
      A
      quality
      D
      maintenance
      Unified MCP server for querying multiple LLM providers (Gemini, OpenAI, Anthropic, etc.) with advanced routing, cost optimization, and fallback resilience.
      2
      22 npm
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to discover, evaluate, and serve task-specialist models (embeddings, reranking, classification, extraction) with OpenAI-compatible endpoints and MCP tools for routing, embedding, reranking, and extraction.
      -
    • A
      license
      A
      quality
      F
      maintenance
      An MCP server that enables AI applications to access 20+ model providers (including OpenAI, Anthropic, Google) through a unified interface for text and image generation.
      2
      30
      MIT

    TDQS

    A3.5/5.0

    Scored across 13 tools

    Disambiguation3/5

    Most tools have clear purposes, but llm_query, llm_list_models, and llm_test_connection could be confused - a user might call query when they only want to list models, or test_connection when checking availability. llm_generate_video and llm_generate_image are distinct by media type, but llm_compare, llm_council, and llm_query all involve sending prompts to multiple models, though their outputs differ significantly.

    Naming Consistency4/5

    All tools follow a consistent 'llm_' prefix with descriptive verb_noun naming (generate_video, list_models, test_connection, manage_providers). Minor inconsistency: 'llm_autodetect' is a verb alone without an object, and 'llm_cache' is a noun-only name rather than a verb_noun pair, but overall the pattern is predictable and readable.

    Tool Count5/5

    13 tools is well within the ideal range for a domain-focused server. The tools cover distinct operational areas: querying, generation, model management, caching, analytics, and multi-model orchestration, each earning its place without unnecessary duplication.

    Completeness4/5

    The surface covers core LLM operations: querying, listing models, testing connections, managing providers, generating content, comparing models, and caching. Missing operations like streaming responses, stopping/canceling ongoing requests, or batch processing are minor gaps for a local dev tool, but the main workflows are complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues