Skip to main content
Glama
deadSwank001

Nexus-MCP

by deadSwank001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Nexus-MCP

No user-submitted related servers found.

    Related Servers

    • mcp-ollama-python

      pblagoje
      A
      license
      Not graded
      quality
      A
      maintenance
      A Python MCP server that exposes local Ollama models as tools for AI assistants, enabling chat, generation, embeddings, and model management without cloud APIs.
      49 PyPI
      5
      MIT
    • Local AI MCP by TMHSDigital

      Local AI MCPofficial

      TMHSDigital
      A
      license
      A
      quality
      A
      maintenance
      Unified MCP server for managing local model runtimes (Ollama, LM Studio, etc.), enabling provider-agnostic discovery, lifecycle management, hardware-fit checks, and delegated inference.
      16
      46 npm
      Creative Commons Attribution Non Commercial No Derivatives 4.0 International

    • 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

    • mcplex

      dbhavery
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server that bridges local Ollama models and ChromaDB vector memory to MCP clients like Claude Code. It enables local text generation, vision-based image analysis, and semantic memory storage without requiring external API keys.
      MIT

    • Ollama MCP Server

      m-mehdi14
      A
      license
      B
      quality
      D
      maintenance
      A universal MCP server that integrates with local Ollama instances, enabling AI-powered chat, model management, and text generation from any MCP-compatible IDE or application.
      6
      73 npm
      3
      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 16 tools

    Disambiguation5/5

    Each tool targets a distinct operation: model management, knowledge indexing, evaluation, or generation. Overlap between 'chat', 'generate', and 'compare_models' is minimal and disambiguated by descriptions.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (e.g., 'create_index', 'list_models'), but a few use single verbs ('chat', 'generate') or noun_verb ('health_check'). The pattern is mostly consistent and readable.

    Tool Count4/5

    With 16 tools covering models, knowledge bases, evaluation, and chat, the count is appropriate for a multi-purpose MCP server. It is slightly on the higher side but still well-scoped.

    Completeness4/5

    The tool surface covers model lifecycle, generation, knowledge index management, and evaluation. Missing features include individual document removal and document listing within indexes, but core workflows are complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources