MCP server adapter

[stationeros]

Problem

v1 exposes an HTTP API, but not a native MCP surface for model-driven tool use.

Goal

Expose registered tools through an MCP server adapter.

Scope

• MCP tool listing from the tool registry
• MCP tool invocation mapped to broker execution
• schema translation for inputs and outputs
• policy-aware error handling for MCP clients

Acceptance criteria

• MCP clients can discover registered tools
• MCP invocations flow through the same policy runtime as HTTP calls
• traces preserve tool identity across the adapter boundary