minimal-mcp-server
Related Servers
Alternatives to minimal-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Node.js/TypeScript MCP server template with sample tools (ping and system_info) that demonstrates how to build custom tools for Claude Desktop using stdio transport.8 npmISC
- AlicenseNot gradedqualityDmaintenanceA local Model Context Protocol (MCP) server that exposes custom tools to Claude Desktop, enabling direct interaction with your local environment. It provides a framework for building and integrating custom TypeScript tools into the Claude interface.8 npmMIT
- AlicenseDqualityDmaintenanceA minimal Model Context Protocol server in TypeScript that demonstrates MCP-compliant resources and tools for LLMs, featuring simple resources and a basic tool that echoes messages or returns greetings.15Apache 2.0
- AlicenseAqualityAmaintenanceA minimal MCP server that provides a health check (server_info) and multi-language greeting (greet) tools, built with TypeScript and the official SDK.2MIT
- -licenseNot gradedqualityNot gradedmaintenanceA production-ready TypeScript MCP server providing basic tools (add, echo, timestamp), resources (server info, greetings, data access), and prompt templates (analyze, code-review, summarize). Serves as a foundation for building custom MCP servers with extensible architecture.284 npm-
- AlicenseAqualityAmaintenanceProduction-ready template for building MCP servers with TypeScript, featuring example tools and resources, and Claude Desktop integration.18 npmMIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: echo returns input messages, get-current-time retrieves the current date/time, and search-wikipedia searches Japanese Wikipedia. There is no overlap in functionality, making tool selection unambiguous for an agent.
The naming follows a mostly consistent verb_noun pattern (echo, get-current-time, search-wikipedia), with echo being a slight deviation as a single verb. The style is readable and predictable, though not perfectly uniform.
With only 3 tools, the server feels thin for a general-purpose MCP server, as it lacks depth in any specific domain. However, it is well-scoped for minimal functionality, avoiding bloat.
The toolset is severely incomplete for any coherent domain; it mixes unrelated utilities (echo, time) with a specific search function (Wikipedia). There are obvious gaps, such as missing CRUD operations or a focused workflow, which could lead to agent failures.