Connect over MCP

Three steps

The server is https://mcp.askmiles.ai/mcp. It speaks streamable HTTP and authenticates with OAuth 2.1; a client that supports both connects with one command.

1. Add the server.

Codex:

2. Approve it. The first call opens a browser tab on askmiles.ai. Sign in if you are not, read the list of what the app will be able to see, and approve. Read access is what you are approving; changes to your wallet are a separate toggle on that screen, off unless you turn it on.
3. Ask something that needs your wallet.

A successful connection shows up two ways: the tool call names Miles (the alias you chose in step 1) and the answer cites your own cards. If the assistant says it has no wallet access, the approval did not complete; run the add command again and finish the browser step.

What the agent gets

Forty-six tools over your cards, valuations, balances, credits, certificates, gift cards, elite status and watchlist, plus a guidance resource at miles://guidance/working-with-miles that tells the model how to read a capped or conditional rate. Miles returns data and arithmetic; the reasoning is the agent's. The full list, with every parameter, is under MCP tools.

Managing the connection

Every connected app is listed at Settings → Connected AI Apps.

• Pause suspends every app at once. Tokens survive, every tool call is refused, and turning it back on resumes the apps without another approval.
• Disconnect revokes one app's tokens. That app has to be approved again to reconnect.

A personal API key is managed next door at Settings → API keys, and the pause switch governs it too.

Other clients

Claude Desktop, ChatGPT, OpenClaw and mcporter each have their own steps on Connect and OpenClaw. The server URL is the same everywhere. An assistant that can read a URL can set itself up from connect.txt.