Summary
A scaffold rather than a capability — the value is the wiring, not the tool.
The entire surface is hello_tool, which takes a name. Installing it proves that a client can find a server, register a tool and call it; the next move is replacing that tool with one that does work. Nothing here talks to an external service, so there is no account or endpoint to arrange before it runs.
What it is
A starter scaffold for building an MCP server, shipping one demonstration tool so the wiring can be tested before any real capability exists.
What you get
- hello_tool, which takes a name and returns a greeting — the working example you edit into your own tool.
- A published package that runs as-is, so client configuration and tool registration can be confirmed end to end before you write code.
Requirements
No account and no key. hello_tool takes a name and returns text, with no external service behind it.
Setup effort
One command — npx -y mcp-starter