Skip to main content
Hosts that mount MCP resources next to tools (context pickers, ”@” attachments) see one resource template on the Sidecars server. Resources are read-only views; they are not callable tools and cannot change anything.

sidecars://document/{id}

Listing

resources/list returns up to 50 of the documents the signed-in person can reach, using the same membership-filtered listing as list_documents with no selector. Only artifacts of type document are listed; pages and tables are not. Each entry has the form:
An anonymous resources/list returns an empty list rather than an authentication challenge, so a host can probe the server before sign-in.

Reading

resources/read with a sidecars://document/<id> URI returns the document’s derived markdown:
Reading runs the same access check as read_document. An artifact the person cannot see, or that does not exist, fails with Artifact not found. Reading without a token fails with Authentication required.

Differences from read_document

Because the resource read does not return a version, use read_document before any write. The resource is for putting a document into context, not for editing it.

Subscriptions

resources/subscribe and notifications/resources/updated are not supported. Re-read a resource to see changes.

Prompts

The server registers no MCP prompts; prompts/list is answered as an unsupported capability. What it provides instead is a short instructions string on initialize (“Sidecars: the workspace’s shared knowledge, pods, conversations and documents. Tools act as the signed-in person inside the workspace their token names.”) and a model-facing description on every tool, reproduced on the reference pages.