How do I get my Concord API key?

Log in to the Concord web app, go to **Global Settings > API Keys**, and generate a new key. Copy it and paste it into the authentication field below.

Does this work with the Sandbox environment?

Yes. Set 'Use Sandbox?' to true in the credentials configuration to connect to the UAT environment instead of production.

Can I create documents from templates?

Yes. When using the 'create_agreement' tool, you can specify a templateId to generate a document based on a pre-existing template.

Concord CLM MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: Concord CLM
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Concord CLM and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "concord-clm": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Concord CLM MCP Server

Connect your AI assistant to Concord, the Contract Lifecycle Management (CLM) platform that centralizes how your team drafts, negotiates, signs, and stores contracts.

GitHub Copilot Agent mode brings Concord CLM data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Agreement Lookup — Search and retrieve any contract by name, ID or status directly through your AI chat.
Signature Workflows — Send agreements out for e-signature to internal or external parties without leaving your conversation.
Template-Based Creation — Create new agreements from pre-approved templates, automatically populating fields and routing them for review.

The Concord CLM MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Concord CLM to VS Code Copilot via MCP

Follow these steps to integrate the Concord CLM MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Concord CLM

Ask Copilot: "Using Concord CLM, help me...". 10 tools available

Why Use VS Code Copilot with the Concord CLM MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Concord CLM through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Concord CLM + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Concord CLM MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Concord CLM MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Concord CLM to VS Code Copilot via MCP:

create_agreement

Create a new agreement in Concord

get_agreement

Retrieve detailed information about a specific agreement

get_current_user

Retrieve details of the currently authenticated user

list_agreements

Retrieve a list of agreements from Concord CLM

list_signed_agreements

Quickly list all fully signed agreements

list_templates

Retrieve a list of document templates available in Concord

list_users

Retrieve a list of all users in your Concord organization

list_webhooks

Retrieve a list of configured webhooks

search_agreements_by_name

Find agreements by their name

send_for_signature

Trigger the signature process for a specific agreement

Example Prompts for Concord CLM in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Concord CLM immediately.

"Show me all signed contracts in Concord."

"Send agreement 'agr-4521' for signature."

"Check the status of agreement ID 'agr-8901'."

Troubleshooting Concord CLM MCP Server with VS Code Copilot

Common issues when connecting Concord CLM to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Concord CLM + VS Code Copilot FAQ

Common questions about integrating Concord CLM MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.