`@app.resource()` does not accept `ctx: Context`

[Kludex]

I'm having this exception:

Traceback (most recent call last):
 File "/Users/marcelotryle/dev/pydantic/logfire-mcp/main.py", line 121, in <module>
 @mcp.resource("schema://records")
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 File "/Users/marcelotryle/dev/pydantic/logfire-mcp/.venv/lib/python3.12/site-packages/mcp/server/fastmcp/server.py", line 383, in decorator
 raise ValueError(
ValueError: Mismatch between URI parameters set() and function parameters {'ctx'}

When I have this resource:

@mcp.resource("schema://records")
async def get_logfire_records_schema(ctx: Context) -> str: ...

It seems the ctx is not being taken in consideration.

cc @jlowin

[luarss]

Not a fix, but a potential workaround:

@mcp.resource("schema://records")
async def get_logfire_records_schema() -> str:
 ctx = mcp.get_context()

[jlowin]

Sorry just seeing this - this is well-supported now in FastMCP v2 https://gofastmcp.com/servers/context#resources-and-templates

[RubenCristino]

Sorry just seeing this - this is well-supported now in FastMCP v2 https://gofastmcp.com/servers/context#resources-and-templates

'm experiencing the same issue as others:
mismatch between uri parameters set() and function parameters {'ctx'}

I'm currently using the following version of the fastmcp package:
Version: 2.10.6

Despite having the latest version, the error persists even when following the documented examples.

[RubenCristino]

I'm having this exception:

Traceback (most recent call last):
File "/Users/marcelotryle/dev/pydantic/logfire-mcp/main.py", line 121, in
@mcp.resource("schema://records")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/marcelotryle/dev/pydantic/logfire-mcp/.venv/lib/python3.12/site-packages/mcp/server/fastmcp/server.py", line 383, in decorator
raise ValueError(
ValueError: Mismatch between URI parameters set() and function parameters {'ctx'}
When I have this resource:

@mcp.resource("schema://records")
async def get_logfire_records_schema(ctx: Context) -> str: ...
It seems the ctx is not being taken in consideration.

cc @jlowin

Did you manage to find a solution for this issue?

[sandil-heymilo]

Same here on 2.10.1