Connect your assistant
Step-by-step setup of the Sommet MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex and other MCP clients.
Every assistant needs the same URL:
https://api.sommet.dev/mcp
The first call opens Sommet in your browser to sign in and approve access. After that, the assistant stays connected.
Works in the Claude web, desktop and mobile apps. On Team and Enterprise plans, an owner may need to allow custom connectors first.
- Open Settings → Connectors.
- Select Add custom connector.
- Name it
Sommetand paste the URL. - Select Connect, then sign in to Sommet and select Allow.
In a chat, open the tools menu and check that Sommet is on.
Custom connectors need developer mode.
- Open Settings → Apps & Connectors, then Advanced settings, and turn on Developer mode.
- Select Create to add a connector.
- Name it
Sommet, paste the URL and choose OAuth as the authentication. - Save, then sign in to Sommet and select Allow.
In a chat, select + → Developer mode and turn on the Sommet connector.
Add Sommet to Cursor with one click, or add it to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):
{
"mcpServers": {
"sommet": {
"url": "https://api.sommet.dev/mcp"
}
}
}Then open Cursor Settings → MCP and select Connect next to Sommet.
For GitHub Copilot in agent mode. Add Sommet to VS Code with one click, or add it to .vscode/mcp.json:
{
"servers": {
"sommet": {
"type": "http",
"url": "https://api.sommet.dev/mcp"
}
}
}VS Code asks you to sign in the first time a tool runs.
Run in your terminal:
claude mcp add --transport http sommet https://api.sommet.dev/mcpThen type /mcp in Claude Code, select sommet and sign in. Add --scope project to share the server with your team through .mcp.json.
Run in your terminal:
codex mcp add sommet --url https://api.sommet.dev/mcpIf Codex does not open your browser, run codex mcp login sommet.
Any client that supports remote MCP servers with OAuth can connect with the URL. Windsurf, Zed, Goose, LibreChat and others work this way.
For a client that only supports local (stdio) servers, use the mcp-remote bridge:
{
"mcpServers": {
"sommet": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.sommet.dev/mcp"]
}
}
}Check the connection
Ask your assistant:
List my Sommet workspaces.
It calls list_workspaces and returns your domains. If it asks you to sign in again, your session ended: approve the connection again.
Troubleshooting
| Problem | What to do |
|---|---|
| The assistant does not open a sign-in page | Check the URL ends with /mcp. Remove the server and add it again. |
| “Could not complete the authorization” | Start the connection again from the assistant, not from an old browser tab. |
| The assistant answers without calling Sommet | Name it in the prompt: “Use the Sommet tools to…”. In ChatGPT, turn the connector on in the chat. |
| The assistant says the connection is read-only | It connected before write access existed. Disconnect it in Settings → AI assistants, then connect it again. |
| A workspace is missing | You see only the workspaces you are a member of. Ask the owner for an invitation. |