Run long work as tasks
읽는 데 약 70분분 걸린다, 8절에 4개 예제이(가) 있음.
AI로 번역함. 영어 원문을 사람이 검증함. 우리가 책을 만드는 방식
영어판 2026.11.14판을 번역한 것이다. 원문 읽기
이 부분은 아직 번역되지 않았으므로 영어로 표시된다.
By the end of this chapter you can negotiate a Model Context Protocol extension, run a slow restock report as a task that the client polls, let tasks expire and cancel them, and say what MCP Apps add to a tool. What the chapter states is true of the specification at revision 2026-07-28 and of mcp 2.3.0, the Python SDK.
Before the shop places its weekly order for kitchen and garden goods with its suppliers, a lead on its support team asks the host for a restock report: every product recounted, and the ones with fewer than 30 units across both warehouses listed for reordering. That is more than a count. The shop's API has a slow endpoint, POST /stock/{sku}/recount, which recounts one product in both warehouses and by default takes 3 seconds. In Serve over Streamable HTTP, the shop's recount_stock tool walks all 64 products through that endpoint and streams a progress report after each one, while the client keeps the HTTP response open.
At the API's default speed, 64 products take more than three minutes, and a call that long has to survive the host's timeout, every proxy between the host and the server, and a lead who closes a laptop. Chapter 6 showed, in Cancel a call the client no longer needs, that a Streamable HTTP client cancels a call by closing its stream, so a call whose connection drops takes its work with it.
Work like this fits another shape that the Model Context Protocol (MCP) offers. With the Tasks extension, the server answers the call at once with a handle to a task: the call's work, whose status the client asks for as often as the server suggests, and whose result waits on the server until the client fetches it. Tasks is an extension, an optional addition to the protocol that both sides must agree to use. This chapter negotiates one, runs the restock report as a task, and ends with when not to.
Every example serves the shop's MCP server over loopback Streamable HTTP, as chapter 6's do, with the shop's API beside it. Setup they share lives in examples/lib/, and two modules there are new. lib.tasks is the book's own small Tasks extension, which Negotiate an extension introduces. lib.restock holds the restock report's work: it recounts every product through chapter 6's lib.recount, sets the task's status message after each one, and lists the products to reorder.
이 부분은 아직 번역되지 않았으므로 영어로 표시된다.
Negotiate an extension
The core protocol is what every client and server must implement. An extension is something the protocol's maintainers, or anyone else, want to standardize without making it mandatory. Extensions became part of the protocol at revision 2026-07-28, when ClientCapabilities and ServerCapabilities gained an extensions field (changelog). The field maps each extension's identifier to a settings object, and an empty one means the extension is supported with no settings. An extension's identifier is a vendor prefix, a slash and a name. Official extensions use the prefix io.modelcontextprotocol, and anyone else uses a reversed domain they own (Extensions overview).
At the pinned revision, a client declares its extensions in every request, under _meta["io.modelcontextprotocol/clientCapabilities"].extensions, the same place it declares every other capability (Carry the version and capabilities on every request). A server lists its own in the result of server/discover (Extensions overview). Both sides leave extensions off by default and need an explicit opt-in. When only one side supports an extension, the specification says that side "MUST either revert to core protocol behavior or reject the request with an appropriate error" (versioning). So an extension is negotiated, not forked: a server that uses one still answers clients that don't.
Extensions also have a lifecycle. A policy adopted in September 2026, after the pinned revision, gives each extension a stage, Experimental, Beta or Stable, or a path into the core protocol (SEP-3392). Tasks is at Beta, to Core, and MCP Apps, which Know what MCP Apps add covers, is Stable (Extensions overview). A Beta extension may still change in ways that break clients.
The Tasks extension's identifier is io.modelcontextprotocol/tasks, and it defines no settings (SEP-2663). The Python SDK, mcp 2.3.0, ships the framework for writing extensions, but not the Tasks extension itself. A server-side extension subclasses mcp.server.extension.Extension, sets identifier, and can add tools, resources and new request methods, or wrap tools/call. A client-side extension is a ClientExtension, which declares the identifier and can claim result shapes that the core protocol doesn't have (mcp/server/extension.py, mcp/client/extension.py).
The SDK has no tasks/get handler and no types for the extension's handle. The task types it does define belong to the experimental tasks of revision 2025-11-25 (mcp_types). The extension's only official SDK package, @modelcontextprotocol/ext-tasks, is TypeScript, and for the pinned revision it covers only the requester, the client side; its receiver support is for the 2025-11-25 tasks. No official package implements the extension's server side at the pinned revision (ext-tasks).
So this book builds a small one. lib.tasks implements, on the SDK's framework, the part of the extension this chapter teaches: a Tasks server extension, a TasksClient client extension, and the methods tasks/get and tasks/cancel. It leaves out tasks/update and pushed notifications, and it keeps tasks in one process's memory. Use it to learn the protocol, and replace it with the SDK's own when a release ships one.
The shop's server passes tasks.Tasks({"restock_report"}) to MCPServer(extensions=[...]), which tells it to answer every call to restock_report with a task. The tool itself calls lib.restock. Serving the shop's server to one client with TasksClient and one without shows both halves of the negotiation; the example reads the first client's declaration off the wire, and the second client also sends one tasks/get.
1"""Declare the Tasks extension on the shop's server, then show what a client gets with it and without it: both declarations, and the2Missing Required Client Capability error a client without it gets from the call and from the task method. The prose's point rests on those two errors."""3import asyncio4import json5import os67from mcp import Client8from mcp.server.mcpserver import MCPServer9from mcp.shared.exceptions import MCPError1011from lib import loopback, restock, shop_api, tasks, wire1213# only restock_report answers with a task; the server's other tools answer as usual14server = MCPServer("shop-support", version="0.7.0", extensions=[tasks.Tasks({"restock_report"})])151617@server.tool(title="Restock report")18async def restock_report(below: int = 30) -> restock.RestockReport:19 """Recount every product's stock and list those with fewer than `below` units. Slow: runs as a task."""20 return await restock.run(below)212223async def main() -> None:24 app = wire.record_http(server.streamable_http_app(), log="declare.jsonl")25 with loopback.serve(shop_api.create_app()) as api_url, loopback.serve(app) as base_url:26 os.environ.update(shop_api.server_env(api_url))27 async with Client(base_url + "/mcp", extensions=[tasks.TasksClient()]) as client:28 print("protocol revision:", client.protocol_version)29 print("server declares:", json.dumps(client.server_capabilities.extensions))30 await client.list_tools()31 async with Client(base_url + "/mcp") as plain:32 try:33 await plain.call_tool("restock_report")34 except MCPError as error:35 print("client without it:", error.error.code, error.error.message)36 # the specification's field, which lists the extensions the client lacked37 print("required:", json.dumps(error.error.data["requiredCapabilities"]))38 try:39 await tasks.get(plain.session, "any-task-id") # the task methods check the declaration too40 except MCPError as error:41 print("tasks/get without it:", error.error.code)42 # the first tools/list the client sent, as the wire trace recorded it43 sent = next(e["request"] for e in wire.read_http_trace("declare.jsonl") if e["request"]["method"] == "tools/list")44 # at this revision a client declares its capabilities in the _meta of each request it sends45 print("client declares:", json.dumps(sent["params"]["_meta"]["io.modelcontextprotocol/clientCapabilities"]))464748asyncio.run(main())
python declare-the-tasks-extension.pyprotocol revision: 2026-07-28
server declares: {"io.modelcontextprotocol/tasks": {}}
client without it: -32021 Client did not declare required extension 'io.modelcontextprotocol/tasks'
required: {"extensions": {"io.modelcontextprotocol/tasks": {}}}
tasks/get without it: -32021
client declares: {"extensions": {"io.modelcontextprotocol/tasks": {}}}
The server declared {"io.modelcontextprotocol/tasks": {}}, and the client with the extension sent {"extensions": {"io.modelcontextprotocol/tasks": {}}} in the _meta of its tools/list request. Both are the identifier with an empty settings object.
The client without the extension called restock_report and got a JSON-RPC error: -32021 Client did not declare required extension 'io.modelcontextprotocol/tasks'. The error's data lists what that client lacked, {"extensions": {"io.modelcontextprotocol/tasks": {}}}. This is the specification's Missing Required Client Capability error, and the SDK's require_client_extension() raises it with the requiredCapabilities field filled in (mcp/server/mcpserver/server.py). The task methods check too. The same client's tasks/get got -32021, because the specification says servers MUST return that error for tasks/get, tasks/update and tasks/cancel from clients that didn't declare the extension (SEP-2663). The SDK doesn't make that check for an extension's own methods, so lib.tasks calls require_client_extension() in each of them.
The shop rejects the call rather than falling back, because the fallback, a plain three-minute call, is the problem this chapter started from. A tool whose work is sometimes short could fall back instead, and answer clients without the extension the ordinary way.
Working rule: Turn an extension on only on a side that implements it, through the SDK's extension classes, never by writing the identifier into capabilities by hand. Decide, for each tool on the server, what a client without the extension gets: an ordinary result when the work can finish within a normal call, and error -32021 when it can't. Check the client's declaration on every request, because at the pinned revision each request declares its own.
이 부분은 아직 번역되지 않았으므로 영어로 표시된다.
Start a task instead of waiting
The client in Negotiate an extension declared that it can handle a task, and declaring is all the client does. The server alone decides, call by call and at the pinned revision, whether to answer with a task. A client that declared the extension "MUST be prepared to handle either CallToolResult or CreateTaskResult" (SEP-2663). The same tool can answer one call at once and the next with a task, and nothing in its definition says which. In the experimental tasks of revision 2025-11-25, the client asked for a task with a task parameter on the request. That design is gone and not wire-compatible with the extension.
Three rules limit the server. It MUST NOT return a task to a client that didn't declare the extension on that request, even if the client declared it on an earlier one. Only tools/call can be answered with a task in this revision. And the server MUST NOT return the handle until the task is durably created, so that a tasks/get for it would already find it (SEP-2663).
A task's handle is a CreateTaskResult: a result whose resultType is "task" instead of "complete". It carries the task's taskId, its status, an optional statusMessage, the timestamps createdAt and lastUpdatedAt, its lifetime in ttlMs, and a suggested pollIntervalMs (Tasks schema). The specification lets extensions add resultType values, and a client MUST treat a value it doesn't recognize as invalid (overview). That rule is why a server never sends a task to a client that hasn't declared the extension.
lib.tasks puts all of this in Tasks.intercept_tool_call, the SDK's one hook around tools/call. For a call to restock_report, it checks the request's declaration, creates a task record with an ID from secrets.token_urlsafe(24), and stores it. Then it starts the tool's ordinary handler in the background and returns the handle. Because the background work runs the same handler as a plain call, the task's result is exactly the CallToolResult a plain call returns. Timestamps come from tasks.Clock, a fake clock that starts on the shop's reference date, 30 June 2026, and moves only when an example moves it, so the output is the same on every run.
This run reuses the server from the previous example and calls restock_report with allow_claimed=True, which returns the handle, not the finished report. It then sends one tasks/get straight after, to check that the server already holds the task.
1"""Call restock_report and keep the handle the server answers with at once, instead of waiting for the report. The tasks/get sent straight after is the line the prose rests on: it finds the task, so the server stored it before the handle left."""2import asyncio3import os45from mcp import Client67from lib import http_mcp, loopback, shop_api, tasks, wire89server = http_mcp.load_server("declare-the-tasks-extension.py") # the shop's server with the Tasks extension101112async def main() -> None:13 app = wire.record_http(server.streamable_http_app(), log="start.jsonl")14 with loopback.serve(shop_api.create_app()) as api_url, loopback.serve(app) as base_url:15 os.environ.update(shop_api.server_env(api_url))16 async with Client(base_url + "/mcp", extensions=[tasks.TasksClient()]) as client:17 # allow_claimed hands back the handle itself, not the result the client would otherwise wait for18 handle = await client.session.call_tool("restock_report", {"below": 30}, allow_claimed=True)19 task = await tasks.get(client.session, handle.task_id)20 print("result type:", handle.result_type)21 print("handle fields:", ", ".join(sorted(handle.model_dump(by_alias=True, exclude_none=True))))22 print("status:", handle.status)23 print("created at:", handle.created_at)24 print("ttl ms:", handle.ttl_ms)25 print("poll interval ms:", handle.poll_interval_ms)26 print("task id length:", len(handle.task_id))27 print("tasks/get straight after:", task["status"])28 exchanges = wire.read_http_trace("start.jsonl")29 get = next(e for e in exchanges if e["request"]["method"] == "tasks/get") # the tasks/get the client sent above30 # the trace stores header names in lowercase, so the lookup uses mcp-name31 assert get["request_headers"].get("mcp-name") == handle.task_id323334asyncio.run(main())
python start-a-restock-report.pyresult type: task
handle fields: _meta, createdAt, lastUpdatedAt, pollIntervalMs, resultType, status, taskId, ttlMs
status: working
created at: 2026-06-30T09:00:00Z
ttl ms: 3600000
poll interval ms: 100
task id length: 32
tasks/get straight after: working
The call came back at once as a task, not the report. Its resultType was task, and its status was working. The handle's fields were _meta, createdAt, lastUpdatedAt, pollIntervalMs, resultType, status, taskId, ttlMs. The _meta field is the SDK's serverInfo stamp, added to every result at the pinned revision (mcp/server/runner.py).
The task was created at 2026-06-30T09:00:00Z on the fake clock. Its ttlMs was 3600000, one hour, and its pollIntervalMs was 100. The tasks/get sent straight after found the task working, which shows the server stored it before the handle left.
The task ID was 32 characters long, which encodes 192 random bits. The specification says task IDs may act as bearer handles, so servers MUST generate them with sufficient entropy that a third party cannot enumerate or guess them (SEP-2663). Over Streamable HTTP, the client MUST also copy the ID into the Mcp-Name header of tasks/get, tasks/update and tasks/cancel, so that a load balancer can route every request for one task the same way. The client's tasks/get carried the task ID in Mcp-Name, because lib.tasks sets name_param = "taskId" on its request classes and the SDK's client fills the header from that field (mcp_types/_types.py).
Working rule: Answer with a task when the work can outlive the connection, and decide per call, not per tool, when some calls are short. Store the task before you return the handle, and generate its ID from a cryptographic random source, with at least 128 bits. Run the same code a plain call runs, so a task's result never differs from a plain result. Never return a task to a request that didn't declare the extension.
이 부분은 아직 번역되지 않았으므로 영어로 표시된다.
Poll a task and fetch its result
The handle from Start a task instead of waiting said the restock report was working. A task has five statuses: working, input_required, completed, failed and cancelled. The completed, failed and cancelled statuses are terminal, and once a task reaches one, its state doesn't change (Tasks overview). failed means a JSON-RPC error. A tool that ran and returned a result with isError: true ends completed, with that result inside, and the specification says failed MUST NOT be used for it (SEP-2663). It is the same split chapter 3 drew between tool execution errors and protocol errors, in Report failures as tool results.
The client finds out where a task stands by polling. It sends tasks/get with the taskId, and it SHOULD wait the server's pollIntervalMs between polls, a value that may change from one reply to the next. Servers MAY rate-limit clients that poll faster. Each reply is the task, with resultType "complete". When the task has completed, the reply carries result, which has the same structure as the result type of the original request (SEP-2663; Tasks schema). For a tool, that is a CallToolResult. Clients SHOULD store task IDs durably, so that polling can resume after a crash or a restart.
A server may also push status changes. The client subscribes with subscriptions/listen for the task IDs it holds, and the server sends notifications/tasks, each carrying the full task. Polling stays the default (Tasks overview), and lib.tasks implements only polling. A task that needs the user's input moves to input_required and carries input requests shaped like a Multi Round-Trip Request's (Return an input request instead of a result), which the client answers with tasks/update. lib.tasks doesn't implement that either, and the restock report never asks.
In the SDK, polling belongs in a client extension. TasksClient claims the result type "task" with a ResultClaim. The claim's resolver gets the handle and a session for follow-up requests, and it must return the call's ordinary CallToolResult (mcp/client/extension.py). The resolver waits pollIntervalMs, sends tasks/get, and repeats until the task is terminal. Client.call_tool then returns the result as if the call had been plain. A client without a claim for "task" can't parse the handle: the SDK validates it as a CallToolResult and raises pydantic's ValidationError. UnexpectedClaimedResult, which carries the handle, is for a client that has the claim but calls session.call_tool without allow_claimed=True (mcp/client/session.py).
A host makes this call when a lead asks for the restock report. Through TasksClient, with on_poll= set to keep every tasks/get reply, a client calls restock_report with a threshold of 30 units.
1"""Call restock_report through a client whose extension polls the task until it ends, and get the report back as an ordinary tool result. The asserts check that the report was still working on more than one poll and that its messages only counted up, which the prose relies on."""2import asyncio3import os45from mcp import Client67from lib import http_mcp, loopback, shop_api, tasks89server = http_mcp.load_server("declare-the-tasks-extension.py") # the shop's server with the Tasks extension101112async def main() -> None:13 polls = []14 with loopback.serve(shop_api.create_app()) as api_url, loopback.serve(server.streamable_http_app()) as base_url:15 os.environ.update(shop_api.server_env(api_url))16 # on_poll keeps every tasks/get reply, in the order the client received them17 async with Client(base_url + "/mcp", extensions=[tasks.TasksClient(on_poll=polls.append)]) as client:18 result = await client.call_tool("restock_report", {"below": 30})19 statuses = [p["status"] for p in polls]20 # dict.fromkeys drops repeated statuses but keeps their order, so each status is listed once21 print("statuses:", " then ".join(dict.fromkeys(statuses)))22 assert statuses.count("working") > 1, statuses23 # the second word of "recounted N of 64 SKUs" is N24 counted = [int(p["statusMessage"].split()[1]) for p in polls if "statusMessage" in p]25 assert counted == sorted(counted), counted26 print("last message:", polls[-1]["statusMessage"])27 print("result type:", type(result).__name__)28 report = result.structured_content29 print("skus recounted:", report["skus"])30 print("to reorder:", len(report["reorder"]))31 # the first of the products the report lists for reordering32 print("first to reorder:", "{sku}, {units} units".format(**report["reorder"][0]))333435asyncio.run(main())
python poll-the-restock-report.pystatuses: working then completed
last message: recounted 64 of 64 SKUs
result type: CallToolResult
skus recounted: 64
to reorder: 5
first to reorder: KG-1018, 2 units
The polls show the statuses in order: working then completed. It was still working on more than one poll, its status messages only counted up, and the last one read "recounted 64 of 64 SKUs". The number of polls varies with the machine's speed, so the example prints none.
What came back from Client.call_tool was a CallToolResult. The report recounted 64 products and listed 5 to reorder, the first being KG-1018, 2 units. The code that made the call never saw a task, which is the point of the claim: a host written against plain tool calls, such as the one in Build a host that works through tickets, gets tasks by adding one extension to its client.
Working rule: Poll at the server's pollIntervalMs, re-read it on every reply, and stop at the first terminal status. Treat completed as the original call's result, isError and all, and failed as a protocol error. Hide the polling in a client extension so the rest of the host sees plain calls. When a host must survive a restart, store each task ID before the first poll, and resume from it.
이 부분은 아직 번역되지 않았으므로 영어로 표시된다.
Expire and cancel tasks
The restock report in Poll a task and fetch its result finished and was fetched. Not every task is. A client may crash and never come back, or a lead may close a report they no longer need, and a server that keeps every task forever runs out of storage. The extension gives a task two ways to end early: its lifetime runs out, or the client cancels it.
A task's lifetime is its ttlMs, counted from createdAt, or null for no limit, and the server may change it. After the TTL elapses, servers MAY mark a task failed at any point, and later delete it at any time. A server that has purged a task must answer a tasks/get for it with error -32602, Invalid Params, and it may say the task can't be found rather than that it expired (SEP-2663). So a client can't count on a result outliving the TTL, however the task went.
Cancelling uses tasks/cancel with the taskId, and the specification says notifications/cancelled MUST NOT be used for it. The reply is an empty acknowledgement, and it promises nothing more: "A server is not obligated to actually stop the work; it is only obligated to acknowledge the request." The task may stay working for a while, and it may still end completed or failed. Once it has sent the cancel, the client may forget the task (SEP-2663). This is cooperative cancellation, unlike chapter 6's, where closing the stream cancelled the call's work in the server (Cancel a call the client no longer needs).
lib.tasks makes both concrete. On a tasks/get after the TTL, it deletes the task, stops its work, and answers -32602 with the message the specification's example uses. On tasks/cancel, it sets a flag and acknowledges. The tool's work reads the flag through tasks.cancel_requested(), and lib.restock checks it after each product, so the restock report stops at the end of the product it is recounting, and the task becomes cancelled then.
The expiry example sets a one-minute ttlMs, which shows expiry without a long wait. So that its output never depends on the machine's speed, it holds each report before every product, with restock.Steps, a gate in lib.restock that lets one more product start each time allow() is called. It starts one report that is never allowed a product, polls it, moves the fake clock 61 seconds on, and polls again. Then it starts a second report, lets it recount one product, waits for its first status message, and cancels it. It polls at once, lets the report start its next product, and polls until the task is terminal.
1"""Show the two ways a task ends early: its time to live runs out and the server purges it, or the client cancels it and the report stops at its next check. The -32602 from the purged task and the final status of the cancelled report are the lines the prose rests on."""2import asyncio3import os45from mcp import Client6from mcp.server.mcpserver import MCPServer7from mcp.shared.exceptions import MCPError89from lib import loopback, restock, shop_api, tasks1011clock = tasks.Clock() # fake time: moves only when the example says so12first_steps, second_steps = restock.Steps(), restock.Steps() # a report starts a product only when allowed13pending = [first_steps, second_steps] # one per call, in call order14# a task expires one minute after it was created, counted on the fake clock15server = MCPServer("shop-support", version="0.7.0",16 extensions=[tasks.Tasks({"restock_report"}, ttl_ms=60_000, clock=clock)])171819@server.tool(title="Restock report")20async def restock_report(below: int = 30) -> restock.RestockReport:21 """Recount every product's stock and list those with fewer than `below` units. Slow: runs as a task."""22 # calls arrive in order, so each report takes the next gate23 return await restock.run(below, steps=pending.pop(0))242526async def main() -> None:27 with loopback.serve(shop_api.create_app()) as api_url, loopback.serve(server.streamable_http_app()) as base_url:28 os.environ.update(shop_api.server_env(api_url))29 async with Client(base_url + "/mcp", extensions=[tasks.TasksClient()]) as client:30 first = await client.session.call_tool("restock_report", allow_claimed=True)31 print("first, ttl ms:", first.ttl_ms) # first_steps allows no product, so it stays working32 print("first, first poll:", (await tasks.get(client.session, first.task_id))["status"])33 clock.advance(61) # 61 seconds: past the one-minute time to live34 try:35 await tasks.get(client.session, first.task_id)36 except MCPError as error:37 print("first, 61 s later:", error.error.code, error.error.message)38 second = await client.session.call_tool("restock_report", allow_claimed=True)39 second_steps.allow() # product 1 only: the report then waits before product 240 task = await tasks.poll_until(client.session, second.task_id, lambda t: "statusMessage" in t)41 print("second, before cancel:", task["status"] + ",", task["statusMessage"])42 ack = await tasks.cancel(client.session, second.task_id)43 print("cancel acknowledged, besides _meta:", ", ".join(f"{k} {v}" for k, v in ack.items() if k != "_meta"))44 print("second, right after:", (await tasks.get(client.session, second.task_id))["status"])45 second_steps.allow() # product 2 starts; the check after it sees the cancel46 task = await tasks.poll_until(client.session, second.task_id, lambda t: t["status"] in tasks.TERMINAL)47 print("second, finally:", task["status"] + ",", task["statusMessage"])484950asyncio.run(main())
python expire-a-task.pyfirst, ttl ms: 60000
first, first poll: working
first, 61 s later: -32602 Failed to retrieve task: Task has expired
second, before cancel: working, recounted 1 of 64 SKUs
cancel acknowledged, besides _meta: resultType complete
second, right after: working
second, finally: cancelled, stopped after 2 of 64 SKUs
The first task's ttlMs was 60000, and it was working on its first poll. After 61 seconds on the fake clock, tasks/get answered -32602 Failed to retrieve task: Task has expired. On that poll, lib.tasks stopped the first task's work too, and its result would have gone with it had the work finished.
The second task was working, recounted 1 of 64 SKUs when the client cancelled it. Besides the SDK's _meta stamp, the acknowledgement held only resultType complete: an empty result, apart from the field every result carries. A poll straight after found the task still working, because the cancel only set a flag and the report hadn't reached its next check. In the shop, that check comes after the current product's recount; in the example, the report was held before its second product.
The last poll found cancelled, stopped after 2 of 64 SKUs. The report recounted one more product after the cancel, then stopped, as the specification allows.
Working rule: Give every task a TTL that covers the longest wait you expect between the work finishing and the client fetching it, and purge after it; for the shop's restock report, that is an hour. Make long work check for cancellation at each natural step, such as each product, and clean up there. In the client, treat a cancel's acknowledgement as "asked", not "stopped", and treat -32602 from tasks/get as a task that is gone for good.
이 부분은 아직 번역되지 않았으므로 영어로 표시된다.
Know what MCP Apps add
Tasks change when a tool's result arrives, as Start a task instead of waiting showed. MCP Apps is an official extension that changes how a result is shown. Its identifier is io.modelcontextprotocol/ui. A tool names a user interface in _meta.ui.resourceUri: a ui:// resource, served with the MIME type text/html;profile=mcp-app. A host that supports Apps renders that HTML in a sandboxed iframe, and talks to it only through postMessage, in JSON-RPC: MCP's own methods, such as tools/call, plus methods whose names start with ui/. Through the host, the app can call the server's tools (MCP Apps; Apps specification).
A tool's _meta.ui.visibility says who may call it, ["model", "app"] by default. A tool for the app alone is hidden from the model. The Apps specification puts both directions on the host: it MUST NOT include such a tool in the model's tool list, and it MUST reject an app's call to a tool whose visibility leaves out "app" (Apps specification). A UI-enabled tool should still return meaningful text for clients that don't support the extension (Extensions overview).
The Apps specification is dated 2026-01-26 and marked Stable, and its negotiation examples use the 2025 initialize handshake. At the pinned revision, a client declares Apps per request, like any extension (Negotiate an extension). Unlike Tasks, Apps ships in the Python SDK, in mcp.server.apps. Apps() is the extension, @apps.tool(resource_uri=...) declares a UI-enabled tool, apps.add_html_resource() serves the HTML, and client_supports_apps(ctx) says whether this request's client declared Apps with the right MIME type (mcp/server/apps.py).
The restock report is a candidate. As an app, it could show the products to reorder as a table, with a button beside each that adds the product to the supplier order. That button would call a tool such as add_to_supplier_order, with a visibility of ["app"], so that the model never places orders on its own. The report would keep its text and structured content, so a host without Apps would read the same report as in Poll a task and fetch its result. The book doesn't build this view, because its host loop in chapter 10 has no screen, and an Apps view needs one to render it.
MCP Apps and elicitation do different jobs. Elicitation is the server asking the user one question in the middle of a call, through the client's own form (Ask for structured input with elicitation). An app is a view of a tool's result, which the server writes and the host renders.
Working rule: Reach for MCP Apps when a result needs more than text to act on, such as a table to sort or a choice per row, and the hosts your users run support the extension. Keep every UI-enabled tool's text result complete, so a host without Apps loses only the view. Give app-only tools a visibility of ["app"] when the model shouldn't call them, and remember that the host enforces it, not your server.
작업, 진행 상황, 일반 호출 중에서 고르기
이제 상점은 세 가지 방식으로 작업을 실행한다. get_order_status와 같은 일반 호출, 6장의 recount_stock처럼 진행 상황을 스트리밍하는 호출, 그리고 작업을 폴링하고 결과 가져오기의 재입고 보고서 같은 작업이다. 이 방식들은 연결이 무엇을 견뎌야 하는지, 그리고 호출자가 기다리는 동안 무엇을 볼 수 있는지에서 서로 다르다.
대부분의 선택은 진행 상황에서 갈린다. 이 개정판 시점에서 사양은 작업 전반에 대해 notifications/progress나 notifications/message를 지원하지 않는다(SEP-2663). 작업은 클라이언트가 폴링할 때 읽는 statusMessage를 통해서만 어디까지 진행했는지 알린다. 재입고 보고서의 "64개 SKU 중 12개 재집계"가 그런 메시지다. 이것은 클라이언트가 폴링하는 만큼만 보이는 문자열이며, 진행률 표시줄에 쓸 수 있는 숫자는 없다. 로그 메시지로는 이를 우회할 수 없다(샘플링, 루트, 로깅 대체하기).
또 하나의 차이는 어느 쪽이 무엇을 지원해야 하느냐이다. 일반 호출과 진행 상황은 핵심 프로토콜이다. 작업은 양쪽 모두 확장을 구현해야 하며, 확장에 대한 호스트의 지원은 제각각이다(확장 지원 매트릭스). 작업 개요는 작업이 맞는 경우를 나열한다. 연결보다 오래 지속되는 작업, 클라이언트를 다시 시작해도 살아남아야 하는 작업, 이미 큐에서 잡으로 실행되는 작업이다.
다음 표는 우리의 경험칙으로 세 방식을 비교한 것이며, 측정값은 아니다.
| 일반 호출 | 진행 상황 | 작업 | |
|---|---|---|---|
| 일반적인 길이 | 수 초 | 최대 수 분 | 수 분 이상 |
| 연결을 계속 열어 두어야 함 | 예 | 예 | 아니요 |
| 기다리는 동안 호출자가 보는 것 | 없음 | 진행 상황과 전체 양 | 상태 메시지 |
| 클라이언트 재시작 후에도 유지 | 아니요 | 아니요 | 예, 클라이언트가 ID를 저장한 경우 |
| 확장 필요 | 아니요 | 아니요 | 예, 양쪽 모두 |
get_order_status는 밀리초 안에 응답하므로 일반 호출로 둔다. recount_stock는 6장의 진행 상황을 유지한다. 이를 시작한 책임자가 숫자가 올라가는 것을 지켜보며 기다리기 때문이다. 재입고 보고서는 작업이 된다. API의 실제 속도로는 몇 분이 걸리고, 책임자는 지켜보기보다 나중에 결과를 받기를 원하며, 연결이 끊겼다고 3분간의 재집계가 헛수고가 되어서는 안 되기 때문이다.
작업 규칙: 호스트와 서버 사이의 모든 타임아웃보다 결과가 충분히 일찍 돌아온다면 일반 호출을 사용한다. 작업이 길고, 호출자가 계속 열려 있으리라 믿을 수 있는 연결에서 기다리며, 보여 줄 숫자를 원한다면 진행 상황을 사용한다. 작업이 연결보다 오래 지속될 수 있거나 호출자가 떠났다가 돌아오려 한다면 작업을 사용한다. 작업은 상태 메시지만 보고한다는 점을 받아들이고, 확장이 없는 클라이언트를 위해 일반 호출 대체 경로를 두거나 분명한 -32021을 반환한다.
이 부분은 아직 번역되지 않았으므로 영어로 표시된다.
What goes wrong in production
The restock report in this chapter ran in one process, with tasks in memory and a fake clock. Spread across replicas, run for days and called by many users, it can fail in the ways that follow, each with a sign you can look for.
Tasks are stored on one replica. lib.tasks keeps tasks in a dictionary. Behind chapter 6's two replicas (Run replicas without sticky sessions), a tasks/get that reaches the other replica finds nothing and answers -32602. Store tasks where every replica can read them, such as a database or a job queue's own store, or route on the Mcp-Name header, which carries the task ID on every task request. You'll notice it as tasks that "expire" within seconds, at about the rate your load balancer switches replicas.
Task IDs leak another caller's result. A task ID can be the only thing between a caller and a stored result. Servers MUST perform authentication and authorization checks on each task-related request, the specification says, and it removed tasks/list, which, scoped badly, could show one caller another's task IDs (SEP-2663). Record the caller with the task, from the token's subject once Authorize clients with OAuth is in place, and refuse every tasks/get and tasks/cancel from anyone else. An input request that arrives through a task gets the same trust as one in a direct call, and no more: "A task is not a higher-trust channel."
The SDK doesn't check the declaration for you. In mcp 2.3.0, the server runner passes an extension's resultType through unchecked, and a note in the source says that rejecting it for clients that didn't declare the extension is still to do (mcp/server/runner.py). The extension must call require_client_extension() itself, on the call and on each of its own methods, as lib.tasks does. A client that didn't declare Tasks and gets a task anyway must treat the result as invalid. The SDK's client does, because without a claim for "task" it validates the handle as a CallToolResult and raises a ValidationError.
Polling costs more than the work. Thousands of clients polling every 100 milliseconds make a load of their own. Raise pollIntervalMs as a task runs longer, rate-limit clients that ignore it, as the specification allows, and offer notifications/tasks once your server can push. The sign is tasks/get outnumbering every other method in your traces.
Tasks pile up. A TTL of null, or one longer than any client waits, keeps every abandoned task's result. Set a TTL, purge on a schedule as well as on read, and alert on the number of stored tasks. Clients that lose task IDs on restart make the pile grow faster, so store IDs on the client before the first poll.
Cancelled work keeps running. A tool that never checks for cancellation runs to the end after every tasks/cancel, and the shop's API recounts products nobody wants. Check at each step, and log how long tasks run after a cancel.
Clients speak the 2025-11-25 tasks. That revision's experimental tasks used tasks/result, tasks/list and a task parameter on the request, and they aren't wire-compatible with the extension (SEP-2663). A 2025-era client never declares io.modelcontextprotocol/tasks, so it meets the server's -32021. Migrate a 2025-era server covers the rest of the old protocol.
The extension changes under you. Tasks is Beta and on its way into the core protocol, and the SDK may ship its own Tasks extension in a later release. Either is an update trigger for this chapter. When the SDK ships one, replace lib.tasks with it and keep the shop's tool as it is, since the tool never knew it ran as a task.
Working rule: Move tasks' storage to where every replica can read it before they go to production, record each task's owner and check it on every task request, and set a TTL with a purge that runs on a schedule. Then watch -32602 from tasks/get by replica, the ratio of tasks/get to tools/call, the number of stored tasks, and how long work runs after a cancel.
이 부분은 아직 번역되지 않았으므로 영어로 표시된다.
Decisions this chapter made
- The shop's restock report runs as a task, through the Tasks extension, because its work outlives a connection.
- The shop's server refuses
restock_reportwith error -32021 for clients without the extension, instead of running a three-minute plain call. - The book builds its own small Tasks extension,
lib.tasks, on the SDK's extension framework, becausemcp2.3.0 ships none. It implementstasks/getandtasks/cancel, and leaves outtasks/updateand pushed notifications. - A task runs the tool's ordinary handler, so its result is the same
CallToolResulta plain call returns. - Task IDs carry 192 random bits, and every task request carries its ID in the
Mcp-Nameheader. - The client polls at the server's
pollIntervalMsinside a client extension, so the host sees plain tool calls. - Tasks expire one hour after they are created, and cancelling is cooperative: the restock report checks after each product.
recount_stockkeeps chapter 6's progress, andget_order_statusstays a plain call.- MCP Apps are described, not built, because the book's host loop renders no HTML. A restock view would keep the report's text, and hide its ordering tool from the model with a visibility of
["app"]. - In production, tasks move to storage that both of chapter 6's replicas share, and every task request is checked against the caller who started the task.
- The lesson is where the waiting goes: a task moves it off the connection and onto the server, which keeps the state, sets how long it lasts, and decides who may read it.
이 판의 이 장
2026.11.14판예제 통과 2026년 11월 19이 장에서 4개 예제개 중 4개가 통과한다
영어판 2026.11.14판을 번역한 것이다.