Skip to main content
Glama
zihin-ai

Zihin MCP Server

by zihin-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Zihin MCP Server

No user-submitted related servers found.

    Related Servers

    • OpenAPI to Model Context

      gujord
      A
      license
      Not graded
      quality
      D
      maintenance
      A proxy server that bridges AI agents and external APIs by dynamically translating OpenAPI specifications into standardized MCP tools, enabling seamless interaction without custom integration code.
      69
      MIT

    • MCPHub

      Jayden-Dong
      F
      license
      Not graded
      quality
      D
      maintenance
      A centralized management platform that aggregates multiple Model Context Protocol (MCP) servers into a single unified endpoint for AI agents. It provides a web interface for hot-swappable tool management, proxying of existing servers, and AI-powered generation of custom MCP plugins.
      1
      -

    • mcp-gateway

      lasso-security
      A
      license
      Not graded
      quality
      D
      maintenance
      Acts as an intermediary between LLMs and other MCP servers, centralizing management, sanitizing sensitive information, and providing a unified interface for discovering and interacting with proxied MCPs.
      385
      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

    • agentforge

      doggychip
      F
      license
      A
      quality
      F
      maintenance
      MCP server that exposes 300+ AI agents as tools via a single API key. Supports listing agents, invoking any agent with chat-completion style messages, checking agent health, and retrieving platform statistics.
      5
      3
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 96 tools

    Disambiguation4/5

    With 96 tools, there is potential for confusion, but the tool names and descriptions clearly separate resources (agents, triggers, schemas, connections, secrets, MCP servers, etc.). Some pairs like get_agent vs get_agent_full serve different depths, and descriptions clarify usage. Overall, each tool has a distinct purpose with only minor overlaps (e.g., test_connection vs test_mcp_server), but the volume makes selection slightly harder.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., list_agents, create_agent, update_agent, delete_agent). Even exceptions like whoami and chat_with_agent are clear and fit the pattern. There are no mixed conventions or chaotic naming.

    Tool Count1/5

    96 tools is far beyond the typical range for an MCP server, even for a full platform admin. The sheer volume creates cognitive overhead for agents and increases misselection risk. While the domain is broad, this count is excessive and would benefit from consolidation or namespacing.

    Completeness5/5

    The tool surface is exceptionally complete, covering CRUD and lifecycle operations for agents, schemas, triggers, connections, secrets, MCP servers, CSPs, API keys, and more. It includes diagnostics, validation, versioning, snapshots, approvals, budgets, and consumer management. No obvious gaps are apparent for the stated purpose of full tenant management.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources