HTTP API: mcp
The 1 operation tagged mcp, each with its parameters, its body and what it answers.
Speak MCP to this instance
POST /mcp
Answer one MCP message.
workspace is a default for the tools' own argument rather than a pin, exactly as
subroutine mcp --workspace is: the credential is what pins, and a session that
could not look anywhere else would leave an agent unable to read a decision filed next
door. A plugin puts it in the URL, which is the one place a static configuration file can
put it.
Left unset on a multi-workspace instance, every read is refused as ambiguous - which is deliberate, and the refusal names the workspaces rather than merely complaining.
project is where a task or a document is filed when the write names no project and no
checkout says, which is the same place in the URL for the same reason. A project named in
the write still wins, and the write is checked against what the credential may do wherever
it lands.
Parameters
workspace(stringornull, in query)project(stringornull, in query)
Request body: object as application/json, required.
Responses
200: Successful Response422:HTTPValidationError. Validation Error