MCP Echo Starter
by gatewayHQ
README.md
# MCP Echo Starter
Minimal [Model Context Protocol](https://modelcontextprotocol.io/) server in TypeScript: one `echo` tool over stdio. Use it as a hello-world before building real tools.
## Requirements
- Node.js 18+
## Setup
```bash
npm install
npm test
npm start
```
## Connect
**Claude Code**
```bash
claude mcp add echo -- node /absolute/path/to/mcp-echo-starter/dist/index.js
```
**Cursor** — add to MCP settings:
```json
{
"mcpServers": {
"echo": {
"command": "node",
"args": ["/absolute/path/to/mcp-echo-starter/dist/index.js"]
}
}
}
```
Then ask the model to call the `echo` tool.
## What this is (and isn't)
This free sample has **one tool** and a smoke test. The paid [MCP Server Starter](https://shipreadyagents.com/templates/mcp-server-starter) adds notes CRUD, an SSRF-safe `fetch_url`, a resource, a prompt template, and a fuller test suite.
Guide: [Best MCP Server Starter for TypeScript](https://shipreadyagents.com/blog/best-mcp-server-starter)
## License
MIT
TDQS
A3.7/5.0
Scored across 1 tool
Disambiguation5/5
There is only one tool, so there is no possibility of misselection or overlap with anything else. Its purpose is unambiguous.
Naming Consistency5/5
The single tool uses a clear, lowercase verb-style name consistent with MCP conventions. There is no competing convention to conflict with.
Tool Count3/5
One tool is thin even for a server, though the stated purpose is explicitly a hello-world starter where minimalism is intentional. It is borderline rather than a mismatch.
Completeness3/5
For a demo/starter the surface is self-contained with no dead ends, but there is no domain to cover, so it cannot demonstrate real completeness. It is adequate for its declared demo purpose only.
Maintenance
ActivityMaintained
ResponsivenessNo issues