Pit record
Claude Desktop does not list dynamic MCP resource templates (only static resources)
A dynamic MCP resource with a URI template (e.g. greeting://{name}) does not appear in Claude Desktop while static resources do. Claude Desktop calls resources/list but not resources/templates/list, so templated resources are never surfaced. Expose the capability as a tool, or verify support per client; the server is fine.
Markdown mirror | Canonical source
Fast answer
Problem: a static resource works in Claude Desktop but a parameterized/templated resource does not show
Root cause: Dynamic resources are exposed via resources/templates/list; static resources via resources/list.
Fix first: Do not rely on dynamic resource templates in Claude Desktop; confirm client support before designing around them.
Verify: Open the server in MCP Inspector and check the Resources tab.
Queries this answers
- dynamic resource not working in Claude desktop
- dynamic resource not working in Claude desktop fix
- dynamic resource not working in Claude desktop root cause
- Claude Desktop does not list dynamic MCP resource templates only static resources
- Claude Desktop does not list dynamic MCP resource templates (only static resources) fix
- Claude Desktop does not list dynamic MCP resource templates (only static resources) root cause
- how to fix Claude Desktop does not list dynamic MCP resource templates only static resources
- claude-desktop list dynamic mcp resource templates static resources
Record metadata
| Status | verified |
|---|---|
| Confidence | high |
| Created | 2026-06-21 |
| Updated | 2026-06-21 |
| Last verified | 2026-06-21 |
| Affected tools | claude-desktop, mcp-server |
| Tags | mcp, claude-desktop, resources, resource-templates, client-capability, fastmcp |
Common search queries
- claude-desktop-no-dynamic-resource-templates
- claude desktop no dynamic resource templates
- Claude Desktop does not list dynamic MCP resource templates only static resources
- Claude Desktop does not list dynamic MCP resource templates (only static resources) fix
- Claude Desktop does not list dynamic MCP resource templates (only static resources) root cause
- claude-desktop
- resources
- resource-templates
- client-capability
- fastmcp
- mcp-server
- a static resource works in Claude Desktop but a parameterized/templated resource does not show
Symptoms
- a static resource works in Claude Desktop but a parameterized/templated resource does not show
- the server is correct and the template appears under the Inspector Resources tab
- time lost assuming the server code is wrong
Environment
| framework | FastMCP / MCP Python SDK |
|---|---|
| agent | claude-desktop |
| constraints | client must call resources/templates/list to discover dynamic resources |
Root cause
- Dynamic resources are exposed via resources/templates/list; static resources via resources/list.
- Claude Desktop calls resources/list only, so it never discovers resource templates.
- The server is fine; the client does not request templates.
Fix
Do not rely on dynamic resource templates in Claude Desktop; confirm client support before designing around them.
Expose the parameterized capability as a tool, which Claude Desktop fully supports.
Verify what the server offers with MCP Inspector (Resources tab shows templates) to separate a client gap from a server bug.
Verification
Open the server in MCP Inspector and check the Resources tab.
Expected: The resource template is listed, proving the server is correct and the gap is Claude Desktop not calling resources/templates/list.
Workarounds
- Model parameterized data as tools instead of resource templates for Claude Desktop.
Anti-patterns
- Assuming a missing resource in Claude Desktop means the server is misconfigured.
- Designing a server around resource templates without checking client support.
Sources
No matching fix?
If this record is close but does not solve the user's failure, create a safe unresolved-pit report instead of guessing. Include exact symptoms, environment, attempted fixes, and the record ids already checked.