MCP Adapter

Commands and payload schemas for MCP integration.

Capabilities

• commands: ["mnemoverse/render"]
• resources: none
• prompts/tools: optional

Command: mnemoverse/render

• Input: render_request.v0
• Output: render_context_reply.v0

Input example

{
	"version": "v0",
	"id": "7d8f59a0-1b2c-4d3e-9f8a-1234567890ab",
	"intent": "debug_memory_leak_in_embedding_computation",
	"budgets": { "tokens_max": 3000, "time_ms": 500 },
	"risk_profile": { "level": "high" },
	"privacy_mode": "allow",
	"request_id": "req-debug-002"
}

Output example (error with recovery options)

{
	"request_id": "req-debug-002",
	"error": {
		"code": "PROVIDER_TIMEOUT",
		"message": "L2 provider exceeded deadline",
		"retriable": true,
		"attempt": 1,
		"max_attempts": 2,
		"options": [
			{ "action": "retry_with_reduced_scope", "hint": "top_k: 20; deadline: 400ms" },
			{ "action": "explicit_l1_expansion" },
			{ "action": "return_l4_only" }
		]
	}
}

Transport

• JSON RPC over MCP; correlation via requestId/session provided by host

Privacy

• honor privacy_mode; adapters MUST not leak raw text when block

Observability

• Include minimal timing metadata in MCP logs; no PII
• Return metrics in payload when available (used_tokens, planner_ms, coverage_entities)
• Expose error.options[] so clients can choose recovery path

Related

• Contracts: ../contracts/README.md