Privacy MCP

Live

OAUTH 2.0

ACCOUNTING & FINANCE

Productivity

Connect to Privacy MCP. Create and manage virtual cards, set spend limits, pause or close cards, and review transactions from your AI workflows.

  • Acts as the user: Every tool call runs as the authorizing user. Access and audit trail stay intact.
  • Credentials stay vaulted: AES-256 encrypted, resolved at request time, never stored in LLM context.
  • Scoped before every call: Per-user permissions enforced automatically. 90-day audit trail included.
Privacy MCP
agent · Acme Q3
Run
Close Card in Privacy MCP
S
privacymcp_close_card
85ms
Privacy MCP agent
Permanently close a virtual card, blocking all future transactions. this action is irreversible..
Sources: Privacy MCP
privacymcpmcp
1 tool call
18:29
Message Claude...

Privacy MCP tools for AI agents

CALL ANY TOOL
10 tools covering get, create, close.
privacymcp_close_card
Permanently close a virtual card, blocking all future transa
Permanently close a virtual card, blocking all future transactions. this action is irreversible.
Parameters
Name
Type
Required
Description
card_token
string
Required
Token of the card
privacymcp_create_card
Create a new virtual card on your privacy.com account with o
privacymcp_get_card
Retrieve details for a specific virtual card by its token, i
privacymcp_get_pan
Retrieve the full card number (pan), cvv2, and expiration da
privacymcp_list_cards
List all virtual cards on your privacy.com account with opti
privacymcp_list_transactions
List transactions on your privacy.com account, with optional
privacymcp_pause_card
Pause a virtual card to temporarily block all transactions u
privacymcp_unpause_card
Re-enable transactions on a previously paused virtual card.
privacymcp_update_card_memo
Update the memo (friendly name) on a virtual card.
privacymcp_update_card_spend_limit
Update the spend limit and optional reset duration for a vir
Build your Agent
Same auth pattern across every framework.
Python · LlamaIndex
from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="privacymcp")

mcp = MultiServerMCPClient({
"privacymcp": {
"url": "https://mcp.scalekit.com/privacymcp",
"headers": {"Authorization": "Bearer " + token}
}
})
tools = await mcp.get_tools()
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "privacymcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/privacymcp
// Pass: Authorization: Bearer + token
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "privacymcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/privacymcp
// Pass: Authorization: Bearer + token
from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="privacymcp")
# Connect to MCP at https://mcp.scalekit.com/privacymcp
# Pass: Authorization: Bearer + token
Try these prompts
Paste any prompt into your agent to get started.
Get started
Copy the prompt
Copied
Update the spend limit and optional reset duration for a virtual card?
Copy the prompt
Copied
Re-enable transactions on a previously paused virtual card?
Advanced
Copy the prompt
Copied
List transactions on your Privacy.com account, with optional filters for card, date range, and result?
Copy the prompt
Copied
Retrieve the full card number (PAN), CVV2, and expiration date for a virtual card?
SEE HOW AUTH WORKS
User authorises once. Every agent call after uses their token with scope enforcement.
1
Authorize
Your user connects
Privacy MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Privacy MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Privacy MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Privacy MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other connectors.
OPS
Email-to-calendar scheduling agent
Parse scheduling intent from Gmail threads and create Google Calendar events with the right attendees and timezone.
ENGINEERING
Engineering standup agent
Aggregate GitHub and GitLab activity, link to Jira, and post a daily standup digest to Slack. No async updates.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
One connector today. Ten tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access Privacy as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Privacy OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Privacy?
Yes. Pass a tool name filter to listScopedTools so the productivity agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Privacy.

What happens when a user revokes Privacy access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent create cards or reveal PANs for any account?
No. Card creation, PAN reveals, and spend limit changes run only on the authorizing user's Privacy account, with every sensitive call logged in the 90-day audit chain.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""privacymcp"": {
""url"": ""https://mcp.scalekit.com/privacymcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.privacymcp]
url = ""https://mcp.scalekit.com/privacymcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""privacymcp"": {
""url"": ""https://mcp.scalekit.com/privacymcp"",
""type"": ""http""
}
}
}