MCP Console — Sewa Setu

Instrumentation / MCP

Model Context Protocol console

Both halves of the scheme, driven by hand from the browser. Every call below is a real streamable-HTTP request to the same MCP endpoints any other client would use — nothing here is simulated or stubbed.

Citizen · open Officer · token required No credential

Recommended / one press

Run both steps end to end

Resets the reserved test citizen, has them apply through the Citizen MCP server exactly as the voice assistant would, then has the block officer work the queue and decide — and finally reads the portal's own tables back to confirm what a clerk would see. Every tool call, its arguments and its raw result are printed below.

Officer bearer token

No departmental credential is configured. Set OFFICER_MCP_TOKEN, or mint a program token at /admin/tokens and paste it here.

Step 1 — the citizen's tools http://mcp_servers:9000/mcp/citizen/

Tool

Arguments (JSON)

No call made yet.

Step 2 — the officer's tools http://mcp_servers:9000/mcp/officer/

These tools answer only with a token. Leave the box empty on purpose once — you will see the flat 401 in the panel below, which is the guardrail rather than a description of one.

Bearer token

Tool

Arguments (JSON)

No call made yet.

The same journeys are asserted automatically, against the database, on the evaluation dashboard.