Skip to main content
Glama
AIOCANA

@aiorouter/mcp

by AIOCANA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @aiorouter/mcp

No user-submitted related servers found.

    Related Servers

    • Outsource MCP

      gwbischof
      A
      license
      A
      quality
      D
      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

    • Model Hub MCP

      akiojin
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that retrieves and provides AI model information from OpenAI, Anthropic, and Google through a unified interface.
      3
      22 npm
      MIT

    • nvidia-mcp

      holm-digital-io
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that provides AI agents free access to NVIDIA's hosted AI models (100+ models) with automatic model routing for tasks like reasoning, coding, vision, embeddings, and translation.
      10
      2
      MIT

    • LLM Radar

      ajentsor
      A
      license
      A
      quality
      F
      maintenance
      MCP server that provides AI assistants with real-time, current information about AI models from OpenAI, Anthropic, and Google, including pricing, capabilities, and context windows.
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: chat, model listing, model details, comparison, pricing, cost estimation, usage, connection test, config export, and presets. While list_models and get_model_info both relate to models, the former enumerates models while the latter provides detailed info for a single model, making the distinction clear. The descriptions reinforce these boundaries.

    Naming Consistency5/5

    All tools follow a consistent aiorouter_ prefix with a verb_noun pattern: chat, list_models, get_usage, get_pricing, export_config, compare_models, etc. Naming is uniform, snake_case, and verbs align with the operation. No mixed conventions or vague verbs like 'do_thing'.

    Tool Count5/5

    With 10 tools, the server is well-scoped for an AI router service. Each tool earns its place by covering distinct user needs: interaction, exploration, cost management, and configuration. This is within the ideal 3-15 range and neither feels sparse nor overwhelming.

    Completeness5/5

    The surface covers the core domain comprehensively: chat completions, model discovery (list, get, compare), pricing and cost estimation, account usage, connection validation, and configuration export. No obvious dead ends or missing essential operations for the stated purpose of interacting with AIOrouter. The only noted limitation (non-streaming) is a technical constraint, not a tool gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources