mcp-server-starter-kit
Related Servers
Alternatives to mcp-server-starter-kit
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA production-grade MCP starter server in TypeScript with example tools, resources, and integration tests. It provides a clean, extensible foundation for building custom MCP servers.61 npmMIT
- AlicenseNot gradedqualityCmaintenanceA minimal, production-ready starter for building Model Context Protocol servers in TypeScript, supporting both stdio and streamable HTTP transports with optional bearer-token auth.5 npmMIT
- AlicenseAqualityDmaintenanceA production-grade TypeScript starter for building Model Context Protocol servers, supporting stdio and Streamable HTTP transports with modular tools, resources, and prompts.14 npmMIT
- AlicenseAqualityNot gradedmaintenanceA production-ready TypeScript template for building MCP servers with dual transport support (stdio/HTTP), OAuth 2.1 foundations, SQLite caching, observability, and security features including PII sanitization and rate limiting.410 npm-
- AlicenseNot gradedqualityBmaintenanceA feature-complete MCP server template in TypeScript demonstrating tools, resources, prompts, and both stdio and HTTP transports.8MIT
- FlicenseNot gradedqualityCmaintenanceA minimal MCP server template for TypeScript with Streamable HTTP transport, bearer-token authentication, and a sample tool, designed for one-click deployment on Render.-
TDQS
Scored across 2 tools
The two tools are completely distinct: 'ping' provides a liveness check, while 'http_get_json' performs an HTTP request. No overlap or ambiguity exists between them.
The tool names are both lowercase but follow different patterns: 'ping' is a single verb, while 'http_get_json' uses a verb_noun structure with a prefix. The lack of a consistent pattern makes the set feel ad hoc.
With only two tools, the set is thin and borderline. For a starter kit, it is minimal but not entirely unreasonable, yet it still feels sparse for most practical purposes.
The server provides only a basic health check and a JSON GET utility. There are no other operations, and the domain is undefined, so it covers a minimal demo but lacks any meaningful workflow or lifecycle.