yapi-mcp-server
Provides an MCP (Model Context Protocol) server that integrates an AI assistant with a YAPI API management instance. It exposes MCP tools to list YAPI projects/categories/interfaces, search interfaces, fetch interface details, and manage/refresh a local cache (including cache stats and per-project cache clearing).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Upstream authentication is via YAPI project tokens stored in application-mcp.yml. TLS/auth requirements for the MCP server itself are not documented in the README, and there is no mention of fine-grained scopes, token rotation, or protection against exposing the SSE endpoint publicly. Cache management implies local storage/retention of YAPI data, which may need explicit consideration.
⚡ Reliability
Best When
You have a self-hosted YAPI instance and want an MCP-capable client (e.g., an agent in an IDE) to query and search API info via standardized MCP tools.
Avoid When
When you cannot secure the server and upstream YAPI credentials (tokens), or when you need strong guarantees about API error semantics/pagination/retry behavior that are not documented here.
Use Cases
- • AI-assisted exploration of YAPI API documentation (projects, categories, interfaces)
- • Natural-language search for API endpoints by name/keyword/path
- • Retrieving detailed request/response information for a specific interface
- • Caching YAPI data locally to reduce repeated YAPI queries
Not For
- • Public, unauthenticated deployments exposed to the internet
- • Use cases requiring strict compliance reporting or audited security controls without additional hardening
- • Workflows needing formal REST/GraphQL/OpenAPI client compatibility (this is primarily an MCP server)
Interface
Authentication
Auth mechanism appears to rely on static per-project tokens for the upstream YAPI, configured via YAML. The README does not describe any auth for the MCP server itself (e.g., whether it is protected).
Pricing
Open-source style project (MIT) per README; no hosted service pricing described.
Agent Metadata
Known Gotchas
- ⚠ Cache-related tools (refreshCache/clearProjectCache) may have side effects; idempotency and concurrency behavior are not documented.
- ⚠ Auth protection for the MCP server endpoint is not described; ensure MCP server is reachable only in trusted environments.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for yapi-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.