-
Book Overview & Buying
-
Table Of Contents
Ship an MCP Server in Python - Fast
By :
Treat mcp.json as your per-workspace switchboard. A clean config lets you juggle multiple servers, keep secrets scoped, and avoid surprise failures when teammates clone the repo. Keep transports straight in your head: this chapter assumes stdio. When you later move to Streamable HTTP, you’ll adjust how the host connects, but the discovery story—tools/resources/prompts—stays the same. Use workspace-specific servers; prefer a .vscode/mcp.json per project so each repo declares exactly which servers to start and how. If you need to manage multiple servers, add one entry per server under servers and name them clearly. If multiple servers export similarly named tools, ensure descriptions and parameter names are unambiguous so the host picks the right one.
Things won’t always go right the first time. The top failure modes are: incorrect args path, wrong launcher in command, and vague tool descriptions. Fix paths first; you won’t reach...
Change the font size
Change margin width
Change background colour