Two workspaces in Claude: one Koltrix connector for each
Run more than one Koltrix workspace? Claude will not add the same connector address twice. Here is how to connect each one separately and tell them apart.
On this page(9 sections)
Many people who run a business also run a side project, a client's company or a second brand. In Koltrix each of those can be its own workspace, with its own mailboxes, team and plan. Connecting an AI assistant to all of them raises a small puzzle: Claude and ChatGPT refuse to add a connector whose address they already have. So how do you connect two workspaces?
This post explains the answer, why it is built the way it is, and a short routine for using two workspaces without mixing them up.
The short version
One connection reads one workspace. To connect a second workspace, add a second connector with its own address:
https://mcp.koltrix.com/mcp?workspace=your-workspace-slug
The part after ?workspace= is the workspace's short name. To the assistant it is a different address, so it accepts it. To Koltrix it is a hint: the sign-in screen opens with that workspace already selected. Nothing else about the connection changes.
Why one connector per workspace
It would be convenient if a single connection could see everything you belong to. We chose not to do that, for a reason that matters for email.
When you approve a connection, you approve it for one workspace and for specific permissions. If one approval covered every workspace, then reading your personal project's inbox could also expose a client's inbox, simply because both happen to be yours. Keeping them apart means:
- What you approved for one workspace never reaches another.
- You can allow reading in one workspace and nothing more, while giving another workspace organizing and drafting.
- Removing one connector cuts off one workspace and leaves the other working.
It costs one extra setup step. For mail, that trade is a good one. The background on what each permission allows is in MCP and OAuth permissions explained for email.
Connecting the second workspace
You need to be a member of both workspaces. If you have not connected an assistant before, start with connecting Claude to Koltrix step by step and come back.
- In Koltrix, open Settings, then Connect AI apps. When you belong to more than one workspace the page asks which workspace the connection is for. Choose one and the address it shows already includes
?workspace=. - In Claude, add a custom connector and paste that address. Give it a name that says which workspace it is, such as "Koltrix, Acme" or "Koltrix, Studio".
- Sign in when Claude sends you to Koltrix. The approval screen opens on the workspace you chose. Check the name, review the permissions and approve.
- Repeat for the next workspace, with its own address and its own name.
If you already have the plain address connected for one workspace, you do not need to remove it. Add the second one beside it.
Checking which workspace you are in
Two connectors with similar names are easy to confuse, so the assistant can tell you directly:
whoamisays which workspace this connector reads, your role there, the permissions this connection was given and whether the workspace is read-only.list_workspaceslists every workspace you belong to, with the connector address for each. It is the quickest way to find the address of a workspace you have not connected yet.
A habit worth building: when you start a conversation that touches mail, ask "Which workspace is this connector reading?" once. It takes a second and prevents the one mistake that matters, drafting a reply in the wrong company's voice.
Using two workspaces day to day
A few practices keep things clear.
Name connectors after the workspace, not the tool. "Koltrix" twice is a trap. "Koltrix, Acme" and "Koltrix, Studio" are not.
Say the workspace in your request. "In the Studio inbox, show what needs a reply" is better than relying on which connector the assistant picks. If you are unsure, ask it to check with whoami first.
Do not copy mail between workspaces through the chat. An assistant can read a thread in one workspace and write a draft in another if both are connected, but ask yourself whether the people in that thread expect their message to travel. The safe default is to keep each client's mail where it is.
Keep the permissions different on purpose. For a client workspace you only look after, read-only access may be enough. For your own company you might also allow labels, archiving and drafts. The assistant can organize and write drafts; it cannot send mail on your behalf unless you have turned that on for that workspace. Drafts always wait for you to review and send them in Koltrix, as described in safe sending from Claude.
What the assistant can do in each workspace
Within one connected workspace, the tools are the same as before. Reading tools include searching mail, opening a conversation, listing what needs a reply and listing what is assigned to you. Organizing tools include labels, archive, snooze, read and unread and starring, and all of them can be undone. A handful of tools about the workspace itself, such as domain status and plan usage, are for owners and admins only.
The full list, with what each one returns, is in every tool in the Koltrix MCP server explained.
If something goes wrong
- The assistant says the connector already exists. Check that the address includes
?workspace=and a different slug from the one you added before. - The approval screen opens on the wrong workspace. You can pick another workspace on that screen before approving. If the slug in the address is misspelled, the screen falls back to your default workspace, so look at the name before you approve.
- A tool answers that the workspace is read-only. A workspace whose trial ended or whose payment lapsed cannot be changed by an assistant, and it may only show a limited amount of message content. Fix the plan in Koltrix and the connector works again.
- Nothing connects at all. The checks in troubleshooting the Koltrix MCP connection apply to each connector in the same way.
A short checklist
- Open Connect AI apps and choose the workspace for this connection.
- Copy the address that includes
?workspace=. - Add it as a new custom connector named after the workspace.
- Approve it on the sign-in screen, after checking the workspace name.
- Repeat for each workspace, never reusing an address.
- Run
whoamiin each connector once to confirm it reads what you expect. - Give each workspace only the permissions you want an assistant to have there.
Key takeaways
Claude will not add the same address twice, so each Koltrix workspace gets its own connector address with a ?workspace= hint. That one-per-workspace design is deliberate: an approval covers one workspace, so connecting a second never widens what the first allows. Name your connectors clearly, confirm the workspace with whoami and keep permissions as narrow as the work needs. For an overview of what you can ask once connected, see what MCP for email is, or the MCP page for the current tool list.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
