Skip to main content
Glama
Sign In
MCP Ollama Consult Server

MCP Ollama Consult Server

by Atomic-Germ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Related Servers

Alternatives to MCP Ollama Consult Server

No user-submitted related servers found.

    Related Servers

    • Ollama MCP Server

      rawveg
      A
      license
      A
      quality
      D
      maintenance
      Enables seamless integration between Ollama's local LLM models and MCP-compatible applications, supporting model management and chat interactions.
      13
      882 npm
      176
      AGPL 3.0

    • Ollama MCP Server

      wisniewski880
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible clients to access local or cloud LLMs, manage and run models, generate completions and embeddings, chat with tool/function support, and use web search/fetch through Ollama Cloud.
      882 npm
      AGPL 3.0

    • localmodels

      CloudCorpRecords
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a locally running Ollama server over MCP so clients can list, pull, inspect, copy, and delete models, then generate completions, chat, and create embeddings without any API key or hosted account.
      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

    B3.4/5.0

    Scored across 5 tools

    Disambiguation3/5

    The purposes of list_ollama_models and remember_context are distinct, but consult_ollama, compare_ollama_responses, and sequential_consultation_chain heavily overlap. All three involve querying models, differing mainly in whether responses are combined or chained, which could lead to agent confusion.

    Naming Consistency3/5

    Tools mostly follow a snake_case verb_noun pattern (list_ollama_models, remember_context, compare_ollama_responses), but 'sequential_consultation_chain' breaks the verb-first pattern with an adjective-noun structure. Also, 'consult_ollama' is a general verb that overlaps with others, making the naming less distinctive.

    Tool Count5/5

    With only 5 tools, the server is well-scoped and each tool seems to have its place, though the overlap among core consultation tools slightly reduces the necessity of having three separate ones. Still, it's a small, manageable set that fits the server's purpose.

    Completeness4/5

    The server covers a typical consultation workflow: listing available models, querying them, comparing responses, chaining consultations, and maintaining context. A minor gap is the lack of a tool to explicitly clear context or manage sessions, which agents might need for long-running interactions.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources