Skip to main content
Glama
irad-bouzidi

mcp-ollama-account-rotation

by irad-bouzidi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to mcp-ollama-account-rotation

No user-submitted related servers found.

    Related Servers

    • mcp-ollama-account-rotation

      irad-bouzidi
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that routes Ollama Cloud API requests across multiple user-owned accounts with automatic rotation to handle quota exhaustion, rate limits, and failures.
      -

    • Multi-LLM Gateway MCP

      tgosoul2019
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that functions as an intelligent gateway for multiple LLM backends including OpenAI, Claude, and Ollama. It supports automatic provider fallback, streaming responses via Server-Sent Events, and real-time monitoring for robust AI integration.
      MIT

    • Multi-Provider LLM MCP Server

      itachiuchihadev
      F
      license
      A
      quality
      B
      maintenance
      Unified MCP server for querying multiple LLM providers (Gemini, OpenAI, Anthropic, etc.) with advanced routing, cost optimization, and fallback resilience.
      2
      3 npm
      -

    • proxyllm-mcp

      proxyllm-ai
      A
      license
      A
      quality
      D
      maintenance
      MCP server for ProxyLLM, the OpenAI-compatible LLM gateway, enabling live model catalogs, plan-savings calculations, routing key management, and autonomous account signup.
      9
      60 npm
      MIT

    • Ollama MCP Proxy

      apn-ra
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP proxy server that bridges MCP clients with Ollama local language models, providing advanced features like RAG integration, context management, caching, and production-ready security.
      1
      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

    C2.4/5.0

    Scored across 5 tools

    Disambiguation2/5

    'chat' and 'generate' both involve text generation with overlapping functionality, making them hard to distinguish without additional context. The account-related tools (get_account_status, get_metrics) are distinct but mixed with unrelated generation tools, causing ambiguity about the server's core purpose.

    Naming Consistency2/5

    Tool names use inconsistent patterns: 'chat' and 'generate' are single verbs, while 'list_models', 'get_account_status', and 'get_metrics' follow snake_case verb_noun. Mixing styles reduces predictability.

    Tool Count3/5

    Five tools is a reasonable number, but the scope is muddled: only two tools (get_account_status, get_metrics) relate to the server's stated 'account rotation' purpose, while the others provide generic Ollama functionality, making the count feel imbalanced.

    Completeness2/5

    For an account rotation server, essential operations like switching accounts, listing accounts, or rotating keys are missing. The existing account tools are limited to status and metrics, leaving significant gaps that would hinder automation.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources