[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"pack-detail-mcp-server-dev-starter-fr":3,"seo:pack:mcp-server-dev-starter:fr":99},{"code":4,"message":5,"data":6},200,"操作成功",{"pack":7},{"slug":8,"icon":9,"tone":10,"status":11,"status_label":12,"title":13,"description":14,"items":15,"install_cmd":98},"mcp-server-dev-starter","🔌","#8B5CF6","new","Nouveau · cette semaine","MCP Server Developer Starter","Dix choix pour le dev qui construit son premier serveur Model Context Protocol. Choisis un SDK (TypeScript \u002F Python \u002F Go), scaffold avec un framework, débogue dans MCP Inspector, puis soumets au registre Smithery et à l'index awesome-mcp-servers — dans l'ordre d'installation.",[16,28,35,44,51,58,65,75,85,92],{"id":17,"uuid":18,"slug":19,"title":20,"description":21,"author_name":22,"view_count":23,"vote_count":24,"lang_type":25,"type":26,"type_label":27},796,"302d7709-9502-4431-9386-eeb966d200d3","mcp-inspector-debug-test-mcp-servers-302d7709","MCP Inspector — Debug and Test MCP Servers","Official debugging tool for MCP servers. MCP Inspector provides a web UI to connect, test tools, inspect messages, and validate responses from any MCP server interactively.","MCP Hub",130,0,"en","mcp","MCP",{"id":29,"uuid":30,"slug":31,"title":32,"description":33,"author_name":22,"view_count":34,"vote_count":24,"lang_type":25,"type":26,"type_label":27},3143,"152110ec-9a13-4942-b142-0ac3eff2a974","microsoft-mcp-official-model-context-protocol-sdk","Microsoft MCP — Official Model Context Protocol SDK","Microsoft MCP provides official Model Context Protocol building blocks and samples so teams wire reliable tools into agents without ad‑hoc contracts.",77,{"id":36,"uuid":37,"slug":38,"title":39,"description":40,"author_name":22,"view_count":41,"vote_count":24,"lang_type":25,"type":42,"type_label":43},3094,"06ee3ea4-e573-4f6c-8cc4-cef1c1cc8de0","mcp-python-sdk-build-mcp-servers-clients","MCP Python SDK — Build MCP Servers & Clients","Build MCP servers and clients in Python with FastMCP, plus a CLI for dev and install flows; supports stdio, SSE, and Streamable HTTP transports.",60,"script","Script",{"id":45,"uuid":46,"slug":47,"title":48,"description":49,"author_name":22,"view_count":50,"vote_count":24,"lang_type":25,"type":26,"type_label":27},3946,"4c9dd8ef-7adc-5835-bb5a-2a2ccb2fda88","fastmcp-python-framework-for-mcp-servers","FastMCP — Python Framework for MCP Servers","FastMCP is a Python framework for building MCP servers\u002Fclients with generated schemas and lifecycle handling. Verified 25154★; pushed 2026-05-13.",83,{"id":52,"uuid":53,"slug":54,"title":55,"description":56,"author_name":22,"view_count":57,"vote_count":24,"lang_type":25,"type":26,"type_label":27},3686,"8dd07efd-d9a7-5258-967a-43f367ba93f7","fastmcp-typescript-framework-for-mcp-servers","FastMCP — TypeScript Framework for MCP Servers","FastMCP is a TypeScript framework on top of the official MCP SDK; verified 3,112★ and includes HTTP streaming, stateless mode, and a CLI for dev+inspect.",76,{"id":59,"uuid":60,"slug":61,"title":62,"description":63,"author_name":22,"view_count":64,"vote_count":24,"lang_type":25,"type":26,"type_label":27},3186,"cad7f465-8f0f-4455-b75b-704d94077c15","mcp-go-build-mcp-servers-in-go","mcp-go — Build MCP Servers in Go","mcp-go is a Go SDK for building MCP servers (tools, resources, prompts) and serving them over stdio transports, so agents can call your Go code as tools.",70,{"id":66,"uuid":67,"slug":68,"title":69,"description":70,"author_name":71,"view_count":72,"vote_count":24,"lang_type":25,"type":73,"type_label":74},664,"8cf17e75-0c30-4c57-971d-34d7284e4049","build-your-own-mcp-server-step-step-guide-8cf17e75","Build Your Own MCP Server — Step-by-Step Guide","Complete guide to building a custom MCP server from scratch. Covers the protocol, TypeScript and Python SDKs, tool definition, resource management, testing, and deployment patterns.","Prompt Lab",163,"prompt","Prompt",{"id":76,"uuid":77,"slug":78,"title":79,"description":80,"author_name":81,"view_count":82,"vote_count":24,"lang_type":25,"type":83,"type_label":84},64,"04ab7e67-695d-4138-b53a-6ecae4f695ea","claude-official-skill-mcp-builder-04ab7e67","Claude Official Skill: mcp-builder","Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP serve...","Anthropic",123,"skill","Skill",{"id":86,"uuid":87,"slug":88,"title":89,"description":90,"author_name":22,"view_count":91,"vote_count":24,"lang_type":25,"type":26,"type_label":27},810,"5ca696fe-0d4f-4b2e-94f7-652f9d3a0da0","smithery-mcp-server-registry-installer-5ca696fe","Smithery — MCP Server Registry and Installer","Discover, install, and manage MCP servers from a curated registry. Smithery provides one-command setup for 200+ MCP servers with Claude Code and Cursor integration.",240,{"id":93,"uuid":94,"slug":95,"title":96,"description":97,"author_name":22,"view_count":64,"vote_count":24,"lang_type":25,"type":26,"type_label":27},3062,"cd5e75f3-8aa3-41fc-9a7e-be6394ad67af","awesome-mcp-servers-mcp-directory-index","awesome-mcp-servers — MCP Directory & Index","awesome-mcp-servers is a curated index of MCP servers, clients, and tutorials. Use it to pick a server, then add it to your MCP config and verify.","tokrepo install pack\u002Fmcp-server-dev-starter",{"pageType":100,"pageKey":8,"locale":25,"title":101,"metaDescription":102,"h1":103,"tldr":104,"bodyMarkdown":105,"faq":106,"schema":122,"internalLinks":127,"citations":140,"wordCount":153,"generatedAt":154},"pack","MCP Server Developer Starter — Build & Ship Your First MCP Server","MCP Inspector, Microsoft TS SDK, Python SDK, FastMCP, mcp-go, Smithery, awesome-mcp-servers — the producer-side starter pack for developers shipping their first Model Context Protocol server. SDK → scaffold → test → register.","MCP Server Developer Starter — From SDK to Registry","Ten picks in install order for the developer building, not just installing, MCP servers. Pick a language SDK (TS \u002F Python \u002F Go), scaffold with a framework, debug live in MCP Inspector, then submit to Smithery and awesome-mcp-servers so agents can find you. Producer-side companion to the consumer-side MCP Server Stack pack.","## Who this pack is for\n\nYou've used MCP servers in Claude Code, Cursor, or Codex CLI for a while. Now you want to **build** one — wrap your internal API, your private CRM, your custom tool — so any MCP-speaking agent can call it. This pack is the producer-side starter; if you only want to install existing servers, see the [MCP Server Stack](\u002Fen\u002Fpacks\u002Fmcp-server-stack) pack instead.\n\nThe ten picks here cover the full loop: pick an SDK in the language you already write, scaffold with a higher-level framework so you skip the boilerplate, debug interactively in MCP Inspector against the live server, then publish to a registry so other developers' agents can discover and install you.\n\n## Install in this order\n\n1. **MCP Inspector** — install this *first*. It's the official web UI for connecting to any MCP server (stdio or HTTP), listing tools, sending test calls, and inspecting raw JSON-RPC messages. You'll keep it open in a browser tab for the entire build. Trying to debug an MCP server without Inspector is like writing a web app without DevTools.\n2. **Microsoft MCP — Official TypeScript SDK** — the canonical SDK if you live in Node. Defines the `Server` class, transports (stdio, HTTP), and the typed `RequestHandler` schemas. Use this when you want full control or you're writing reference samples.\n3. **MCP Python SDK** — the official Python SDK. Same shape as the TS one: `Server`, `stdio_server`, request handlers. Pick Python if your tool calls already use Python libraries (data, ML, scraping).\n4. **FastMCP — Python Framework** — the Flask-vs-Werkzeug of MCP. Decorator-based, dramatically less boilerplate. `@mcp.tool()` on a normal function and you have a server. Use this for 90% of Python MCP servers; drop to the raw SDK only when you need fine-grained transport control.\n5. **FastMCP — TypeScript Framework** — same philosophy on the Node side. `server.addTool({ name, parameters, execute })` and you're done. Pairs with the official TS SDK as needed.\n6. **mcp-go — Build MCP Servers in Go** — the Go SDK. Use this when latency or single-binary deploy matters (serverless cold start, embedded in a CLI, Docker scratch image).\n7. **Build Your Own MCP Server — Step-by-Step Guide** — the tutorial you read before your first commit. Covers JSON-RPC framing, tool discovery, error envelopes, and the three transports. Saves you a half-day of reading specs.\n8. **Claude Official Skill: mcp-builder** — Anthropic's official Claude skill for scaffolding MCP servers. Plug into Claude Code, describe the tool you want, and it writes the SDK boilerplate (manifest, request handlers, type stubs). Great for the first server; you'll outgrow it on the third.\n9. **Smithery — MCP Server Registry & Installer** — the de-facto registry. Publishing here gets your server installable via `npx smithery install your-server` and listed alongside hundreds of others. Required reading for visibility.\n10. **awesome-mcp-servers — MCP Directory Index** — the GitHub-hosted curated index. PR your server in once it's stable. Different audience from Smithery (devs browsing on GitHub vs agents auto-discovering), so do both.\n\n## How they fit together\n\n```\nPick an SDK:    Microsoft TS  ─┐\n                MCP Python   ──┼─▶  scaffold with a framework\n                mcp-go       ─┘       │\n                                      ├─ FastMCP Python\n                                      ├─ FastMCP TypeScript\n                                      └─ Claude mcp-builder skill\n                                              │\n                                              ▼\n                                       MCP Inspector\n                                       (live debug + test calls)\n                                              │\n                                              ▼\n                                       Publish\n                                       ├─ Smithery registry\n                                       └─ awesome-mcp-servers PR\n```\n\nThe four-step loop **SDK → framework → Inspector → registry** is the entire job. Most failure modes (no agent can find your tool, tool calls hang, schema validation errors) come from skipping Inspector. Don't skip Inspector.\n\n## Tradeoffs you'll hit\n\n- **Raw SDK vs FastMCP** — Raw SDK = 80 lines for a hello-world server, full control over transports and middleware. FastMCP = 12 lines, decorator-based, opinionated. Start with FastMCP; drop to raw SDK only when you hit a wall (custom auth, non-stdio transport you're inventing).\n- **TypeScript vs Python vs Go** — TS has the most reference samples and the largest ecosystem of agent hosts speaking it natively. Python wins when your tool body is already Python (pandas, sklearn, scrapy). Go wins for single-binary deploys and tight latency.\n- **Smithery vs awesome-mcp-servers** — Smithery is machine-readable (agents auto-install). awesome-mcp-servers is human-readable (developers browse on GitHub). Different funnels — submit to both.\n- **mcp-builder skill vs hand-written** — The skill is great for the first server (writes correct boilerplate). It generates patterns you'll want to customize by server three; expect to outgrow it.\n\n## Common pitfalls\n\n- **stdio transport buffering** — never write to stdout for logging. Logs go to stderr; stdout is reserved for JSON-RPC frames. Mixing them silently corrupts every message.\n- **Tool schema drift** — your tool's input schema in the manifest must exactly match what your handler expects. MCP Inspector will surface the mismatch instantly; without it, you'll spend hours wondering why the agent passes `query` and your handler reads `q`.\n- **Long-running tools without progress** — MCP supports progress notifications. If your tool takes >5 seconds, emit progress, or the host will assume it hung and time out.\n- **Forgetting to register on shutdown** — handlers that hold resources (DB connections, file locks) need `on_shutdown` cleanup. Inspector won't catch this; you'll find it in production.\n- **Submitting to Smithery before the server is stable** — version churn breaks installs for every agent that pinned to you. Tag a real `v1.0.0` first, then publish.",[107,110,113,116,119],{"q":108,"a":109},"Do I need to pick TypeScript, Python, or Go up front?","Pick the language where your tool body already lives. If your MCP server wraps a Python data pipeline, write it in Python. If it wraps a Node API client, write it in TS. The MCP protocol itself is language-agnostic — agents don't know or care what language your server is in, only what tools and schemas it exposes. Don't switch languages just because TypeScript has more samples.",{"q":111,"a":112},"FastMCP vs the raw official SDK — which should I start with?","Start with FastMCP unless you have a specific reason not to. The raw official SDKs give you full control but require ~80 lines of boilerplate for a hello-world server. FastMCP (Python or TS) wraps that in decorators and gets you to a working tool in ~12 lines. The escape hatch back to the raw SDK is always there when you hit a real customization need (custom auth, exotic transport, deep middleware). Premature use of the raw SDK is the #1 reason first-time MCP servers never ship.",{"q":114,"a":115},"Why is MCP Inspector listed first if I haven't written any code yet?","Because the moment your first handler compiles, you'll want to send it a tool call and see the raw JSON-RPC exchange. Inspector is the only sane way to do that interactively. Installing it first means it's already running on localhost when your scaffolded server boots — saves the context switch later. Treat it like installing DevTools before writing a webpage.",{"q":117,"a":118},"Smithery vs awesome-mcp-servers — submit to both or pick one?","Both. They serve different funnels: Smithery is machine-readable (agents query the registry to auto-install your server) and awesome-mcp-servers is human-readable (developers browse the GitHub README looking for tools to add manually). Submitting to Smithery without the awesome-mcp-servers PR cuts you off from every developer who hasn't onboarded to Smithery yet, which is most of them in 2026.",{"q":120,"a":121},"How long until my first working server with this pack?","About two evenings of focused work for someone comfortable in TS or Python. Evening one: install Inspector, scaffold with FastMCP, get a hello-world tool call working end-to-end. Evening two: wire up your actual tool body, write the manifest, debug schema mismatches in Inspector, package for Smithery. The mcp-builder Claude skill compresses evening one to about an hour if you're willing to let Claude write the scaffold for you.",{"@context":123,"@type":124,"name":13,"description":125,"numberOfItems":126,"inLanguage":25},"https:\u002F\u002Fschema.org","ItemList","Ten picks in install order for the developer building their first Model Context Protocol server — SDK, framework, debugger, registry.",10,[128,132,136],{"url":129,"anchor":130,"reason":131},"\u002Fen\u002Fpacks\u002Fmcp-server-stack","MCP Server Stack pack","Consumer-side companion: the MCP servers everyone installs once this one ships",{"url":133,"anchor":134,"reason":135},"\u002Fen\u002Fai-tools-for\u002Fmcp","All MCP tools on TokRepo","Browse the broader MCP catalog beyond the curated ten",{"url":137,"anchor":138,"reason":139},"\u002Fen\u002Ftopics","Browse other topic packs","Adjacent packs for agent frameworks, browser automation, and SDK comparisons",[141,145,149],{"claim":142,"source_name":143,"source_url":144},"Model Context Protocol specification and SDK references","modelcontextprotocol.io","https:\u002F\u002Fmodelcontextprotocol.io",{"claim":146,"source_name":147,"source_url":148},"MCP Inspector official debugging tool","MCP Inspector GitHub","https:\u002F\u002Fgithub.com\u002Fmodelcontextprotocol\u002Finspector",{"claim":150,"source_name":151,"source_url":152},"Smithery MCP server registry and installer","Smithery","https:\u002F\u002Fsmithery.ai",905,"2026-05-22T10:00:00Z"]