Claude Privacy.com connectorWhat Claude can do in your Privacy.com account.
The Claude Privacy.com connector exposes 10 tools: 4 read your cards and spending, 6 change them, 0 are undocumented. Here: what Claude sees, what it can create or shut, what it asks first, and who in your organization can switch it off.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude handles your virtual cards
Instead of opening the Privacy.com dashboard, finding the right card and clicking through its settings, you tell Claude what you want in a sentence. It reads your cards and transactions, then creates a merchant-locked or single-use card, pauses one, or changes its spending limit, right in the conversation. Every one of those moves touches real payment cards, so the publisher puts the responsibility squarely on you.
A card per merchant, set up in one request. You are signing up for several new services: create_card opens a card locked to each merchant with its own limit, and update_card_memo gives each one a name you will recognise in your list.
Spending reviewed without exporting anything. list_transactions pulls the approved and declined charges between two dates, filtered by card if you want.
A card stopped on request. A merchant keeps billing a card you want to stop: pause_card freezes it for now, close_card shuts it for good, which the publisher describes as permanent.
Now what the directory sheet does not say. Privacy.com states that API access, which this connector relies on, comes with one of its subscriptions that you pay for. get_pan returns the full card number, CVV and expiry into the conversation. And nothing runs on its own: no tool wakes up when a charge is declined or a limit is hit. For alerts that fire in the background you need an automation tool, a different job; the Integrations hub gathers that side.
The vocabulary in one minute
Five words you will meet while connecting Privacy.com.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in it while it answers you.
- Tool
- One named thing a connector lets Claude do in that account. Claude picks the ones it needs; the directory sheet lists them by name.
- Authorization
- Privacy.com's own sign-in screen, where you hand Claude the access it will use. Granted once per person, and it can be taken back.
- Approval
- The confirmation Claude waits for before it goes ahead with something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to a service outside it.
Setting up the Claude Privacy.com connector in three steps
- 01
Find Privacy.com in Claude
Open Claude's settings, go to Customize, then Connectors, and look for Privacy.com in the list. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector before each member can sign in on their own.
- 02
Connect from its row
Click Connect on the Privacy.com row, then sign in to your Privacy.com account in the window the service opens itself. If the link breaks later, Disconnect and connect again.
- 03
Read the authorization screen
Read the authorization screen before you accept. It belongs to Privacy.com, not to Claude, and it is what decides how far the access reaches. Privacy.com says this sign-in and authorization step happens the first time you use one of its tools.
The 10 tools, split by what they do
Privacy.com gives Claude 10 tools: 4 that read your account, 6 that change something in it.
Two groups: what Claude reads about your cards, and what it changes on them. Names stay exactly as Claude displays them.
- 4 read
- 6 write
What Claude reads (4)
4 toolsFour tools that look at cards and spending and leave them as they are.
get_card
Pulls the details Privacy.com holds for one specific card, so Claude answers about that card from its record rather than from your memory of it.
get_pan
Retrieves the full card number of a card, along with its CVV and expiry date, and shows them in the conversation.
list_cards
Lists every card on the account, page by page, which gives Claude the full inventory of the cards that exist on it, whatever their type.
list_transactions
Brings back charges filtered by card, by account, by date range or by result, approved or declined, with up to 1000 lines per page.
What Claude changes (6)
6 toolsSix tools that act on real payment cards. No source spells out their confirmation, so the general rule below applies.
close_card
Approval: see the ruleShuts a card, and the publisher describes that closure as permanent.
create_card
Approval: see the ruleOpens a new virtual card, single-use, merchant-locked or unlocked, with an optional memo, spending limit and limit period.
pause_card
Approval: see the ruleFreezes a card for the time being without closing it, as the publisher's word temporarily says.
unpause_card
Approval: see the ruleBrings a paused card back into service so purchases can go through again.
update_card_memo
Approval: see the ruleRenames a card by changing its memo, the friendly label you see in your list.
update_card_spend_limit
Approval: see the ruleChanges how much a card may spend and over which period: per transaction, monthly, yearly or for the card's whole life.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before any action it takes on an account on your behalf. The request shows up in the conversation at the moment it matters.
No source says whether Claude asks before creating, pausing or closing a Privacy.com card, so that default rule is what covers all six changing tools. On Team and Enterprise workspaces, owners decide whether members may let certain actions through without being asked each time, and they can restrict what a connector may do for the whole organization, keeping reading and blocking changes, for example. Claude works with your Privacy.com rights and nothing more.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. The answer, connector by connector, is not published anywhere: a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members can sign in. For the current state, check the Privacy.com sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a charge goes through, gets declined or reaches a limit.
This connector has no Claude help article of its own; what we know comes from the directory sheet and from the publisher's developer page. The tool list is an observed floor, not a promise: an administrator can open actions that no public sheet shows. The directory's verified badge is not a security audit either, and Anthropic writes on every sheet that it does not control which tools a publisher exposes.
Need help connecting Privacy.com to Claude?
A person reads every message.
