# MCP server

Connect compatible agents to the existing management tools.

Status: Implemented stdio bridge · Desktop-control tools not yet available

## Run the bridge
Install or check out the ComputerUse source on the machine running your agent. Supply `COMPUTERUSE_API_ORIGIN` and `COMPUTERUSE_API_TOKEN` through that machine's secret configuration, then launch:
```bash
python -m computeruse.mcp
```
The bridge uses newline-delimited JSON-RPC over stdio and advertises MCP version `2025-11-25`. It calls the authenticated REST API; it never reads the database directly. Remote origins must be HTTPS; loopback HTTP is permitted for development.

## Tools
| Tool | Effect |
|---|---|
| check_stock | Read verified inventory and pricing |
| quote_desktop | Read a quote without reservation |
| list_rentals | Read the account's rentals |
| purchase_desktop | Spend prepaid credit for one computer; needs explicit buyer authority |
| order_computers | Reserve a mixed 8 GB/16 GB fleet, 1–100 total, using prepaid credit |
| assign_agent | Store an association with an active owned rental |
| proxy_catalog | Read available proxy catalog data |
| quote_proxy | Quote without purchasing a proxy |

## Client configuration
Use your client's stdio MCP configuration with `command: python` and `args: ["-m", "computeruse.mcp"]`. Set the working directory to the source checkout or install the module in that Python environment. Secret substitution syntax depends on the client; do not paste a real token into a committed JSON file.

## Protocol and permissions
The client initializes, sends `notifications/initialized`, lists tools and calls them. Validation rejects unknown properties, missing required inputs and invalid values. Tool annotations do not override authorization. The API checks owner and scope for each operation.

## Limit
This bridge currently manages rentals. It is not a browser/desktop automation server, and there is no hosted HTTP MCP endpoint yet. Read each integration guide for its verification status.