Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Configure Concord MCP Server with ChatGPT

Concord's Model Context Protocol (MCP) connector makes Concord CLM securely available inside ChatGPT so teams can search, summarize, and act on contracts with natural language,  using OAuth and existing Concord permissions. 

Who this doc is for: ChatGPT workspace admins who will enable Developer mode, create the custom MCP connector, and publish it for the organization.

What this covers
  • Enable ChatGPT Developer mode and create a custom MCP connector.
  • Point it to the Concord MCP server and test the connection.
  • Publish the connector so it appears for your entire ChatGPT workspace.

MCP Server URL: https://mcp.concord.app/mcp 

Prerequisites

  • Admin access to your ChatGPT workspace.
  • A Concord account (Viewer role is sufficient).
  • ChatGPT Developer mode enabled.

1) Open ChatGPT settings → Apps & Connectors


Settings → Apps & Connectors catalog
chatgpt_dev_entry

2) Enable Developer mode

Developer mode allows adding custom (unverified) MCP connectors.


Advanced settings → Enable Developer mode
chatgpt_connectors_catalog

 

3) Create the connector

Click Create and fill the form:

  • Name: “Concord (Beta)” or “Concord CLM”
  • MCP Server URL: https://mcp.concord.app/mcp
  • Authentication: OAuth (leave Client ID/Secret blank)
  • Acknowledge the standard MCP warning.
Create New Connector — form
chatgpt_create_form

4) Sign in & authorize

You’ll be redirected to Concord for OAuth. Sign in and click Allow access.

Concord login (SSO/Google supported)
chatgpt_form_filled

Authorize ChatGPT to access your Concord account
chatgpt_login

5) Confirm connection (private)

After connecting, the connector is available only to you (the creator) until it is published.

6) Publish to your workspace

Publishing makes the connector visible to everyone in your ChatGPT organization. Each user must still click Connect once so the connector uses their own Concord credentials and permissions.

Connector actions menu → Publish
chatgpt_publish

FAQ

Do we need to enable anything inside Concord?
No additional toggle is required today. OAuth and permission checks occur automatically.

What role is required in Concord?
A Viewer seat is sufficient for setup; users inherit capabilities based on their Concord role.

Troubleshooting

  • No Create button: You may lack ChatGPT org admin rights. Ask an admin to create/publish.
  • 403 / Not authorized when running a tool: Your Concord role disallows that action; request access or try read‑only queries.
  • Tool calls seem to “hang”: ChatGPT UI offers limited live feedback; retry with a more specific prompt.

Security & Data

  • Authentication uses OAuth to your own Concord account; actions run under your permissions.
  • No shared credentials. Each user connects individually after publish.
  • Published connectors are visible org‑wide in ChatGPT; Concord permissions still control data access.