Skip to main content
Every workspace on the Mirage server is an MCP server at:

Connect

On your own machine, let the client launch mirage mcp. It starts the server if needed and sends your token.
For a server elsewhere, give the client the URL and a token:

Auth

The endpoint takes the same bearer token as the HTTP API. mirage mcp reads it from MIRAGE_TOKEN or ~/.mirage/auth_token. The server does not offer OAuth sign-in, so a client must send the header.

Tools

Their inputs are listed under Call a tool. read, ls, grep and glob are marked read-only.

Sessions

Calls run in the workspace’s default session. To use another, add ?session_id=<id> to the URL, or -s <id> to mirage mcp. The session’s profile applies as it does to a shell line: a path hidden from cat is hidden from read. Command rules apply only to shell, ls and grep.