Ten runnable MCP server boilerplates — TypeScript and Python — with the auth, sandboxing, retries, pagination, and client configs already done.
Stop starting from a blank file every time you need a new MCP server. The Model Context Protocol is the open standard for connecting AI assistants (Claude Desktop, Claude Code, Cursor, Windsurf) to your tools and data — and the official SDK docs get you the first 10% of the way. This pack picks up where the docs leave off.
Ten production-ready MCP server templates, each a complete and runnable codebase with the patterns built in:
The MCP SDKs are stable; the good practices for production servers are still scattered across blog posts, Discord threads, and GitHub issues. These templates codify them: one tool per intent, validate at the boundary, sandbox file/DB access, log to stderr (never stdout), idempotent where possible, errors that actually help you debug. Read the templates and you've absorbed the patterns — keep using them and you ship faster.
The Model Context Protocol is the open standard for connecting AI assistants to external tools and data. An MCP server exposes named tools (and optionally resources and prompts) that clients like Claude Desktop, Claude Code, Cursor, and Windsurf can call. One server works in any MCP-compatible client.
They're complete, runnable servers — not pseudocode. Every template has install + run steps, a working entrypoint, dependencies pinned, and the exact client config snippet to wire it up. The TypeScript templates are tested to compile cleanly against the SDK; the Python templates' safety layers (SQL validator, AST safe-eval, JSON path walker) are exercised before shipping.
Both. The pack ships five TypeScript templates (using @modelcontextprotocol/sdk) and five Python templates (using FastMCP from the official mcp package). The hello-world is in both languages side-by-side so you can see the same shape twice.
Any MCP-compatible client. Setup snippets and a config generator are included for Claude Desktop, Cursor, Windsurf, and Claude Code. For other clients (or for connecting the OAuth server via HTTP), the protocol is the same — the JSON-RPC and transports are spec-defined.
Yes — unlimited personal, internal, and client/work use. Build commercial products on top, ship them under your own name. The only restriction is that you can't resell the pack itself (or the templates substantially unchanged) as a competing starter pack. See LICENSE.txt for the exact terms.
TypeScript templates target @modelcontextprotocol/sdk ^1.29 with Node.js 18+. Python templates target the official mcp package (>= 1.6, includes FastMCP) on Python 3.10+. Both use the modern stable APIs (McpServer + registerTool in TS; @mcp.tool() in Python).
No — it has a pluggable embeddings layer. You can use OpenAI embeddings (with an API key) or local sentence-transformers (no API key, downloads a ~90 MB model on first run). The vector store is an on-disk JSON file with documented swap-in points for Qdrant, pgvector, or Milvus.
61 production-grade Claude Code skills, subagents, and slash commands — instant expert capabilities across web, backend, data, payments, testing, DevOps, and code quality.
40 production-grade Cursor rule files across 20 stacks, 1,700+ directives — stop Cursor from generating outdated, inconsistent code.
10 ready-to-install Claude Code hooks that block secrets and destructive commands, auto-format, run the right tests, gate on typecheck, and log every tool call. Bash + jq, shellcheck-clean, with the real hook contract documented from captured payloads.