Skip to main content
Glama
Sign In
bdbais

io.github.bdbais/routeai

by bdbais
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to io.github.bdbais/routeai

No user-submitted related servers found.

    Related Servers

    • Ollama MCP Server

      Jadael
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to delegate coding tasks to local Ollama models, reducing API token usage by up to 98.75% while leveraging local compute resources. Supports code generation, review, refactoring, and file analysis with Claude providing oversight and quality assurance.
      449 npm
      26
      AGPL 3.0

    • Nanites

      ADn-001
      A
      license
      B
      quality
      B
      maintenance
      Enables Claude Code and Claude Desktop to delegate bounded, disposable tasks to local or cheap cloud models, with model scoring, guardrails, and cost-saved tracking.
      53
      MIT

    • claude-token-saver-mcp

      BlackFoil
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code to offload routine code generation and text processing tasks to a local Ollama LLM, saving Cloud API tokens and costs with automatic model selection and security features.
      11
      281 npm
      3
      Apache 2.0

    • Houtini LM

      NiklasNunes6682
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code and other MCP clients to offload bounded work — code review, boilerplate, commit messages, format conversion, embeddings — to a local or cloud OpenAI-compatible LLM, cutting token spend by keeping large files out of the orchestrator's context. It also provides a second model for reviewing code and drafting tasks while the main assistant retains planning and QA.
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 11 tools

    Disambiguation4/5

    Each tool has a mostly distinct purpose, with action and resource clearly separated. The main overlaps are fleet_status vs fleet_usage on usage/savings metrics and fleet_job vs fleet_queue on background work status, but the descriptions clarify the boundaries.

    Naming Consistency5/5

    All tools share the fleet_ prefix and use lowercase snake_case throughout. The verb/noun suffixes are intuitively matched to each operation, making the naming pattern highly predictable.

    Tool Count5/5

    With 11 tools, the set is well-scoped and covers the fleet lifecycle without redundancy or bloat. Each tool has a clear role, and the count is comfortably within the ideal range.

    Completeness4/5

    The core workflow is well covered: set up the fleet, manage nodes, delegate single/batch tasks, queue work, monitor jobs, provide feedback, benchmark, and track usage. Minor gaps include no way to cancel a running background job or remove a pulled model.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources