MCP Server Boilerplate
Related Servers
Alternatives to MCP Server Boilerplate
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceA starter template for building Model Context Protocol servers that integrate with AI assistants like Claude and Cursor, providing custom tools, resource providers, and prompt templates.212 npm-
- FlicenseCqualityDmaintenanceA starter template for building Model Context Protocol servers that can integrate with AI assistants like Claude or Cursor, providing custom tools, resource providers, and prompt templates.212 npm-
- FlicenseBqualityDmaintenanceA starter template for building Model Context Protocol servers that can integrate AI assistants with custom tools, resource providers, and prompt templates.184 npm1-
- AlicenseCqualityDmaintenanceA starter template for building Model Context Protocol servers that can be integrated with Cursor or Claude Desktop, allowing developers to create custom tools and extensions for AI assistants.119 npm14MIT
- 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-
- AlicenseAqualityDmaintenanceA template for building Model Context Protocol servers that allow AI assistants to interact with custom data and services through queryable resources and specialized tools.6MIT
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: 'get-mcp-docs' is for server creation/documentation, while 'hello-world' is for user interaction. There is no overlap or ambiguity between them.
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 verb. There is no predictable pattern across the set.
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 a coherent toolset for server development.
For a boilerplate server, there are significant gaps: no tools for configuration, testing, deployment, or common MCP operations like listing or updating. The surface is severely incomplete for the implied domain of server setup and examples.