hello_tool
Hello tool
LABSCO 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
USE CASES
01
Proving a new client can reach a server at all
Before wiring up anything real, one greeting confirms that the transport, the client configuration and tool registration all work. What fails after that is your code, not the plumbing.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-starter": {
"command": "npx",
"args": [
"-y",
"mcp-starter"
]
}
}
}npx
TERMINAL
npx -y mcp-starter
