FastMCP context¶

Add FastMCPProvider() to expose FastMCP operation objects through Dishka's normal from_context mechanism.

from dishka import make_async_container
from fastmcp import Context, FastMCP

from dishka_fastmcp import (
    FastMCPProvider,
    FromDishka,
    dishka_lifespan,
    inject,
    setup_dishka,
)

container = make_async_container(FastMCPProvider())
mcp = FastMCP('app', lifespan=dishka_lifespan(container))
setup_dishka(container, mcp)


@mcp.tool
@inject
async def notify(message: str, ctx: FromDishka[Context]) -> None:
    await ctx.info(message)

Available objects¶

All entries are request-scoped and resolved only when requested:

Use Context for request IDs, client logging, progress reporting, resource access, sampling, elicitation, and session state. When a child server is mounted, the injected FastMCP value is the server that owns the executing component.

Using context in providers¶

Dependencies can consume the same context without coupling the handler to the FastMCP decorator:

from dishka import Provider, Scope, provide
from fastmcp import Context


class RequestProvider(Provider):
    @provide(scope=Scope.REQUEST)
    def request_id(self, context: Context) -> str:
        return context.request_id

Operation arguments¶

FastMCPProvider does not register CallToolRequestParams, ReadResourceRequestParams, or GetPromptRequestParams. Receive tool and prompt arguments in the handler signature, receive resource parameters from the resource URI template, and use Context for request metadata.