xiaofenshen-mcp-server
Related Servers
Alternatives to xiaofenshen-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceExposes OpenAPI/Swagger API documentation as MCP tools, enabling AI agents to search, inspect, and call API endpoints through natural language.517 npmMIT
- AlicenseBqualityBmaintenanceExposes 97 official Shanghai Library open data APIs and the Sou-Yun poetry database (1.99 million poems) as 12 MCP tools, covering genealogy, ancient books, calligraphy, historical buildings, and more. Enables MCP clients to query these datasets using natural language.1225 PyPI4MIT
- AlicenseNot gradedqualityDmaintenanceProvides MCP tools to list and search OpenAI Agents SDK documentation, enabling LLMs to retrieve documentation topics and content via natural language queries.MIT
- AlicenseNot gradedqualityDmaintenanceExposes OpenAPI specifications as MCP tools, enabling AI assistants to explore and understand API structures, endpoints, schemas, and documentation through semantic queries.12 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables agents to query real-time OpenAPI documentation of backend services, providing tools to list services, endpoints, and schemas via MCP.-

@prosodyai/mcp-docsofficial
AlicenseAqualityBmaintenanceExposes ProsodyAI documentation, SDK references, REST API reference (OpenAPI), and curated implementation recipes to AI coding agents via MCP tools and resources.8MIT
TDQS
Scored across 3 tools
Each tool serves a completely distinct purpose: reading public shares, listing image prompt templates, and fetching product docs. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern with snake_case: read_public_share, list_image_prompt_templates, get_product_docs. The naming is predictable and uniform.
With only 3 tools, the server is tightly scoped for its read-only informational purpose. Each tool earns its place and covers a distinct resource, fitting comfortably within the ideal range.
The server covers the three main public-facing resource types (shares, templates, docs) with read operations. No obvious gaps exist for the stated read-only domain, as operations align with the server's purpose.