An MCP server is an item in the project.
Connect a Model Context Protocol server the way you connect a broker: over stdio with a command, or over HTTP. Its tools become forms, its resources and prompts are a click away, the whole JSON-RPC conversation is in the log, and Themis can use the server as her own hands.
At a glance
Call it, read it, sign in to it.
Connected, the server's catalog is the item: its tools, resources, resource templates and prompts, fetched together with their pages. Pick a tool and its arguments are a form built from the input schema, with completions where the server offers them — or raw JSON. The result comes back as text or structured content, with the isError flag and the duration; progress is shown while it runs; a call waits up to ten minutes.
Underneath, the same JSON-RPC frames the model would see, every one of them in the log, both ways — the server's stderr beside them for stdio servers.
Themis driving MCP serversResources, prompts, OAuth, and the server's own questions.
Everything the protocol allows a client to do, from the item — and everything a server may ask of a client, answered.