MCP Server Starter
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Server Starter what time is it in Tokyo right now?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Server Starter (TypeScript)
A small, production-minded starting point for a Model Context Protocol server that Claude, Cursor, VS Code, ChatGPT and agent frameworks can connect to.
Stateless Streamable HTTP (
POST /mcp): any replica or Worker isolate can answer any request, so scaling and deploys never drop sessions.stdio for local clients (Claude Desktop, Cursor, Claude Code).
One codebase, two runtimes: Node (
src/node.ts) and Cloudflare Workers (src/worker.ts).The boring edge cases handled: GET/DELETE
/mcp→405JSON (no reconnect loops), unknown and.well-knownpaths → JSON404(never your HTML page), Origin check, body size limit.One example tool (
time_in_zone) with input/output schemas, annotations and error handling.preflight: a checker you run against any deployed MCP URL before you share it.11 tests with a real MCP client (in-process, real HTTP server, and stdio).
Quick start
git clone https://github.com/ninonorden/mcp-server-starter.git
cd mcp-server-starter
npm install
npm run dev # http://127.0.0.1:3000/mcp
npm testTry it with the MCP Inspector: npm run inspector, then connect to http://127.0.0.1:3000/mcp (transport: Streamable HTTP).
Related MCP server: mcponce
Preflight: will real clients work with my server?
npm run preflight -- https://your-server.example.com/mcpHTTP methods
✓ GET -> 405
✓ DELETE -> 405
Discovery paths
✓ /.well-known/oauth-protected-resource/mcp -> 404
✓ /.well-known/oauth-protected-resource -> 404
✓ /.well-known/oauth-authorization-server -> 404
Auth challenge
! unauthenticated tools/call -> 200 (server is public; make sure that is intended)
MCP session
✓ initialize -> mcp-server-starter@1.0.0 in 27 ms
✓ tools/list -> 1 tools in 15 ms
PASSED: 0 failure(s), 1 warning(s)It catches the failures that most often break clients in production: HTML catch-all routes answering GET /mcp or .well-known paths, 401 without WWW-Authenticate, broken initialize, tools without descriptions/annotations, invalid tool names and slow responses. It works against any MCP server, not only this one. Pass --key <apiKey> or --token <bearer> for protected servers.
Connect a client
Claude Code
claude mcp add --transport http my-server https://your-server.example.com/mcpCursor (.cursor/mcp.json) / Claude Desktop (stdio, after npm run build)
{
"mcpServers": {
"my-server-remote": { "url": "https://your-server.example.com/mcp" },
"my-server-local": { "command": "node", "args": ["/absolute/path/to/mcp-server-starter/dist/stdio.js"] }
}
}Deploy
Cloudflare Workers
npx wrangler login
npm run cf:deploy # https://mcp-server-starter.<you>.workers.dev/mcp
npm run preflight -- https://mcp-server-starter.<you>.workers.dev/mcpNode anywhere (Fly.io, Railway, Render, a VM): npm run build && HOST=0.0.0.0 PORT=8080 npm start.
Set ALLOWED_ORIGINS=https://your-web-app.com if a browser app calls the server directly (localhost is always allowed).
Add a tool
Open src/server.ts and add another server.registerTool(...). Tips that make models use your tool well:
Write the description for the model: what it does and when to use it.
Add
annotations(readOnlyHint,destructiveHint) so clients can ask for confirmation.Return
isError: truewith a helpful message instead of throwing.
Project layout
src/server.ts MCP server + tools (created per request)
src/app.ts Hono app: /mcp, 405/404 handling, Origin + size checks
src/node.ts Node entry (Streamable HTTP)
src/worker.ts Cloudflare Workers entry
src/stdio.ts stdio entry
scripts/preflight.ts
test/ in-process, HTTP edge cases, end-to-end (real server + stdio)Need auth, multi-tenancy and billing? → Pro
This starter is intentionally small: it has no authentication, so anything you deploy is public. When your server goes to real users, the MCP Server Starter Kit Pro ($39 one-time) adds:
Free starter | Pro | |
Stateless Streamable HTTP + stdio, TypeScript | ✓ | ✓ |
| ✓ | ✓ (+ auth checks, key hashing) |
Python version (official SDK v2) | ✓ | |
API keys (hashed, scoped) | ✓ | |
OAuth 2.1 resource server (protected-resource metadata, JWKS, audience checks), works with ChatGPT/Claude connectors | ✓ | |
Per-caller server binding / tenant isolation | ✓ | |
Rate limiting, SSRF-safe fetch, timeouts | ✓ | |
Metering hook + Apify pay-per-event Actor (charge per tool call) | ✓ | |
Deploy configs: Workers, Vercel, Fly, Docker, Apify | Workers | ✓ |
7 guides (architecture, auth, clients, deploy, monetize, checklist, publish) + | ✓ | |
48 tests | 11 | 48 |
Get MCP Server Starter Kit Pro: $39 → · 14-day money-back guarantee · unlimited projects
Other tools from Nino Ventures
Filing Watch — SEC Form 4 / 8-K alerts to Telegram ($29, free starter)
Agency Monitoring Pack — five n8n workflows ($24)
Stackdiff — Shopify app & theme detector ($4/mo Pro)
License
MIT © Nino Ventures
Available Tools
1 tooltime_in_zoneCurrent time in a time zoneARead-onlyIdempotent
Returns the current date and time in the given IANA time zone (e.g. Europe/Amsterdam, America/New_York). Use it whenever the user asks what time it is somewhere.
Inputs: timeZone (required). Returns: iso, local, timeZone
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of selecting the wrong one. The tool's purpose (current time in a given IANA zone) is clearly stated and non-overlapping with anything else on the server.
The lone name `time_in_zone` is descriptive snake_case and reads naturally. Consistency across a pattern cannot really be assessed with one tool, but nothing is inconsistent.
A single tool is a thin surface for anything beyond a hello-world scaffold, matching the 'starter' framing but offering little utility. It sits at the low end of the appropriate range.
The time domain is only minimally covered: there is no timezone conversion, no way to list supported zones, and no fallback for local/server time. Agents asking anything beyond 'what time is it in X' will hit a dead end.
Maintenance
Related MCP Connectors
Generate a typed SDK, CLI, and MCP server from any OpenAPI or GraphQL spec, and keep them current.
MEOK MCP Test MCP — golden-file + schema-drift + tool-failure tests for any MCP server. Drop-in
Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.
Host any HTTP API as a standard MCP server; auto-distribute to 12+ mainstream agent platforms.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients to call a hello tool and access observability features, including metrics and request traces, through a Streamable HTTP transport with SQLite-backed storage.-
- AlicenseNot gradedqualityBmaintenanceEnables building and running MCP servers from a single executable, with shared daemons, concurrency controls, retries, caching, security, and OpenAPI integration.MIT
- FlicenseNot gradedqualityCmaintenanceExposes the getWeather and getTime tools over a stateless streamable-HTTP MCP endpoint at /mcp, so clients can look up weather for a location and the current time for a timezone through MCP tool calls. Running the same pure tool code as the app's OpenAPI surface, it lets you register the deployment as a remote MCP tool and compare MCP against custom-OpenAPI integration.-
- FlicenseNot gradedqualityCmaintenanceEnables deployment and connection to a minimal Streamable HTTP MCP server with bearer-token authentication, a health endpoint, and an example tool, while allowing developers to add custom tools.-