This article walks through the setup for each assistant that connects to your Coodesh workspace over MCP (Model Context Protocol). If you are not familiar with MCP and the permissions an assistant receives, start with How to connect your AI Assistant (MCP).
Before you start
MCP is available for company accounts. You need to be logged in to Coodesh and belong to at least one workspace.
These are the only details any assistant will ask for:
Server address:
https://coodesh.com/mcpConnection type: remote server, Streamable HTTP transport (some clients call it HTTP). Do not choose SSE or stdio.
Authentication: OAuth, completed in your browser.
There is no API key to paste. If the assistant asks for a token or an authentication header, leave it empty: authorization happens in the browser, on the Coodesh screen.
Claude Code (terminal)
In your terminal, add the server:
claude mcp add --transport http --scope user coodesh https://coodesh.com/mcp
--scope user makes the connection available in every project. Without it, the server only applies to the folder you were in.
Then:
Open Claude Code and type
/mcp.Select coodesh and then Authenticate. Your browser opens the Coodesh authorization screen.
Log in, pick the workspaces and click Authorize.
To check it, run
claude mcp list. The server should show as Connected.
Claude Desktop and claude.ai
Free, Pro and Max plans:
Go to Settings > Customize > Connectors.
Click Add custom connector.
Enter the URL
https://coodesh.com/mcpand click Add. Leave the OAuth and header fields empty.Click Connect and finish the authorization in your browser.
Team and Enterprise plans: only the organization owner adds the connector, under Organization settings > Connectors > Add > Custom (if Claude asks for the type, choose Web). After that, each teammate goes to Customize > Connectors and clicks Connect to authorize with their own Coodesh account.
Inside a chat, use the + button to turn the connector on or off.
ChatGPT (app)
Open Settings > MCP servers and click Add server.
Name it Coodesh, choose Streamable HTTP and enter the URL
https://coodesh.com/mcp.Save it and click Restart.
In the server list, click Authenticate and finish the authorization in your browser.
To check it, type
/mcpin the composer: the server should appear among the connected ones.
Codex (command line)
Open ~/.codex/config.toml and add:
[mcp_servers.coodesh]
url = "https://coodesh.com/mcp"
Do not set a token or headers: Codex already uses OAuth by default for remote servers. Then run codex mcp login coodesh and finish the authorization in your browser. To check it, run codex mcp list.
GitHub Copilot (VS Code)
Using the setup assistant:
Open the command palette (
Ctrl+Shift+PorCmd+Shift+P) and run MCP: Add Server.Choose HTTP, enter the URL
https://coodesh.com/mcpand the name coodesh.Choose where to save it: your user profile, which applies to every project, or the current project only, in
.vscode/mcp.json.
Or by editing the file directly:
{
"servers": {
"coodesh": {
"type": "http",
"url": "https://coodesh.com/mcp"
}
}
}
Once saved, click Start and then Auth, in the shortcuts shown right above the server entry, and finish the authorization in your browser. In Copilot Chat, switch to Agent mode and click the tools icon to see what Coodesh made available.
In Visual Studio, JetBrains and Xcode the setup is the same: a remote HTTP server pointing to the same URL.
How to confirm it worked
Ask the assistant something simple, such as "which Coodesh workspaces can I access?". It should answer with your name and the workspaces you authorized. If it says it has no Coodesh tools available, the connection has not been authorized yet.
With the connection active, the assistant can, for example:
look up jobs, the jobs panel and applications, and change the status of an application;
list and open assessments, and invite people to an assessment;
search the Coodesh question library and your own company library;
look up the people in the workspace and the plan you are on.
If something goes wrong
The address must end in
/mcp, with no trailing slash.https://coodesh.comon its own does not work.Always choose HTTP (Streamable HTTP). If the client tries SSE or stdio, the connection fails.
"Authentication required" or a 401 error before you authorize is expected. That is the server asking you to log in. Use your assistant’s authentication step:
/mcpin Claude Code, Authenticate in ChatGPT,codex mcp loginin Codex, Auth in VS Code.The browser did not open, or the screen expired. The authorization is valid for 10 minutes. Repeat the authentication step and finish it without long pauses.
The assistant asks for a token or API key. There is no key for MCP. Leave the field empty and finish in the browser.
No workspace shows on the authorization screen. Your account has to be a company account with an admin, manager or business profile in at least one workspace. Ask whoever manages the account to add you.
The assistant cannot see a new workspace. Access is fixed at the moment you authorize. Reconnect and select the missing workspace.
You switched Coodesh accounts. Disconnect the assistant under My account > Security and connect again with the right account.
Permissions and disconnecting
The assistant never has more permissions than you already have, and access covers only the workspaces you selected. To review or revoke it, go to My account > Security, in the Connected assistants card. Each permission is detailed in How to connect your AI Assistant (MCP).
