A
licenseB
qualityD
maintenanceAn educational implementation of a Model Context Protocol server that demonstrates how to build a functional MCP server for integrating with various LLM clients like Claude Desktop.
1
162
MIT
MCP Server Example
Related Servers
Alternatives to MCP Server Example
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA custom Model Context Protocol server that gives Claude Desktop and other LLMs access to file system operations and command execution capabilities through standardized tool interfaces.23Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that bridges MCP clients with local LLM services, enabling seamless integration with MCP-compatible applications through standard tools like chat completion, model listing, and health checks.-
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that standardizes tool discovery, execution, and context management for AI applications.MIT
- AlicenseNot gradedqualityDmaintenanceA secure, local communication runtime bridge that interfaces a cloud-based Large Language Model (Claude Desktop) with a local machine execution environment using the Model Context Protocol (MCP).Eclipse Public 2.0
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to connect to LLM/API services using the Model Context Protocol, providing real-time interaction and tool access. Also offers RESTful API endpoints via FastAPI for programmatic integration with existing systems.Apache 2.0
TDQS
A4.1/5.0
Scored across 1 tool
Disambiguation5/5
With only a single tool in the set, there is no possibility of confusing it with another tool. Its purpose (searching library documentation by query and library name) is clearly stated.
Naming Consistency5/5
The lone name get_docs follows a clean verb_noun snake_case convention. No inconsistency is possible within a one-tool surface, though it's worth noting 'get' is slightly at odds with the described search behavior.
Tool Count2/5
A single search tool is very thin for a docs-lookup server; agents have no way to list supported libraries or fetch a specific document. One tool earns its place but the surface feels under-scoped rather than well-scoped.
Completeness2/5
Only a query-based search exists, with no listing of available libraries, no fetch-by-id/page retrieval, and no error or fallback path. Notable gaps will force agents to rely on trial-and-error query strings to reach specific content.
Maintenance
ActivityMaintained
ResponsivenessNo issues