MCP Server Boilerplate
Related Servers
Alternatives to MCP Server Boilerplate
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceA starter template for building custom MCP (Model Context Protocol) servers that can integrate with Claude, Cursor, or other MCP-compatible AI assistants. Provides a clean foundation with TypeScript support, example implementations, and installation scripts for quickly creating custom tools, resources, and prompts.211 npm-
- 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.211 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.211 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-
- 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-
- 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-
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: 'get-mcp-docs' is for server creation/development, while 'hello-world' is for user interaction/greeting. There is no overlap or ambiguity in their functions.
The naming is inconsistent: 'get-mcp-docs' uses kebab-case with a verb-object structure, while 'hello-world' uses kebab-case but is a noun-phrase without a clear action verb. This mixing of conventions reduces predictability.
With only 2 tools, this server feels too thin for a 'boilerplate' purpose, which typically implies foundational or example functionality. The count is insufficient to demonstrate meaningful coverage or utility.
For a boilerplate server, there are significant gaps: no tools for configuration, testing, deployment, or common MCP operations like listing resources. The surface is severely incomplete for development or example use cases.