How to Use the Concord CLM MCP in Claude Code

Q: Can Claude Code search Concord CLM records from the terminal?

Yes. Invoke searchagreementsbyname via your command line interface. It fetches the relevant agreement data directly to your output stream.

Q: How do I get user details from Concord CLM in Claude Code?

Run the getcurrentuser tool. It returns your authentication profile so you can verify your connection settings.

Q: Does Claude Code support listing all users in Concord CLM?

It does. The listusers tool outputs your entire organization roster. This works perfectly for shell-based auditing.

Q: Can I check my signed agreements in Concord CLM using Claude Code?

You can. Use the listsignedagreements tool to pull a list of completed contracts. You can easily pipe this into a text file or JSON parser.

Connect Claude Code to your legal stack and automate contract tasks from the terminal.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Concord CLM MCP to Claude Code

Create your Vinkius account to connect Concord CLM to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Concord CLM with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

CLI-based agreement management

Automate contract creation by piping commands through `create_agreement` within your terminal. You can script the generation of new documents based on your templates. `list_templates` allows you to see what is available before you trigger a creation command. This keeps your build process moving without browser interference.

Terminal-driven signature workflows

Trigger the signature process via `send_for_signature` directly from your shell environment. This is ideal for CI/CD pipelines where you need to finalize documents based on build triggers. Use `list_signed_agreements` to verify completion. You can pipe this output into other shell tools to track your legal status.

System-level Concord CLM access

Query your entire system using `list_agreements` to get raw data for your logs. It provides the necessary state for any DevOps task you are running. `list_webhooks` provides the status of your event listeners. Use this to verify your API connections are active and ready to receive updates.

Setup guide

Set up Concord CLM MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see concord-clm-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Concord CLM transactions." It will automatically discover and invoke the available Concord CLM tools.

Terminal

claude mcp add --transport http concord-clm-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Concord CLM MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Concord. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Concord CLM now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Concord CLM MCP in Claude Code

Yes. Invoke `search_agreements_by_name` via your command line interface. It fetches the relevant agreement data directly to your output stream.

Run the `get_current_user` tool. It returns your authentication profile so you can verify your connection settings.

It does. The `list_users` tool outputs your entire organization roster. This works perfectly for shell-based auditing.

You can. Use the `list_signed_agreements` tool to pull a list of completed contracts. You can easily pipe this into a text file or JSON parser.

All traffic is routed through a secure, ephemeral Vinkius tunnel. Your document metadata and user credentials are never persisted beyond the life of your session.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript