Zihin MCP Server
Related Servers
Alternatives to Zihin MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA 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.69MIT
- FlicenseNot gradedqualityDmaintenanceA 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-
- AlicenseNot gradedqualityDmaintenanceActs 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.397MIT
- AlicenseNot gradedqualityDmaintenanceA 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.1MIT
- AlicenseNot gradedqualityBmaintenanceThis MCP server enables agents to administer a self-hosted AI control plane for users, organizations, subscriptions, API keys, model providers, and service health, with local-first model routing and cloud failover.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA proxy server that unifies multiple MCP servers, enabling seamless tool, prompt, and resource management via the MetaMCP App.69 npm155Apache 2.0
TDQS
Scored across 88 tools
Most tools target clearly distinct resources and actions, and the descriptions explicitly cross-reference siblings (e.g., get_agent vs get_agent_full, get_tenant_health vs get_agent_metrics, session-related tools). Some clusters like set_session_control/set_engagement_control/set_consumer_denylist and the four session-inspection tools (list_agent_sessions, list_consumer_sessions, get_session_history, get_session_agent_tree) risk misselection, but the descriptions disambiguate reasonably well.
Overwhelmingly consistent snake_case verb_noun pattern (list_/get_/create_/update_/delete_/toggle_/set_/validate_/test_/rollback_/compare_). The only notable deviation is 'whoami', which breaks the verb_noun convention, but it is a single outlier in an otherwise uniform scheme.
88 tools is very heavy and well past the threshold where an agent can reliably scan and select; even with a genuinely broad platform domain, the surface is over-large. Many CRUD families (agents, schemas, triggers, csp, secrets, mcp servers, api keys, approval policies, budgets, versions, snapshots, sessions) inflate the set.
Coverage is remarkably full: CRUD for agents, schemas, triggers, CSPs, secrets, MCP servers, API keys, approval policies, budgets, plus metrics, versions, snapshots and session inspection. Minor gaps exist, e.g. there is list/delete for agent memory but no explicit create/update memory tool, and no consumer update/delete.