On Claude Team and Enterprise plans, the Coodesh connector has to be published once by an organization administrator. After that, each person on the team connects their own account. This article walks through that process, screen by screen.
If you are not sure yet what MCP is and which permissions the assistant gets, start with How to connect your AI assistant (MCP). To set up other assistants, see How to set up MCP in Claude, ChatGPT, Codex and Copilot.
Before you start
Requirement | Detail |
Claude plan | Team or Enterprise. Free, Pro and Max plans have no organization settings: each person adds the connector directly under Settings > Customize > Connectors. |
Your role in Claude | Owner or Primary Owner. Other roles cannot see the screen used here. |
Coodesh plan | Company account with MCP included. |
Coodesh account | Everyone who uses the connector needs an active login and must belong to at least one workspace. |
API key | Not required. Authorization happens through OAuth, in the browser. |
Server address: https://coodesh.com/mcp, with no trailing slash. The address api.coodesh.com does not answer MCP requests.
About the screenshots: they were taken in a demo organization, with the interface in Portuguese. The layout is identical in every language.
1. Open the organization connector list
In Claude, go to Organization settings and, in the side menu, click Connectors, under Libraries and Access.
2. Choose to add a custom connector
Click Add connector, at the top right of the list, then Custom. The All available option only shows Anthropic's ready-made catalog, which does not include Coodesh.
3. Select the Web type
In the submenu, choose Web. The Coodesh connector is a remote server reached over HTTPS. Desktop is for extensions installed on each computer, which is not the case here.
4. Enter the name and the server address
Fill in the two fields on step 1 of 2:
Name:
Coodesh. This is the label your team sees in the connector list.MCP server URL:
https://coodesh.com/mcp
The Continue button only becomes active once both fields are filled in.
5. Check the authentication options
When you continue, Claude queries the Coodesh server and fills in step 2 on its own. Two options appear with a Detected tag, confirming that the server responded:
Sign in now: each person logs in through Coodesh before using any tool.
Register automatically: Claude registers itself as an OAuth client on the server as users connect.
Nothing needs to be changed on this screen. Leave the custom OAuth client and the request header fields empty.
6. Check the transport under Advanced
Optional, but worth checking. Open the Advanced section and confirm the transport is set to Streamable HTTP. The Coodesh server does not use SSE.
Managed authorization appears disabled when the organization does not use an identity provider compatible with SSO. That does not prevent the connector from working.
7. Finish with Add
Click Add. The message Custom connector added confirms it was created, and the details window opens next.
8. Adjust permissions, if you want to
Still in the details window, two tabs let you refine the connector for the whole organization:
Configuration: which login methods are enabled. At least one has to stay active.
Tools: per-tool restrictions, in case you want to expose only part of what the server offers.
9. Confirm the connector in the list
Close the window. The Coodesh connector now appears in the list as Web / Custom with Individual authorization, meaning each member signs in with their own account.
What each team member does next
Publishing the connector grants no data access on its own: it only makes the connector appear in the available list. Each person still connects their own account:
In Claude, open Settings > Customize > Connectors.
Find Coodesh in the list and click Connect.
Sign in on the Coodesh authorization screen that opens in the browser.
Select which workspaces the assistant may access.
Click Authorize.
To check it worked, ask the assistant: "which Coodesh workspaces can I access?". It should list the authorized workspaces.
The assistant never has more permission than the person who authorized it, and access is limited to the selected workspaces.
How to remove or revoke access
You, the administrator: remove the connector from the options menu in the organization connector list. It disappears for every member.
Each person: in Coodesh, under My account > Security, the Connected assistants card lists active authorizations. Disconnect revokes access immediately.
If something goes wrong
Symptom | What to check |
The server does not respond | The URL has to end in |
401 error before authorizing | That is expected. The server requires OAuth and only responds after login. |
Authorization never completes | The authorization screen expires after 10 minutes. Start the connection flow again. |
The assistant lists nothing | Confirm the person belongs to a workspace and selected at least one on the authorization screen. |
Transport error | Use Streamable HTTP. The server accepts neither SSE nor stdio. |
The organization screen is missing | It exists only on Team and Enterprise plans, and only for Owners. |
Anthropic's documentation on custom connectors is at Get started with custom connectors using remote MCP. For anything on the Coodesh side, reach us through the platform chat.