# ![](/img/ai/claude.svg) Connect Claude to Comind.work

Claude supports MCP across three clients - the desktop app, the `claude` CLI (Claude Code), and the web app at claude.ai. The server URL and authentication are the same for all three; only the configuration location differs.

## Before you start[​](#before-you-start "Direct link to Before you start")

You need:

* Your **MCP server URL** - `https://mcp.comind.work/<your-company>` (ask your administrator for the company alias)
* Your **Comind.work credentials** for the OAuth sign-in flow. If you need to use a manual API token instead - see [authentication alternatives](/ai/authentication.md#manual-api-tokens-alternative)

## Claude Desktop[​](#claude-desktop "Direct link to Claude Desktop")

Claude Desktop reads MCP servers from its JSON config file.

1. Open Claude Desktop and go to **Settings > Developer > Edit Config**. This reveals `claude_desktop_config.json` in your file manager.

2. Add a `comind` entry under `mcpServers`:

   claude\_desktop\_config.json

   ```
   {
   	"mcpServers": {
   		"comind": {
   			"url": "https://mcp.comind.work/your-company"
   		}
   	}
   }
   ```

3. Save the file and restart Claude Desktop.

4. Open a new chat - Claude Desktop opens a browser window for you to sign in to Comind.work. Approve the requested scopes.

5. The MCP icon in the input bar should now list `comind` tools (`list_workspaces`, `list_records`, etc.).

On Anthropic's docs

For UI screenshots and the latest menu paths, see [Getting started with MCP on Claude for Desktop](https://support.claude.com/en/articles/10949351-getting-started-with-model-context-protocol-mcp-on-claude-for-desktop).

Using a manual token instead

If you need to use a long-lived API token instead of OAuth, add a `headers` block with `"Authorization": "Bearer YOUR-TOKEN-HERE"`. See [authentication alternatives](/ai/authentication.md#manual-api-tokens-alternative).

## Claude Code[​](#claude-code "Direct link to Claude Code")

Claude Code (the CLI) reads MCP servers from a per-project `.mcp.json` file or from user-level config.

### Per-project setup[​](#per-project-setup "Direct link to Per-project setup")

1. In your project root, create or edit `.mcp.json`:

   .mcp.json

   ```
   {
   	"mcpServers": {
   		"comind": {
   			"url": "https://mcp.comind.work/your-company"
   		}
   	}
   }
   ```

2. Restart any running `claude` sessions. On next startup the CLI prompts you to approve the new server, then opens a browser for OAuth sign-in.

### User-level setup[​](#user-level-setup "Direct link to User-level setup")

To make the server available in every project without committing `.mcp.json`, run:

```
claude mcp add --transport http comind https://mcp.comind.work/your-company
```

Then verify with `claude mcp list`. The first time you use the server in a session, Claude Code opens a browser for OAuth sign-in.

Using a manual token instead

Append `--header "Authorization: Bearer YOUR-TOKEN-HERE"` to `claude mcp add`, or add a `headers` block to `.mcp.json`. See [authentication alternatives](/ai/authentication.md#manual-api-tokens-alternative).

On Anthropic's docs

For the full set of Claude Code MCP commands (add, list, remove, project vs user scope, env-var interpolation), see [Connect Claude Code to tools via MCP](https://code.claude.com/docs/en/mcp).

## Claude.ai (web)[​](#claudeai-web "Direct link to Claude.ai (web)")

The web app supports MCP through **custom connectors**. Availability depends on your Claude plan - check **Settings > Connectors** to confirm.

1. Go to **Settings > Connectors**, click the `+` button, and choose **Add custom connector**.

   ![claude.ai Connectors page with the plus-menu open, showing the Add custom connector option](/assets/images/01-add-custom-connector-menu-1ef612736b7efcd627d7cacc0fd4cc28.png)

2. Fill in:

   * **Name** - `Comind.work`
   * **Remote MCP server URL** - `https://mcp.comind.work/your-company`

3. Click **Add** and complete the Comind.work sign-in in the browser popup.

   ![Add custom connector dialog filled in with Comind.work as the name and the mcp.comind.work server URL](/assets/images/02-add-connector-form-552f3e1fcbd362b5c576ca8c6c68ce9a.png)

   The Comind.work sign-in opens in a new tab and shows the standard [OAuth consent screen](/ai/authentication.md#oauth-default).

On Anthropic's docs

For the latest menu paths (this UI changes faster than the desktop app), see [About custom connectors using remote MCP](https://support.claude.com/en/articles/11175166-about-custom-connectors-using-remote-mcp).

Once connected, the connector appears under the `+` menu in new chats. Toggle it on to let Claude call Comind.work tools during the conversation.

![New chat with the plus-menu expanded, showing the Comind connector with its toggle switched on and the Manage connectors / Tool access submenu](/assets/images/03-connector-in-chat-menu-ea958e6ec578d86387090b0fe418f6c3.png)

### Manage tool permissions[​](#manage-tool-permissions "Direct link to Manage tool permissions")

Open **Settings > Connectors > Comind.work** to see the tools the connector exposes. Read-only tools (such as `list_records`, `search_records`) run automatically by default, while write/delete tools (`create_record`, `update_record`) can be set to require your approval before each call.

![Connector detail page showing read-only tools and write/delete tools with per-tool permission switches for approve, prompt, and block](/assets/images/04-tool-permissions-cb57212e8e6629895a6729a776716fa8.png)

OAuth only

The claude.ai web app does not accept manual API tokens - every connection goes through the OAuth sign-in flow. This is the same experience as the default setup on Claude Desktop and Claude Code.

## Verify the connection[​](#verify-the-connection "Direct link to Verify the connection")

In any of the three clients, ask:

> "List my Comind workspaces."

Claude should call `list_workspaces` and return the workspaces you have access to. If nothing happens, see [troubleshooting](#troubleshooting).

Once the basic connection works, you can ask richer questions that combine multiple tools - aggregations, month-over-month comparisons, cross-workspace summaries. Claude picks the right MCP calls and can render structured answers:

![Claude.ai chat showing a February vs March activity comparison returned via the Comind connector, with summary tiles and side-by-side bar charts](/assets/images/05-example-chat-4d1787c7442d0495e4e56e4fc209b5ed.png)

## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting")

**The MCP icon does not show `comind` tools** : Restart the client fully (quit from the tray, not just close the window). JSON syntax errors silently drop the server - validate with any JSON linter.

**401 or 403 responses** : The OAuth sign-in was cancelled or the token (if you are using the manual-token alternative) is wrong or expired. Sign in again, or check that the URL points to the correct company alias.

**OAuth browser window never appears** : Check that your firewall or browser is not blocking the localhost callback the client uses to complete the sign-in. Try in a different browser.

## Next steps[​](#next-steps "Direct link to Next steps")

* [MCP tools reference](/ai/mcp-tools.md) - what each tool does and how filters work
* [Authentication](/ai/authentication.md) - manual tokens vs OAuth
* [Claude Code setup for app development](/developer-guide/getting-started/claude-code-setup.md) - the complementary **comind-dev** plugin for building and deploying Comind.work apps with Claude Code