Lerian MCP Server
Related Servers
Alternatives to Lerian MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides read-only tools to search, read, and look up Natural API documentation from an AI agent, enabling documentation lookup without credentials.4MIT
- AlicenseBqualityBmaintenanceEnables AI agents to plan, validate, and discover Ishtaran integrations—covering capabilities, operations, SDK methods, errors, webhooks, and recipes—without executing any financial operations.114 npmApache 2.0
- AlicenseAqualityAmaintenanceEnables AI assistants to search API documentation, retrieve endpoint details, get SDK snippets, and check changelogs from an OpenAPI spec.7253 npmMIT
- FlicenseNot gradedqualityCmaintenanceProvides AI assistants with live, searchable documentation for any programming library, eliminating hallucinated APIs by returning current, structured API references.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to automatically create, update, and publish API documentation through Theneo's platform. Supports OpenAPI specs, Postman collections, AI-powered description generation, and natural language interactions for seamless documentation workflows.MIT
- AlicenseNot gradedqualityCmaintenanceProvides real-time, up-to-date documentation for major LLM providers (OpenAI, Anthropic, Google Gemini) to prevent hallucinations and outdated code patterns in AI agents.9 npm6MIT
TDQS
Scored across 16 tools
Each product-specific tool clearly targets a distinct product, and the discover/execute split is unambiguous. The two meta tools (lerian and portfolio-workflow) serve separate discovery and cross-product workflow purposes, so there is no overlap or confusion between any tools.
The 14 product tools follow a highly consistent <product>-discover/<product>-execute pattern. However, the 'lerian' and 'portfolio-workflow' tools deviate from this convention, introducing a minor inconsistency that prevents a perfect score.
With 16 tools, the count is slightly above the typical 3-15 range, but every tool is necessary to cover seven distinct products, each requiring discovery and execution, plus two meta tools. The size is justified by the multi-product scope.
The tool set provides complete coverage for each product with both discovery and execution capabilities, including full CRUD operations. The addition of a unified documentation tool and a cross-product workflow tool ensures no dead ends and covers the entire lifecycle from exploration to execution.