F
licenseA
qualityF
maintenanceMCP 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
-
lyzr-mcp
by nandanNM
Related Servers
Alternatives to lyzr-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for the LiteLLM proxy, enabling agents to administer resources like keys, teams, users, models, and proxy settings through risk-graded meta-tools.6MIT
- FlicenseNot gradedqualityFmaintenanceA production-ready MCP server built with FastAPI, providing an enhanced tool registry for creating, managing, and documenting AI tools for Large Language Models (LLMs).34-
- AlicenseNot gradedqualityDmaintenanceMCP server that provides tools to interact with the LiteLLM proxy API, enabling LLM completions, embeddings, image generation, and admin operations.11 npmMIT
- AlicenseBqualityAmaintenanceMCP server that exposes any LynxPrompt instance to LLMs, enabling browsing, searching, and managing AI configuration blueprints and prompt hierarchies.647 npm2GPL 3.0
Agorus MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceMCP server for the Agorus AI agent marketplace, exposing API operations as tools for LLMs to discover, contract, and interact with agents and services.4 npmMIT
TDQS
C2.9/5.0
Scored across 423 tools
Disambiguation1/5
There are numerous near-identical clusters (e.g., lyzr_kg_train_text vs lyzr_kg_ext_train_text_neo4j, session_create/session_create_for_agent/session3_create, and multiple session history variants) whose boundaries are unclear from names alone. The 423-tool surface forces agents to choose between duplicates, v3/ext/task/internal variants, and deprecated endpoints with overlapping purposes.
Naming Consistency2/5
All tools share the lyzr_ prefix and snake_case, but the verb/noun ordering is inconsistent: lyzr_create_agent, lyzr_kb_create, lyzr_session_create, lyzr_agent_create_single_task, and lyzr_report_usage_by_model all use different constructions. There are also bare nouns like lyzr_agent_sessions and single verbs like lyzr_extract, so no reliable naming pattern predicts a tool's role.
Tool Count1/5
423 tools is an extreme count for an MCP server, far beyond the 3-15 well-scoped range and even beyond the 25+ threshold. Even if the underlying platform is broad, exposing this much surface destroys navigability and makes correct tool selection impractical.
Completeness5/5
The tool surface provides thorough CRUD and lifecycle coverage for agents, sessions, knowledge bases, credentials, workflows, git repos, world models, A2A agents, sharing, reports, and more, including async task variants and status polling. There are no obvious dead ends; most resources have create/read/update/delete plus operational triggers.
Maintenance
ActivitySlowing
ResponsivenessNo issues