Connect an MCP client

Griot's stdio bridge forwards MCP JSON-RPC to the governed K01 HTTP MCP endpoint. K01 owns tool discovery, authorization, invocation, audit, and schemas; the bridge does not expose a second independent tool catalog.

Before you begin

The bridge source is zone-k/griot-mcp on its feature branch. Install it from a checkout with the bridge:

python -m pip install -e zone-k/griot-mcp

Choose one credential type accepted by your K01 MCP edge. A session JWT carries a human principal; a gak_ agent key uses X-API-Key plus tenant routing and is limited by the agent's grants. A PAT works only where the MCP edge verifies it as a human principal. The bridge cannot turn a PAT into a JWT. Never put a key in the endpoint URL.

Configure the stdio server

Configure your MCP client to launch griot-mcp with an environment containing GRIOT_MCP_URL (an HTTPS /mcp/ endpoint), GRIOT_API_TOKEN, and, when required, GRIOT_TENANT_ID. Use the MCP client's secret storage for the token rather than checking a JSON config with a literal value into git. For gak_, the tenant ID is required. http://localhost is allowed for local development; remote HTTP is refused.

Once connected, ask the client to list tools. The returned names and input schemas are the current server's advertised set. A missing tool may mean your principal lacks a grant; it is not evidence that an arbitrary method name will work. Griot currently advertises tools, not MCP resources or prompts.

Move an older integration

The bridge maps legacy run_query(sql) to governed query_dataset(sql) and sample_dataset(slug) to get_dataset_sample(slug) only when the target appears in discovery. A domain-qualified dataset reference is not shortened to a bare slug. Other old names should be replaced with the live tool names and schemas, such as describe_contract for contract description. Revoke an agent key through the identity flow when no longer needed; revocation removes discovery and invocation after the edge's validation cache expires.

The bridge is implemented on a feature branch. Check its version and the server's advertised tools before treating these instructions as a deployment guarantee.