ProxyLoom

One MCP connection.Every account.

Claude, Codex and every other MCP client maintain a single connection per SaaS. ProxyLoom bundles multiple Slack workspaces, multiple Google accounts, multiple Notion workspaces, multiple Miro teams and multiple Figma accounts behind one MCP endpoint. All of them stay live at once.

No credit card. Free while in beta.

MCP client 1 CONNECTION ProxyLoom N WORKSPACES / ACCOUNTS Slack workspace A Slack workspace B Notion workspace A Notion workspace B Google Calendar account A Google Calendar account B Google Drive account A Google Drive account B

Use cases

Signing in to every client, one at a time?

MCP clients maintain a single connection per SaaS, so an account per client turns into constant re-authentication. ProxyLoom keeps them all connected at once — no more re-authenticating every time you switch clients.

Back-office & virtual assistants

Every client's Slack, calendar and Notion behind one connection — updates, scheduling and notes handled in one conversation.

“Post the minutes to client A's Slack, and summarize client B's schedule for next week.”

SlackGoogle CalendarNotion

Consultants & fractional PMs

Stop hopping between client workspaces. Review every engagement's activity across Slack and Notion in a single thread.

“Pull this week's movement across all client Slacks and give me one digest.”

SlackNotionMiro

More for consultants & PMs →

How it works

Connect once, then use them all

ProxyLoom sits between your MCP client and the SaaS — which is what lets you hold as many accounts and workspaces of the same service as you want, while your client still registers exactly one connection.

1. 01

   Pick the service you want to connect

   Choose the service on the ProxyLoom dashboard and you are taken straight to the provider's own consent screen. There is nothing to prepare first.
2. 02

   Authorize on the provider's own screen

   Choose the account or workspace on the SaaS consent screen and grant access. The second one works exactly the same way — and it does not replace the first.
3. 03

// one endpoint, every accountslack_send_message( account: "caret0", channel: "#release" )slack_send_message( account: "acme", channel: "#qa" )notion_search( account: "acme", query: "spec" )gcal_list_events( account: "you@example.com" )

Connectors

Unlimited accounts, and a growing lineup

The private beta covers Slack, Gmail, Google Calendar, Google Drive, Google Sheets, Notion, Miro, Figma, Granola, HubSpot and QuickBooks Online, with more on the way — and no limit on accounts per service.

Missing a connector you need? Tell us — requests drive the roadmap.

Send a request

Security

It holds your tokens, so it is built like it

A proxy that stores credentials for every account you own has to earn that.

Credentials encrypted at rest, per customer

Stored tokens are encrypted with keys that differ per customer, and decrypted in memory only at the moment of an upstream call.

Per-customer isolation enforced by the database

Separation between customers is enforced at the database layer, not by application code — so even a bug in our code cannot reach another customer's data.

We never look at relayed traffic

ProxyLoom never reads the content of the traffic it relays between your AI agent and your SaaS accounts — never inspected, never stored, never logged. The audit log records metadata only: which connection, which tool, when.

Deleting a connection revokes the stored token

Removing a connection deletes the stored token from ProxyLoom and sends a revocation request to the SaaS, so the credential is no longer valid on either side. *Limited to services that provide a revocation API.

Hosted in Japan

ProxyLoom runs entirely on infrastructure located in Japan, and credentials and audit records never leave the country.

Pricing

Free while in beta

ProxyLoom is in private beta. Every feature is free while the beta lasts.

Beta

Free

• Every feature included Start free

AI agents

Works with the AI you already use

Claude

ChatGPT

Codex

Cursor

…and any other MCP-compatible client

Product names and logos are trademarks of their respective owners.

FAQ

Frequently asked questions

Claude, Codex, and any other client that speaks Streamable HTTP MCP and OAuth 2.1. Registration is a single ProxyLoom URL — the proxy handles discovery and consent from there.

Each connection gets a routing key derived from the workspace or business you authorized, and you can give it a name of your own in the dashboard (e.g. “Northgate Trading”). Every relayed tool gains an account argument, and the model picks the connection from context using either name.

Not the payload. ProxyLoom never inspects the messages and tool calls it relays, and never writes them to logs. What it does store is your encrypted tokens and audit-log metadata — connection, tool, timestamp. Tokens are decrypted in memory just for the duration of an upstream call.

The stored token is deleted from ProxyLoom, and revoked at the SaaS where the service provides a revocation API (Slack, Google, …). No credential of yours stays behind in ProxyLoom.