Boundary
Run with a control-scoped VIRA_API_KEY.
CONTROL
MCP
Expose reviewed control-plane operations to MCP clients while keeping runtime behavior enforcement and automatic publishing outside the MCP server.
EXECUTION BOUNDARY
The MCP server exposes selected control-plane tools. Runtime resolve remains in the runtime API; MCP does not become the behavior enforcement path.
IDENTITY PRESERVED
Keep the behavior identity attached to the host framework.
- control-scoped API identity
- profile/revision identity
- Teach evidence identity
- evaluation/deployment records
SUPPORTED OPERATIONS
Use Vira where the control boundary actually belongs.
- 01
view profiles, revisions, and deployments
- 02
inspect Teach Inbox
- 03
submit evidence
- 04
start evaluation
- 05
review control-plane state
IMPLEMENTATION HOOK
Keep the host runtime native.
This example mirrors the repository documentation. The exact API contract remains in Docs and source.
VIRA_API_URL=https://api.example.com VIRA_API_KEY=... pnpm --filter @vira-behavior/mcp-server startSECURITY BOUNDARY
Integration does not equal authority.
Boundary
Runtime enforcement remains outside the MCP process.
LIMITATIONS
State what the adapter does not control.
- MCP cannot resolve runtime behavior.
- MCP cannot publish automatically.
- Tool availability must not imply unrestricted control authority.