MCP server

The hosted MCP endpoint uses the API key in an Authorization header. Use a client that supports this header, or run the local cec mcp transport. OAuth-based web connectors are not available in this version; the existence of a tools manifest does not imply that claude.ai or ChatGPT can authenticate to the hosted server.

Client configuration

Keep your key in the client's private configuration; the placeholder below stands for it.

  claude mcp add --transport http ce-computers https://api.agents.computeengines.com/mcp \
    --header "Authorization: Bearer $CE_API_KEY"

Tool discovery and permissions

The MCP tools reference lists each tool with its required scope and its annotations. Read-only and idempotent annotations describe behavior; they do not authorize an action. The hosted server filters the list by the key's scopes and hides computer creation for a computer_ids-restricted key. The local server lists all tools because that key cannot read its own scope list; unauthorized calls still fail.

Create tools return the idempotency key they used. Retain and reuse it after a lost response instead of creating another computer. Tool errors preserve the Problem object. Desktop coordinates are display pixels; screenshot scaling must be applied before an action. read_file is limited to 1,000,000 bytes and write_file to 700,000 bytes; use the SDK, CLI or an appropriate guest command for larger transfers.

Ask for a bounded task such as creating a computer, running a repository's tests and pausing on completion. The tool transport is not permission to follow untrusted instructions inside the repository. For interactive help, follow the complete human takeover sequence and retain the desktop session ID privately.

Other clients

Any client that can send an Authorization: Bearer header to the hosted endpoint can use it; consult your client's documentation for its configuration format. Clients that cannot send that header can run cec mcp locally instead.

Dory is in development; these pages describe the planned service and may change. Questions: support@computeengines.com.