What this covers
- How to connect your Claude workspace to the Concord MCP server
Prerequisites
- Admin access to your Claude workspace.
- A Concord account (Viewer role is sufficient).
Overview
- Enable connectors for your organization in Admin settings.
- Add a custom connector that points to the Concord MCP server.
- Add a custom Name to the MCP Server (e.g Concord)
- Add the MCP Server URL:
https://mcp.concord.app/mcp - Users connect with their own Concord credentials via OAuth.
Step 1 — Open Admin settings
Step 2 — Add the Concord MCP connector
In Admin settings or personal Settings → Connectors, click Add custom connector. Enter a clear name and the MCP URL.
- Add a custom Name to the MCP Server (e.g Concord)
- Add the MCP Server URL:
https://mcp.concord.app/mcp - Advanced settings are optional and not required for the configuration of Concord's MCP Server
Step 3 — Confirm availability in Connectors
Step 4 — Set tool permission defaults
From Connectors → Concord → Configure set default tool permission policy (for example Needs approval / Always allow for read-only tools). Policies can be adjusted later.
Step 5 — Users complete OAuth
Each user clicks Connect and completes Concord OAuth to use their own permissions.
Notes
- Publishing concept is not required in Claude Web; availability is controlled by enabling the connector and permission policies.
- Permissions mirror Concord. Viewers get read-only behavior on documents they can access.
Troubleshooting
- If users cannot see the connector, verify it is enabled in Admin settings and appears under Connectors.
- For 403 errors when running tools, confirm the user’s Concord role grants the action.
- If OAuth does not appear, have the user disconnect and click Connect again.