Module mcp 

The MCP server: the HTTP API’s operations as MCP tools for AI agents.

It is served at /mcp on the TLS listener, in rmcp’s stateless mode with JSON answers, behind the same authentication as every route. The stdio command in stdio forwards to it, so both transports pass one gate.

Modules

budget

The byte budget a result is held to: the call’s max_bytes, clamped to mcp.response_bytes, counted as the length of the result’s JSON text. A list drops whole rows from its end; a vCon’s text is cut on a character boundary. Something always remains, so a cursor always moves.

fence

Text the server did not write, marked for a language model: each value between OPEN and CLOSE, rewritten so that no fence character stands inside it.

stdio

vcon-server mcp: MCP on stdin and stdout, for an agent that starts the server as a command. Each request is forwarded to a running server’s /mcp with the one key the client file names, so stdio passes the same authentication, gate and audit as HTTP. The command opens no data directory and no master key.

Structs

Limits

The limits from configuration that the MCP server applies.

Functions

router

The MCP server’s routes: /mcp, behind authentication and counting, with every tool.

scope

The scope a tool needs, from its name’s area and its hints: vcon_ tools need read when read-only, delete when destructive, else write; legal_ tools legal; audit_ tools audit; admin_ tools admin. None, which refuses every call, for a tool that does not state both hints, states both true, or has no known area.