mcp-server-template
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-template initialize a new MCP server from the template"
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-template
A template for building a TypeScript MCP
server. It ships a reusable carcass — typed fetch client (timeouts, retries,
backoff), rate limiting, TTL cache, OAuth token store, structured errors, leveled
logging, MCP tool-result helpers — plus build tooling, node:test setup, .mcpb
packaging and GitHub Actions CI/release.
The server speaks standard MCP over stdio, so it works with any MCP client (Claude Desktop/Code, Cursor, VS Code, Cline, …).
Use it
Click Use this template on GitHub (or copy this directory), then follow the
checklist in TEMPLATE.md. In short: rename, edit src/config.ts,
add your src/clients/ and src/tools/, and update the manifest and docs. The
included search tool is a placeholder to delete.
Related MCP server: MCP Server Template
Develop
npm install
npm run build # type-check + bundle to dist/index.js
npm test # node:test (mocked, offline)
npm run lint
npm run format
npm run check:api # live upstream health-check (add your endpoints)
npm run inspector # run under the MCP InspectorRuntime requires Node ≥ 20. Contributor/agent guidance lives in
AGENTS.md (the single source of truth; CLAUDE.md just links to it).
Updating
Document how users update your server (keep this section in the generated repo):
.mcpbbundle: download the new bundle from the releases page and reinstall.From source:
git pull && npm ci && npm run build.npx (if published): unpinned
npx -y <package>fetches the latest next run.
Tell users to Watch → Releases, and keep the CHANGELOG current.
License
MIT © Grinv
Available Tools
1 toolsearchSearchCRead-only
Example tool — search the upstream API by keyword. Replace with real tools.
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
Only one tool exists, so there is zero ambiguity in tool selection.
With a single tool named 'search', naming is trivially consistent, though no pattern is established.
A single placeholder tool is far too few for any meaningful server purpose; it does not earn its place.
The tool set is a template with a single example tool, providing no real coverage of any domain.
Maintenance
Related MCP Connectors
A simple Typescript MCP server built using the official MCP Typescript SDK and smithery/cli. This…
A TypeScript MCP server for Home Assistant, enabling programmatic management of entities, automati…
Primarily to be used as a template repository for developing MCP servers with FastMCP in Python, P…
Kickstart development with a customizable TypeScript template featuring sample tools for greeting,…
Related MCP Servers
- AlicenseCqualityDmaintenanceA TypeScript-based template for building Model Context Protocol servers, featuring fast testing, automated version management, and a clean structure for MCP tool implementations.1177 npm4MIT
- AlicenseAqualityNot gradedmaintenanceA production-ready TypeScript template for building MCP servers with dual transport support (stdio/HTTP), OAuth 2.1 foundations, SQLite caching, observability, and security features including PII sanitization and rate limiting.430 npm-
- AlicenseNot gradedqualityDmaintenanceA TypeScript-based template for rapidly developing MCP servers with modular tool architecture, built-in validation using Zod schemas, and comprehensive error handling.5 npmMIT
- AlicenseAqualityBmaintenanceA TypeScript starter template for MCP servers with CI/CD, OIDC npm publishing, and zero-secret setup.171 npmMIT