# Connect MiMo Code

This guide uses a personal access token. OAuth requires a pre-registered public client and an approved callback address; entering only the server URL may attempt anonymous dynamic registration, which Reconstruct disables. See [client compatibility](../connect-ai-agents.md#client-compatibility).

Copy your MCP access token from your [Reconstruct Platform account settings](https://reconstruct.dev/platform/). See [Before you start](../connect-ai-agents.md#before-you-start) for the connection requirements. Set `CR_RECONSTRUCT_MCP_TOKEN` in the environment that launches MiMo Code.

Add `reconstruct` under `mcp` in your user `~/.config/mimocode/mimocode.json` (or your project's `mimocode.json`). If the file already exists, add only the `reconstruct` entry to its existing `mcp` object:

```json
{
  "$schema": "https://mimo.xiaomi.com/mimocode/config.json",
  "mcp": {
    "reconstruct": {
      "type": "remote",
      "url": "https://reconstruct.dev/mcp",
      "enabled": true,
      "oauth": false,
      "headers": {
        "Authorization": "Bearer {env:CR_RECONSTRUCT_MCP_TOKEN}"
      }
    }
  }
}
```

This configuration uses a personal access token; `oauth: false` keeps MiMo Code on that authentication method. For a different OAuth setup, contact support with the exact callback URI before connecting. Keep a literal token out of project files. Run `mimo mcp list` to inspect the connection, then ask MiMo Code to call `list_products` using the `reconstruct` tools.

See the official [MiMo Code MCP guide](https://mimo.xiaomi.com/mimocode/mcp-servers) and [configuration locations](https://mimo.xiaomi.com/mimocode/config-overrides). Next, try the [prompt examples](../prompt-examples.md).