ONE KEY FOR EVERY ACCOUNT YOU RUN
Youragent.Youraccounts.Oneclick.
Connect every account you own across Supabase, Vercel, Cloudflare, Stripe and 20+ more. Switch between them with one shortcut—your agent only ever sees the account you choose.
- your whole stack, connected
- API key for all of them
- 1
- credentials exposed to your agent
- 0
Sound familiar?
The tools were never the hard part. Switching between your accounts is.
Run a few projects in parallel and you know the loop: open a tab, change org, copy a key, paste it into .env, realize it was the other project's, start over.
- 01Supabase caps you at 2 active projects on free. You have 5.
- 02Stripe splits test and live accounts per product. You run 3 SaaS.
- 03Cloudflare separates DNS, Workers and R2 per account. You have 4.
- 04Vercel mixes personal, work, and every client.
- 05Your AI agent understands none of this — every time, you paste the right key by hand.
Three steps. There is no fourth.
Connect your accounts, mint one key, point your agent at it. Switching workspaces is a click—your agents stay aligned without redeploys.
Connect your accounts
Connect your accounts
One-click OAuth where the provider supports it, copy-paste API key where it doesn’t.
Add as many accounts of the same service as you want—personal, work, each client—grouped by workspace. No more scattered shells or .env files buried in agent sandboxes.
Every secret is sealed with AES-256-GCM at rest and never resurfaces as plaintext. You just see a clean inventory of what’s live, what’s idle, and what needs reconnecting.
Generate your API key
Generate your API key
One TuMCP key for everything—never another raw provider token in a prompt.
You decide which tools it exposes and at what level—read, write, or nothing—per tool, not per service. Your assistants point at one MCP endpoint while we resolve the exact credential graph on every call.
So swapping GitHub identities or waking a dormant Stripe sandbox never forces a refactor of your MCP blocks.
Static configuration gives way to living policy: you steer access from the dashboard while agents keep shipping.
Connect it to your agent
Connect it to your agent
Works with Claude Code, Cursor, VS Code, n8n, LangChain, CrewAI and any MCP client—the same snippet everywhere.
When you switch workspace in the app, your agent sees the change at once. If the key ever leaks, you mint a new one in seconds while underlying OAuth grants stay intact.
If a provider token goes stale, targeted health checks flag it before your agent threads derail—you decide which accounts stay hot and when to pull the plug.
Less copy-paste, fewer midnight rotations, and more confidence your agents ride governed infrastructure instead of tribal knowledge.
Your whole stack — secure, observable, one switch away
Connect the services you actually run. Every credential is vaulted once, exposed behind a single MCP endpoint, and ready to flip between accounts without rewriting a single prompt. Right now we ship 24 provider integrations—each wired exactly the same way: vault once, one endpoint, switch accounts in a click.
- GitHub
- Stripe
- Notion
- n8n
- ManyChat
- Supabase
- Neon
- PayPal
- Google Drive
- Telegram
- Slack
- Cloudflare
- Polymarket
- Clerk
- Vercel
- Render
- Pinecone
- Sentry
- Resend
- Browserless
- Railway
- Discord
- Apify
- Dodo Payments
No sales call. No enterprise tier. Just ship.
Start free for 14 days with every surface unlocked. Move to Amateur or Professional when your agents can’t sit still—annual billing trims ~15%.
FREE
- 14-day free trial — every dashboard surface unlocked
- 1000 routed MCP/API calls per month — enough for real multi-step agent runs
- One MCP endpoint that mirrors every connected account
- AES-256-GCM at rest plus OAuth-aware refresh where supported
- Docs written for Claude Code, Cursor and VS Code MCP — no generic fluff
Start free
AMATEUR
Billed monthly
- 10000 routed API calls per month (UTC)
- Unlimited connected accounts and workspaces
- Success vs. error charts and per-integration signals
- Built for running agents across several machines
- Room to iterate prompts without a hard stop mid-month
Upgrade to Amateur
PROFESSIONAL
Billed monthly
- 50000 routed API calls per month (UTC)
- Mission control for org-wide agent fleets
- Aggressive rotation policies for the most sensitive workloads
- White-glove onboarding from our engineers
- Quarterly architecture reviews as your surface area grows
Upgrade to Professional
FAQ for builders shipping AI automation
If you have more than 2 accounts on any service, you already lose time switching between them: copy an API key, paste it into .env, find out it was the wrong project’s key, repeat. TuMCP is one credential gateway: connect every account once (OAuth where we support it, or paste a key), get a single MCP key, and your AI agent only ever sees the account you pick. Switch workspace in one click—no redeploy, no re-pasting OAuth flows you already completed. Under the hood it behaves like an API gateway for your agent stack; day to day it’s just centralized control instead of brittle, repeated configuration everywhere.
Yes, that’s the baseline outcome. Teams typically forget which token lived in which Claude project folder or Cursor workspace. With TuMCP you record credentials in the vault, activate the right workspace or billing account when the task shifts, and your agents inherit the routing automatically—without redeploy and without re‑pasting OAuth flows you already completed once.
Any MCP-capable workload: Claude Code, Cursor, VS Code extensions that speak MCP, and agent frameworks exposing stdio or Streamable HTTP. You paste one MCP block pointing at TuMCP—the same snippet travels across tools, eliminating duplicate setup when every teammate brings a favourite assistant.
Dozens of providers including GitHub, Stripe, Notion, Supabase, Vercel, Cloudflare, Slack, n8n, Figma, Clerk, Neon, PayPal, and major AI model APIs (Claude, OpenAI, Gemini). Google Drive, Meta Ads, WhatsApp Business, and Telegram are also available. Many connections use OAuth; others accept pasted API credentials when that’s what the vendor issues.
From .env roulette to one click
Notes from founders, freelancers and agency devs who stopped switching accounts by hand and gave their agents one key.
If you have more than 2 accounts on any service, you're already losing time.
No credit card required · 14-day free trial · cancel anytime
Tell us what you're juggling
Building agents across multiple accounts, clients or side projects? Tell us the services you connect and how your agents run—we'll show you the fastest path to one key and one-click switching.
Contact details
- Email: dtricoma@gmail.com
- Address: Barcelona, Spain, 08035
TuMCP concierge
Quick answers on integrations, quotas, and security posture.