The right account.
Every call.

Plug every MCP server and account into one endpoint. The right one answers for whatever repo you're in.

Your tools, connected.Clients → endpoint → accounts
Claude Cursor Codex distributorOne MCP endpoint Notion / work Team workspace Notion / personal Your own workspace Other servers GitHub, Linear, and more Claude · Cursor · Codex distributorOne MCP endpoint Notion / work Notion / personal
One endpoint in each client. Your accounts live here.See the setup

Connections

Your accounts.
All in the same place.

Connect a server once, then use it from Claude, Cursor, or Codex. Add another account when you need it. Each keeps its own name.

ConnectionsExample workspace
notion/workTeam workspace
Connected
notion/personalA separate account. Same provider.
Connected
github/workEngineering
Connected
Find a server or paste its URL
Profiles / workExample
Work

The accounts for this project

ProviderConnection
Notionnotion/work
GitHubgithub/work
Supabasesupabase/staging
Client profilework

Profiles

Give each project
its own accounts.

Work repo, work workspace. Notes app, personal workspace. A profile maps each provider to the account you want to use.

The tool name stays the same. The destination changes with the project.

Call history

See where
the call went.

Open the log to see the tool, the selected account, and why it was chosen. If a call stops, the decision is recorded too.

Open your call history
Call detailExample

notion.search

Find the launch notes

Account
notion/work
Profile
work
Selected by
profile_default
Decision
Allowed

Forwarded to the work account

Get your first server connected.

Start in the dashboard. Add your accounts, then copy your endpoint into the clients you use.

  1. Create your endpoint

    Sign up to get your MCP endpoint. Use an API key for clients that accept one, or sign in through OAuth when the client requires it.

  2. Connect your accounts

    Find the server in Connections, or paste its URL. Sign in with the provider or add its API token. You can connect a second account under a different name.

  3. Group into profiles

    A profile maps providers to accounts. Work gets one, personal gets another.

  4. Point your tools at it

    Add the endpoint to Claude, Cursor, Codex, whatever else speaks MCP. From then on you make changes in the Distributor dashboard and every client sees them on its next call. Those configs stay closed.

Bring your servers.

Find them in the directory, or connect by URL.

Browse servers
NotionGitHubLinearSupabaseCloudflareSentry

FAQ

The questions people ask before adding it.

What changes in Claude, Cursor, or Codex?+−

Add your Distributor endpoint to each client. The CLI can also bridge a client that expects a local stdio server to your hosted endpoint.

I have two Notion workspaces. How does it pick?+−

Each workspace is its own connection with its own name: notion/work, notion/personal. Your profile maps the provider to one of them per project. Inside the work repo, calls go to the work workspace. In your notes app, personal. Override by hand whenever you want.

What keeps a call from hitting prod by accident?+−

Environment tags. When routing is ambiguous and one of the options is prod, Distributor stops and asks instead of guessing. You can also require confirmation on every prod write, even an unambiguous one.

Do I have to know server URLs?+−

No. The dashboard has a directory of the big ones (Notion, GitHub, Linear, Stripe and about twenty more), one click each. For anything else, paste the URL and Distributor figures out what it's talking to. Servers that need OAuth walk you through sign-in.

What do you store?+−

Your connections, your tool list, and a log of every call: tool, account, reason, duration. Results pass through to your client. They aren't kept.