Yapi-MCP and MCP

Both are servers for MCP (Microservice Communication Protocol), but one is a more general-purpose implementation (Yapi-MCP) while the other is specifically the official remote server for Jina AI's ecosystem, making them **ecosystem siblings** where the latter is a specialized instance within a broader microservice framework that could potentially leverage or be an alternative to the former in specific contexts.

Yapi-MCP
65
Established
MCP
56
Established
Maintenance 2/25
Adoption 18/25
Maturity 25/25
Community 20/25
Maintenance 13/25
Adoption 10/25
Maturity 15/25
Community 18/25
Stars: 72
Forks: 25
Downloads: 5,640
Commits (30d): 0
Language: TypeScript
License: MIT
Stars: 533
Forks: 59
Downloads: —
Commits (30d): 3
Language: TypeScript
License: Apache-2.0
Stale 6m
No Package No Dependents

About Yapi-MCP

lzsheng/Yapi-MCP

yapi mcp server

Implements Model Context Protocol (MCP) server exposing YApi interface management capabilities—search, create, and update API definitions—enabling AI tools like Cursor and Claude Desktop to understand and manipulate API documentation within coding workflows. Communicates via stdio transport with multi-project support, caching layer, and flexible configuration through CLI arguments or environment variables.

About MCP

jina-ai/MCP

Official Jina AI Remote MCP Server

Exposes 19 tools for web search, content extraction, academic research, and semantic operations via Jina's Reader, Embeddings, and Reranker APIs. Uses Streamable HTTP transport for remote MCP compatibility with Claude, LM Studio, and other clients, with optional stdio proxy support for older integrations. Includes server-side tool filtering via query parameters to reduce context window overhead by selectively registering only needed capabilities.

Scores updated daily from GitHub, PyPI, and npm data. How scores work