MCP Server Templates and Starters: What Is Current in November 2026

The best MCP server starter in November 2026 is usually not a template at all. It is the official SDK's own setup: uv add "mcp[cli]" for Python or npm install @modelcontextprotocol/server for TypeScript, plus a copy of one of the SDK's example servers. For a remote server, Cloudflare's authless template and Vercel's mcp-handler route are the quickest hosted starts.

Many starters you will find in search results are stale. The official TypeScript scaffolder on npm is deprecated and pins an SDK version from 2024. The official Python scaffolder repository is archived. This guide lists what is current, what each starter gives you, and how to check any template before you build on it.

Checked against: npm, PyPI and the GitHub API on 2 November 2026; the Python SDK and TypeScript SDK repositories; Cloudflare's remote MCP guide; and Vercel's MCP deployment docs (last updated 18 September 2026). eSEOspace did not deploy any of these templates.

The quick picker

1. Official Python SDK setup

The Python SDK's install docs use uv:

uv init my-server --python 3.12
cd my-server
uv add "mcp[cli]"

On PyPI on 2 November 2026, mcp was at 2.3.0, requiring Python 3.10 or newer; the SDK README says 3.11+. A minimal server is a few lines with from mcp.server import MCPServer and @mcp.tool(). Our Python first-tool lesson walks through it.

What you get: the official API, uv run mcp dev to open the Inspector, mcp install for Claude Desktop, and the in-memory test Client.

Watch out for: templates that import from mcp.server.fastmcp import FastMCP. The SDK's What's New page says that path "is gone rather than deprecated" in v2.

2. Official TypeScript SDK setup

npm init -y && npm pkg set type=module
npm install @modelcontextprotocol/server zod
npm install -D tsx typescript

The v2 TypeScript SDK splits into packages. You install @modelcontextprotocol/server for servers, plus adapters such as @modelcontextprotocol/node when you need them. On npm on 2 November 2026, @modelcontextprotocol/server was 2.4.0, while the v1 package @modelcontextprotocol/sdk was 1.32.2. Our TypeScript first-tool lesson covers registerTool and serveStdio.

3. The SDK example folders

Both SDK repositories ship example servers you can copy:

• Python examples/servers/ includes simple-tool, simple-resource, simple-prompt, simple-streamablehttp, simple-streamablehttp-stateless, simple-auth and everything-server, among others.
• TypeScript examples/ includes bearer-auth, elicitation, dual-era, cli-client and todos-server. The TypeScript docs' examples page says every example is a complete client and server pair "that CI runs on every pull request, so they stay correct as the SDK changes."

That CI promise is the main reason to prefer SDK examples over third-party templates. They change when the SDK changes.

The separate reference servers repository holds seven servers, including Filesystem, Fetch, Git, Memory and Time. Its README calls them "educational examples for developers building their own MCP servers," not production-ready solutions. Older reference servers such as PostgreSQL, SQLite and Slack sit in the archived repository with no security guarantees.

4. Cloudflare remote MCP template

Cloudflare's guide creates a remote server with no sign-in:

npm create cloudflare@latest -- remote-mcp-server-authless --template=cloudflare/ai/demos/remote-mcp-authless

npm start serves it locally at http://localhost:8788/mcp, and npx wrangler@latest deploy publishes it to https://<worker-name>.<your-account>.workers.dev/mcp. For sign-in, the guide describes adding an authorization server Worker in front, rather than a separate template.

Good for: a public, read-only demo server, or a team that already runs on Workers. Add OAuth before exposing private data. Our comparison of Cloudflare Workers vs Vercel for MCP hosting covers the trade-offs.

5. Vercel mcp-handler

Vercel's docs add an MCP route to an existing Next.js App Router app:

npm i mcp-handler@2.1.1 @modelcontextprotocol/server@2 zod@4

The route lives at app/api/mcp/route.ts and uses createMcpHandler from mcp-handler. Vercel's note says version 2 "uses @modelcontextprotocol/server instead of @modelcontextprotocol/sdk, changes tool registration, and removes legacy HTTP+SSE transport and Redis configuration." The docs pin mcp-handler 2.1.1; npm showed 2.3.0 as the latest release on 2 November 2026.

Vercel also links one-click templates for Next.js and for Vercel Functions. For auth, its docs say withMcpAuth verifies tokens and publishes metadata, but the package "does not issue tokens or run an authorization server."

6. FastMCP 4 (Python framework)

FastMCP is a separate open-source project, now at PrefectHQ/fastmcp on GitHub. PyPI listed fastmcp 4.1.5 on 2 November 2026. Its upgrade guide says "FastMCP 4 builds on the MCP Python SDK v2." It adds extras on top of the SDK, such as OpenAPI conversion and server composition.

Do not confuse it with the SDK's old built-in mcp.server.fastmcp module, which v2 removed, or with punkpeye/fastmcp, a separate TypeScript framework that shares the name. Our FastMCP vs the official Python SDK comparison helps you choose.

7. Generators from an OpenAPI spec

If you already have an OpenAPI document, a generator gives you a working prototype:

• FastMCP from_openapi turns each endpoint into a tool, with route maps to filter them.
• Speakeasy generates "a TypeScript-based MCP server," per its MCP guide.

Both are starting points. FastMCP's docs say models perform better with curated servers than with auto-converted ones. See turning an OpenAPI spec into an MCP server.

8. Data-source starters from this guide

Each of these is a complete, small server you can copy, with code that ran on 2 November 2026:

• PostgreSQL and SQLite
• CSV files, Excel files and Google Sheets
• A REST API and an internal API in TypeScript
• Docs search, a Slack bot, WordPress and Shopify

Starters to avoid

How to vet any template in five minutes

1. Check the pinned SDK. Open package.json or pyproject.toml. @modelcontextprotocol/sdk 0.x or 1.x means a v1-era template.
2. Search for old imports. mcp.server.fastmcp, server.tool(, SSEServerTransport and StreamableHTTPServerTransport plus connect() all point to older patterns.
3. Check the repository. Is it archived? When was the last commit?
4. Run it with the Inspector. List tools and call one. Our Inspector lesson shows the CLI.
5. Read the security defaults. No auth, a wide CORS policy or a 0.0.0.0 bind without host checks are fine for a demo, not for production.

Our free server risk checklist covers the security side in more depth.

Next step

If you are learning, the free Learn MCP course takes you from first tool to deployment with current code. If you need a production server built from the right starter, with auth, logging and tests, eSEOspace MCP development can help. For inspiration on what to build, see our MCP server project ideas.

Frequently asked questions