MCP server project (TypeScript) · Chapter 12 of 12
Shipping
By the end of this chapter you can write the config files two real assistants read to reach Parda's server, one over stdio and one over HTTP, keep a member's token out of any file that is shared, say which changes to the tools break the assistants already using them, and give each release the version number that tells them so. Build it in your browser: a real editor and terminal, AI that explains, and tests that tell you when it works.
- Part: Ready for every assistant
- 3 tasks
- TypeScript
- In the all labs plan
The first 2 chapters of MCP server project (TypeScript) are free. This one comes with the all labs plan.
Why you need this
Thursday 5 November is the day. Neha uses Claude Desktop; Pranav uses VS Code. In October each of the 4 integrations was set up by hand, with a member's password or an admin's cookie pasted somewhere. Sayali wants the opposite: one server, and a few lines of config that any member can follow, with their own token and nothing else.
Then the server keeps changing. Sayali already wants see_seats' seat_class renamed to class, because it is shorter. That looks harmless. But every assistant that learned seat_class from tools/list keeps sending it: a saved workflow, a prompt, a model's habit. After the rename, those calls fail. The code so far cannot tell a harmless change from one like that, and nothing tells Pranav's VS Code that anything changed.
What you build: 3 tasks
Each task has tests. You write the code in the lab's editor and press Check.
- Task 1
clients.ts: the config files assistants read
Write claudeDesktopConfig({ node, tsx, project, databaseUrl, token }) and vscodeConfig(url) in src/mcp/clients.ts. The first returns { mcpServers: { parda: { command: node, args: ['--import', tsx, '<project>/src/mcp/main.ts', '--stdio'], env: { DATABASE_URL, PARDA_MCP_TOKEN } } } }. The second returns { inputs: [a promptString input parda-token, described "Your Parda MCP token", password true], servers: { parda: { type: 'http', url, headers: { Authorization: 'Bearer ${input:parda-token}' } } } }.
The Check compares both with the files Claude Desktop and VS Code read, then starts the server the way Claude Desktop would, from your config (the command, its arguments and its environment, with Neha's token, from the folder /), lists its tools and calls list_my_bookings.
- Task 2
versions.ts: what breaks
Write breakingChanges(old, now) in src/mcp/versions.ts: for each tool of old in order, "<tool> was removed" when now lacks it; otherwise, for each of its parameters in order, "<tool>: parameter <p> was removed" or "<tool>: parameter <p> changed type" (typeOf differs), then "<tool>: parameter <p> is now required" for each parameter required in now but not in old, sorted.
The Check compares the released tools (contract/tools-1.0.0.json) with changed copies: a tool removed, seat_class renamed to class, showtime_id made a string, part_of_day made required, a new tool and a new optional parameter (no breaking change), and a new description (none).
- Task 3 · interview question
Interview: versions.ts, the next version
Write nextVersion(current, old, now) in src/mcp/versions.ts: MAJOR+1.0.0 when breakingChanges finds anything; MAJOR.MINOR+1.0 when now has a tool old lacks or a tool with a parameter it did not have; MAJOR.MINOR.PATCH+1 for any other difference; current when nothing changed.
The Check asks for the next version of 1.4.2 after each change of Task 2's, and runs npm run release, which compares the server with its contract.
Nikhil will ask: Sayali wants see_seats' seat_class renamed to class. Who breaks, and how would you ship it without breaking them?
What you will learn
- stdio config: Claude Desktop's claude_desktop_config.json, where the client starts the server itself.
- HTTP config: VS Code's .vscode/mcp.json, with an input for the token so the file holds no secret.
- What breaks an old client, and what does not.
- Semantic versioning: what MAJOR.MINOR.PATCH promises.
- The contract file and npm run release.
- The take-home: the whole project, on your own machine.
More in Ready for every assistant
Build "Shipping" yourself
Parda wants AI assistants like Claude Desktop to book seats for its members, safely. You build the MCP server that lets them, and only as the member who allowed it. A real editor and terminal in your browser, AI that explains, and a Check that says when it works.
The first 2 chapters of MCP server project (TypeScript) are free. This one comes with the all labs plan.