context
Context
Bases: BaseModel, Generic[LifespanContextT, RequestT]
Context object providing access to MCP capabilities.
This provides a cleaner interface to MCP's RequestContext functionality. It gets injected into tool and resource functions that request it via type hints.
To use context in a tool function, add a parameter with the Context type annotation:
@server.tool()
async def my_tool(x: int, ctx: Context) -> str:
# Log messages to the client
await ctx.info(f"Processing {x}")
await ctx.debug("Debug info")
await ctx.warning("Warning message")
await ctx.error("Error message")
# Report progress
await ctx.report_progress(50, 100)
# Access resources
data = await ctx.read_resource("resource://data")
# Get request info
request_id = ctx.request_id
client_id = ctx.client_id
return str(x)
The context parameter name can be anything as long as it's annotated with Context. The context is optional - tools that don't need it can omit the parameter.
Source code in src/mcp/server/mcpserver/context.py
32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 | |
request_context
property
request_context: ServerRequestContext[
LifespanContextT, RequestT
]
Access to the underlying request context.
report_progress
async
Report progress for the current operation.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
progress
|
float
|
Current progress value (e.g., 24) |
required |
total
|
float | None
|
Optional total value (e.g., 100) |
None
|
message
|
str | None
|
Optional message (e.g., "Starting render...") |
None
|
Source code in src/mcp/server/mcpserver/context.py
114 115 116 117 118 119 120 121 122 | |
notify_tools_changed
async
notify_tools_changed() -> None
Publish a tools list-changed event to subscriptions/listen subscribers.
Source code in src/mcp/server/mcpserver/context.py
130 131 132 | |
notify_prompts_changed
async
notify_prompts_changed() -> None
Publish a prompts list-changed event to subscriptions/listen subscribers.
Source code in src/mcp/server/mcpserver/context.py
134 135 136 | |
notify_resources_changed
async
notify_resources_changed() -> None
Publish a resources list-changed event to subscriptions/listen subscribers.
Source code in src/mcp/server/mcpserver/context.py
138 139 140 | |
notify_resource_updated
async
Publish a resource-updated event for uri to subscriptions/listen subscribers.
The URI is matched as an exact string against each stream's filter.
Reaches subscriptions/listen streams only; clients on earlier
protocol versions that used resources/subscribe are notified via
ctx.session.send_resource_updated(uri) instead.
Source code in src/mcp/server/mcpserver/context.py
142 143 144 145 146 147 148 149 150 | |
read_resource
async
read_resource(
uri: str | AnyUrl,
) -> Iterable[ReadResourceContents]
Read a resource by URI.
This is a content reader: an InputRequiredResult returned by a
resource template function (the 2026-07-28 multi-round-trip flow)
raises here, and the nested template never sees this request's
input_responses/request_state — those answer the outer handler's
own questions, so the template always behaves as round one. A handler
that wants to receive and forward an InputRequiredResult as its own
result calls MCPServer.read_resource(uri, context) instead — but
not from a tool whose dependencies elicit via Resolve(...): the
resolver owns that tool's request_state channel, and a forwarded
result's state would clobber it.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
uri
|
str | AnyUrl
|
Resource URI to read |
required |
Returns:
| Type | Description |
|---|---|
Iterable[ReadResourceContents]
|
The resource content as either text or bytes |
Raises:
| Type | Description |
|---|---|
ResourceNotFoundError
|
If no resource or template matches the URI. |
ResourceError
|
If template creation or resource reading fails. |
RuntimeError
|
If the resource returned an |
Source code in src/mcp/server/mcpserver/context.py
152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 | |
elicit
async
Elicit information from the client/user.
This method can be used to interactively ask for additional information from the client within a tool's execution. The client might display the message to the user and collect a response according to the provided schema. If the client is an agent, it might decide how to handle the elicitation -- either by asking the user or automatically generating a response.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
message
|
str
|
Message to present to the user |
required |
schema
|
type[ElicitSchemaModelT]
|
A Pydantic model class defining the expected response structure. According to the specification, only primitive types are allowed. |
required |
Returns:
| Type | Description |
|---|---|
ElicitationResult[ElicitSchemaModelT]
|
An ElicitationResult containing the action taken and the data if accepted |
Note
Check the result.action to determine if the user accepted, declined, or cancelled. The result.data will only be populated if action is "accept" and validation succeeded.
Source code in src/mcp/server/mcpserver/context.py
186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 | |
elicit_url
async
Request URL mode elicitation from the client.
This directs the user to an external URL for out-of-band interactions that must not pass through the MCP client. Use this for: - Collecting sensitive credentials (API keys, passwords) - OAuth authorization flows with third-party services - Payment and subscription flows - Any interaction where data should not pass through the LLM context
The response indicates whether the user consented to navigate to the URL.
The actual interaction happens out-of-band. When the elicitation completes,
call ctx.session.send_elicit_complete(elicitation_id) to notify the client.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
message
|
str
|
Human-readable explanation of why the interaction is needed |
required |
url
|
str
|
The URL the user should navigate to |
required |
elicitation_id
|
str
|
Unique identifier for tracking this elicitation |
required |
Returns:
| Type | Description |
|---|---|
UrlElicitationResult
|
UrlElicitationResult indicating accept, decline, or cancel |
Source code in src/mcp/server/mcpserver/context.py
219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 | |
log
async
log(
level: LoggingLevel,
data: Any,
*,
logger_name: str | None = None
) -> None
Send a log message to the client.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
level
|
LoggingLevel
|
Log level (debug, info, notice, warning, error, critical, alert, emergency) |
required |
data
|
Any
|
The data to be logged. Any JSON serializable type is allowed (string, dict, list, number, bool, etc.) per the MCP specification. |
required |
logger_name
|
str | None
|
Optional logger name |
None
|
Source code in src/mcp/server/mcpserver/context.py
254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 | |
client_id
property
client_id: str | None
Get the client ID if available.
Note: this reads from the MCP request's _meta params, not the OAuth
bearer token. For that, use get_access_token().client_id.
headers
property
Request headers carried by this message, when the transport has them.
Populated by HTTP-based transports; None on stdio or when the
transport's request object carries no headers. Headers are
client-supplied input - never treat one as an identity assertion.
protocol_version
property
protocol_version: str | None
The negotiated protocol version, or None outside of an active request.
input_responses
property
input_responses: InputResponses | None
Client responses to a prior InputRequiredResult.input_requests.
None on the initial round, or when the client retried without
responses.
request_state
property
request_state: str | None
Opaque state echoed from a prior InputRequiredResult.request_state.
None on the initial round.
client_capabilities
property
client_capabilities: ClientCapabilities | None
The client's declared capabilities for this connection.
None when the client supplied no client info (e.g. an anonymous
stateless request without the reserved _meta keys).
session
property
session
Access to the underlying session for advanced usage.
close_sse_stream
async
close_sse_stream() -> None
Close the SSE stream to trigger client reconnection.
This method closes the HTTP connection for the current request, triggering client reconnection. Events continue to be stored in the event store and will be replayed when the client reconnects with Last-Event-ID.
Use this to implement polling behavior during long-running operations - the client will reconnect after the retry interval specified in the priming event.
Note
This is a no-op if not using StreamableHTTP transport with event_store. The callback is only available when event_store is configured.
Source code in src/mcp/server/mcpserver/context.py
340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 | |
close_standalone_sse_stream
async
close_standalone_sse_stream() -> None
Close the standalone GET SSE stream to trigger client reconnection.
This method closes the HTTP connection for the standalone GET stream used for unsolicited server-to-client notifications. The client SHOULD reconnect with Last-Event-ID to resume receiving notifications.
Note
This is a no-op if not using StreamableHTTP transport with event_store. Currently, client reconnection for standalone GET streams is NOT implemented - this is a known gap.
Source code in src/mcp/server/mcpserver/context.py
357 358 359 360 361 362 363 364 365 366 367 368 369 370 | |
debug
async
Send a debug log message.
Source code in src/mcp/server/mcpserver/context.py
373 374 375 376 | |
info
async
Send an info log message.
Source code in src/mcp/server/mcpserver/context.py
378 379 380 381 | |
warning
async
Send a warning log message.
Source code in src/mcp/server/mcpserver/context.py
383 384 385 386 | |
error
async
Send an error log message.
Source code in src/mcp/server/mcpserver/context.py
388 389 390 391 | |