miosa-mcp

# miosa-mcp MCP (Model Context Protocol) bridge that exposes MIOSA cloud sandboxes and desktops to any MCP-aware client (Claude Code, Cursor, Gemini CLI, etc.). ## Two ways to run it ### 1. Hosted (recommended) - no install MIOSA ships a public MCP endpoint at `https://api.miosa.ai/api/v1/mcp`. Point any MCP client at it with your `msk_u_*` API key as a Bearer token: ```bash claude mcp add --transport http miosa \ https://api.miosa.ai/api/v1/mcp \ --header "Authorization: Bearer msk_u_your_key_here" ``` Full guide: [`docs/api/mcp-connect.md`](../docs/api/mcp-connect.md). ### 2. Local stdio (this Python package) Install: ```bash pip install miosa-mcp ``` Add to `~/.claude/mcp.json`: ```json { "mcpServers": { "miosa": { "command": "python", "args": ["-m", "miosa_mcp"], "env": { "MIOSA_API_KEY": "msk_u_your_key_here", "MIOSA_TENANT": "optional-organization-slug" } } } } ``` Use stdio when you need to wrap the MCP layer with custom local logic, or your client does not yet support remote MCP. Both modes hit the same MIOSA REST API under the hood. Get your API key at <https://miosa.ai/dashboard/api-keys>. `MIOSA_TENANT` selects an initial organization for every API request. You can also change organization context during a session with `organization_switch`. The backend verifies membership before MCP updates its active context. ## Action authority Governed MCP tools ask MIOSA's control-plane action authority immediately before dispatch. The control plane owns capability versions, grants, one-time approvals, revocation, and receipts. The MCP package only maps tool names to canonical capabilities from a generated contract and never copies policy locally. Every registered tool has exactly one canonical capability; a tool with no mapping fails closed before any dispatch. Pending approval, denial, a missing catalog capability, or an unavailable authority fails closed before the SDK or REST operation runs.…