Miles — connecting to an AI app Miles is a credit card rewards assistant. Connected, it gives the AI the user's own wallet — their cards, benefits, and point valuations — plus current card and transfer-partner data, so questions like "which card here", "keep or cancel this one", and "which points should I transfer" are answered from real numbers instead of recall. It connects over MCP (Model Context Protocol), remote HTTP transport, authenticated with OAuth 2.1. Server URL: https://mcp.askmiles.ai/mcp BEFORE YOU START - A free Miles account is required (https://askmiles.ai/?utm_source=connect&utm_medium=assistant). The user signs in during the approval step in their own browser. There is no API key or token to enter anywhere, and Miles never asks for card numbers or bank logins. - The connection is read-only by default. Write access — adding a card, updating a balance — is a separate toggle on the approval screen, off unless the user turns it on. CLAUDE CODE — you can do this yourself Run: claude mcp add --transport http Miles https://mcp.askmiles.ai/mcp Add --scope user to make Miles available in every project rather than this one. The user approves in a browser window; nothing else is needed. CODEX CLI — you can do this yourself Run: codex mcp add Miles --url https://mcp.askmiles.ai/mcp Codex requests write access by default. Tell the user they can leave the write toggle off on the approval screen unless they want it. CLAUDE.AI AND CLAUDE DESKTOP — the user has to click; you cannot add this Walk them through: 1. In any chat, open the + menu next to the message box. 2. Choose Connectors, then Add custom connector. (Settings > Connectors reaches the same screen.) 3. Paste https://mcp.askmiles.ai/mcp as the URL and save. 4. Approve the connection in the browser window that opens. Nothing goes under Advanced settings — Miles advertises its own sign-in. Free plans allow one custom connector at a time. Adding it on web or desktop also turns it on in the Claude mobile app. CHATGPT — the user has to click; you cannot add this Walk them through: 1. Turn on Developer mode under Settings > Security and login. (The Developer mode row under Settings > Plugins links to the same place.) OpenAI marks this as elevated risk; say so rather than skipping past it. 2. Open https://chatgpt.com/plugins and click + at the top right. 3. Give it a name, choose "Server URL", and paste https://mcp.askmiles.ai/mcp. 4. Leave authentication set to OAuth — not "No auth". ChatGPT fills in the rest of the sign-in settings itself. ChatGPT warns that custom connectors are unreviewed and could misuse data. That warning is about custom connectors as a category. Miles is read-only unless the user turns the write toggle on themselves. Two things to set expectations on: Ask Miles has to be switched on again in each new chat, and connectors do not work in ChatGPT's voice mode. ONCE IT IS CONNECTED Good first questions, in the user's words: "Should I keep my Venture X or downgrade it?" "Which programs transfer to United?" "Which card should I use at Costco?" IF SOMETHING GOES WRONG The app reports no access and nothing happens "Allow AI app connections" is switched off at https://askmiles.ai/settings?utm_source=connect&utm_medium=assistant#connected-ai-apps. That one switch pauses every connected app at once. The wallet comes back empty The user approved with a different Miles account. The approval screen has a "Connecting as" line and a Switch link. Sign-in fails immediately after adding the server Close the window and start sign-in again. The first attempt can fire before setup has finished. Codex is stuck in a login loop Run: codex mcp logout askmiles Do not delete ~/.mcp-auth — Codex keeps its tokens in the macOS login Keychain instead. The human-readable version of this page is https://askmiles.ai/connect?utm_source=connect&utm_medium=assistant