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: 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 these functions, making tool selection straightforward.
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 action. There is no predictable pattern across the tool set, making it harder to infer functionality from names alone.
With only 2 tools, this server feels thin and under-scoped for a 'boilerplate' purpose, which typically implies a foundational set of utilities. The count is too low to provide meaningful coverage or demonstrate a coherent tool surface for server development.
The server is severely incomplete for a boilerplate MCP server domain. It lacks essential operations like configuration, testing, deployment, or common utilities, leaving obvious gaps that would hinder agent workflows and fail to support typical development tasks.