An MCP Server for Your Service|INEMA.CLUB-PRO

WebMCP Track · course 1 of 6 · 8 lessons

An MCP server for your service, tested and on the current revision

Tools the agent calls, with confirmation when there are consequences, a token when it's remote, and an automated test at the end. All on the 2026-07-28 revision of MCP, with the official SDK (v2, 2.3.1), in a kit that runs on your machine at no cost and with no key.

Start with lesson 1 See the track area
An MCP server for your service: a laptop with a terminal and a small server with a cable plugged in, on a dark desk.
  • 8short lessons
  • 2026-07-28MCP revision taught
  • 2.3.1official SDK version in the kit
  • 0API keys and cost

The lessons

Each lesson ends with a command you run and an output you can check. The kit lives in the course's own repository.

  1. Lesson 1 · 15 minAnatomy: tools, resources, and prompts; client, server, and transportBefore you write code, separate the pieces. The MCP server offers three things (tools, resources, and prompts), the client lives inside the app with the model, and the transport is just the pipe. In this lesson you connect a client to the kit's server and see each piece listed.
  2. Lesson 2 · 20 minFirst stdio server with the official SDK, tested in the InspectorThe simplest way to connect a service to an agent is stdio: the client starts your program and talks to it over stdin and stdout. In this lesson you install the kit with pinned versions, read the class server, and call the tool two ways: with a test client and with the MCP Inspector in command-line mode.
  3. Lesson 3 · 20 minDesigning a good tool: name, description, JSON Schema, idempotency, read-only × with consequencesThe model picks the tool by reading its name, description, and schema. The client decides whether to ask for approval by reading the annotations. A badly designed tool gets called at the wrong time or with the wrong argument. In this lesson, you use a script to check that your tools say what they do and what they change.
  4. Lesson 4 · 20 minStateless Streamable HTTP: server/discover, Mcp-Method and Mcp-Name headersFor the service to handle many clients at one URL, the transport is Streamable HTTP. In the 2026-07-28 revision it became stateless: no session to keep, each request carries what it needs. In this lesson you bring up the same server over HTTP and talk to it with curl, even making mistakes on purpose.
  5. Lesson 5 · 20 minAsking the user for input in the middle of the call: MRTR (InputRequiredResult)Book, pay, delete: an action with consequences needs a yes from a person. In the 2026-07-28 revision, the server no longer opens its own request to ask. It returns input_required, the client asks the user, and repeats the call with the answer. In this lesson you see both rounds and the path of the no.
  6. Lesson 6 · 20 minAuthorization: OAuth with iss (RFC 9207), minimum scope, secret kept out of the repoAn HTTP server on the internet without a token is an open tool for anyone. In MCP, your server is an OAuth resource server: it doesn't issue tokens, it only checks them. In this lesson you protect the kit's server, see the 401 that starts the client's login, and give each token only the scope it needs.
  7. Lesson 7 · 15 minMCP Apps: interface inside the client (official extension)Sometimes text is not enough: a list with colors, a chart, a form. MCP Apps is the official extension that links a tool to an HTML page that the client draws in an isolated iframe. In this lesson you link a panel to the ver_turmas tool and check the link without needing to open a client.
  8. Lesson 8 · 20 minConnect to Claude Code/Codex, automatic tests and Registry (preview)A server is ready when your agent uses it and a test checks it on every change. In this lesson you run the kit's automatic test suite, connect the server to Claude Code and to Codex from your subscription, and prepare the server.json for the official Registry, which is still in preview. It closes with the map and your plan.

Who it's for

  1. 1Devs who run Node and a terminal and want their service to be used by agents (Claude Code, Codex, and other MCP clients).
  2. 2Anyone with an MCP server built in 2025 with SSE, session, and initialize who needs to know what changed.
  3. 3If you prefer Python: the concepts apply equally; the course uses Node (the Python SDK mcp 2.3.0 contains server/discover in its code, with no hands-on practice here).

What you'll build

  1. 1A server with a read-only tool, a tool with consequences, a resource, and a prompt.
  2. 2The same code over stdio and over stateless Streamable HTTP, with a Host and Origin guard.
  3. 3User confirmation mid-call (MRTR) and a token with minimum scope per tool.
  4. 4An MCP Apps interface, the test suite, and the server hooked up to Claude Code and Codex.

Where this course fits in the WebMCP Track

  1. 1Course 0 shows how agents use a site; this one is the server side (backend).
  2. 2Course 2 brings tools into the page with WebMCP; course 4 goes deeper into threats.
  3. 3Autonomous-loop threats and in-depth evals belong to the LOOP-R Engenharia Track.