Resources and prompts are in beta and subject to change.
Besides tools/*, the same POST /mcp JSON-RPC session supports resources (URI-addressable context) and prompts (reusable templates). Use the standard MCP method names; auth matches tools (Authorization: Bearer …).
JSON-RPC method | params | Returns |
|---|
resources/list | — | { "resources": [ … ] } — resource descriptors (uri, name, …). |
resources/templates/list | — | { "resourceTemplates": [ … ] } |
resources/read | uri (required) | { "contents": [ { "uri", "mimeType", "text" } ] } — typically JSON in text. |
prompts/list | — | { "prompts": [ … ] } — prompt names and metadata. |
prompts/get | name (required), arguments (optional object, depends on prompt) | Resolved prompt per MCP spec. |
For workflow guidance (when to prefer resources or prompts vs tools), see
Accessing patient state.