Cardzen MCP Server

The Cardzen MCP server lets a compatible assistant securely access supported parts of your Cardzen wallet. You connect it from the assistant, sign in to Cardzen in your browser, and approve the requested access.

For manual setup, use this MCP server address.

https://mcp-stage.cardzen.ai/mcp

Set Up a Connection

1. Open Account & Settings in Cardzen and choose Connections & MCP under Integrations.
2. Under Connect, choose ChatGPT, Claude, or Muse. The guides show the setup currently available for each assistant. Custom setup does not require a directory listing. For another compatible client, choose Other MCP client or open the generic setup guide.
3. Follow the guide for your assistant. When your browser opens Cardzen, sign in and review the access request before approving it.

New to Cardzen? Choose Create one on the sign-in page, create a Free account, and finish the existing account setup. Cardzen then returns you to the access review while the assistant's request is still valid. You can skip adding cards during setup and add them later. The Cardzen AI consent step belongs to Cardzen's account setup; the MCP tools themselves do not call Cardzen's AI. Approval of the separate assistant connection is always your choice.

After approval or denial, return to the original assistant tab or app. A request can expire while you sign up or complete setup. Your Cardzen account and any saved setup remain; go back to the assistant where you started and choose Connect again to get a fresh request. Do not reuse the old Cardzen authorization URL.

Your assistant and plan may affect where custom MCP connections are available. Cardzen maintains guided instructions for ChatGPT, Claude, and Muse; other clients use the generic standards-based instructions.

The guide for each assistant reflects its current Cardzen setup route. A directory install appears only after that assistant's Cardzen listing is approved and the guide is updated.

What the Connection Can Do

Cardzen shows the exact access being requested before you approve a connection. Available tools depend on your account and the capabilities Cardzen has enabled.

• Every authenticated account: search Cardzen Help and the public card catalog; view Active and Past wallet cards, their ownership timeline, saved reward choices, and component tracking; and ask which credits expire this month after approving credits:read. On Free, the expiration lookup shows credit and card names and dates only, through the rest of the current Eastern calendar month. With wallet:write, you can add a card, mark it closed, reopen it, remove an entry added by mistake, change preferred or frozen state and open date, and save an available reward choice. With credits:write, you can turn credit, perk, or multiplier tracking on or off.
• Pro: the above plus tracked credit details, including recorded usage and remaining amounts, longer expiration windows, expiration totals, history, streaks, renewals, and stored Current Insights or selected annual credit report sections. With credits:write, you can also update credit usage.
• Email-unverified accounts: use the Free quota ceiling even if another account capability would otherwise allow more traffic.

Closing a card moves it to Past and keeps its saved Cardzen history. Reopening it starts a new period and keeps the earlier periods. Removing a mistaken entry hides it from your wallet and Past cards while keeping saved credit usage. These actions affect only your Cardzen records.

Where the connected assistant supports bulk credit updates, name up to 12 saved periods for one credit in one calendar year. Each period can have its own amount or status. Cardzen saves the whole batch together. The card needs a confirmed Start Date, and any period ending before that date makes the batch ineligible. Review Start Date in My Cards if your assistant reports that it is unconfirmed.

You can also explicitly request a change to an owned card's saved ownership periods or permanent erasure of its Cardzen wallet entry and saved history. When an assistant requests history access, Cardzen shows it as a Write permission under Your wallet. History changes also need the Manage your cards permission. The normal Approve button grants the requested permissions shown on that screen. Your assistant may ask you to confirm the exact change before applying it. Permanent erasure deletes the saved Cardzen history for that entry.

An existing connection without history access keeps its current permissions. To add history access, reconnect from an assistant that requests it and review the new Cardzen access screen. Cardzen does not add history access automatically.

Billing, applications, money movement, account deletion, CardManager publication, Plaid data, and public web search are not MCP tools.

The authorization screen identifies every requested read and write scope. The Server rechecks the current grant, scope, account capability, verification state, and tool switch on every call; a client cannot bypass those checks by caching an older tool list. Write tools are separately capped, require an idempotency key, and can be disabled without disabling read tools.

Cardzen MCP tools are deterministic and do not call Cardzen's AI. See MCP Privacy and Security for details.

If your wallet is empty, Cardzen can still search Help and the public card catalog. Add your cards in Cardzen before asking about your wallet. Catalog benefits are public product definitions; they do not establish your saved selectable choices, account-specific earning rates, or tracked state. The assistant cannot infer cards you have not added, and it should not add or change cards without your explicit request.

Manage or Disconnect Apps

Open Account & Settings -> Connections & MCP to see connected apps and their last-used time. Select a connected app and choose Disconnect. Disconnecting immediately blocks that app from making another Cardzen MCP request and stops refresh and new token issuance, including when an older access token remains visible to the OAuth provider. You can reconnect later by completing setup and authorization again.

On a touch device, pull down from the top of the Connections & MCP content to refresh the Connected Apps list. Cardzen keeps the last successfully loaded list visible while it checks for updates. If a background refresh fails, the existing rows remain visible and no connection is revoked.

For usage caps and connection problems, see MCP Limits and Troubleshooting.