MCP Server Boilerplate
Related Servers
Alternatives to MCP Server Boilerplate
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceA starter template for building MCP (Model Context Protocol) servers that integrate with Claude, Cursor, or other MCP-compatible AI assistants. Provides a clean foundation with TypeScript support, example tool implementation, and installation scripts for quick customization.212 npm-
- FlicenseAqualityDmaintenanceA starter template for building MCP (Model Context Protocol) servers with TypeScript support. Provides a clean foundation with example tools, resources, and prompts for creating custom integrations with Claude, Cursor, or other MCP-compatible AI assistants.24 npm-
- FlicenseCqualityDmaintenanceA starter template for building custom MCP servers that can integrate with Claude, Cursor, or other MCP-compatible AI assistants. Provides a clean foundation with TypeScript support, example implementations, and easy installation scripts for quickly creating tools, resources, and prompt templates.212 npm-
- FlicenseCqualityDmaintenanceA starter template for building MCP (Model Context Protocol) servers that can integrate with Claude, Cursor, or other MCP-compatible AI assistants. Provides a foundation with example implementations of tools, resources, and prompts along with installation scripts.212 npm-
- FlicenseNot gradedqualityDmaintenanceA starter template for building MCP servers with TypeScript support, example tools, and automated installation scripts for Claude Desktop, Cursor, and other MCP-compatible AI assistants. Provides a foundation for creating custom tools, resource providers, and prompt templates.4 npm-
- FlicenseAqualityDmaintenanceA starter template for building custom MCP servers with example implementations of tools, resources, and prompts. Includes TypeScript support and installation scripts for Claude Desktop, Cursor, and other MCP-compatible clients.24 npm-
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one is for creating MCP servers (get-mcp-docs) and the other is for greeting users (hello-world). There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool.
The naming is inconsistent: get-mcp-docs uses kebab-case with a verb-noun structure, while hello-world uses kebab-case but is a phrase rather than a clear verb-noun pattern. This mixed style reduces predictability and readability.
With only 2 tools, this server feels too thin for a boilerplate purpose, which typically implies a foundational set of utilities. The scope seems limited, lacking coverage for common operations like setup, configuration, or testing that might be expected in a boilerplate.
Inferred domain is MCP server development, but the tool surface is severely incomplete: it includes a documentation tool and a greeting, but misses essential CRUD/lifecycle operations (e.g., initialize, configure, deploy, test). This will likely cause agent failures in practical workflows.