How do I generate an API Key in Copper?

Log in to Copper, go to **Settings > API Keys**, and click 'Generate API Key'. Note that you also need the email address of an admin or the owner.

Does Copper integrate with my Gmail?

Yes, Copper is built for Google Workspace. This integration works alongside Copper's native Google features, allowing the agent to manage the same records you see in your inbox.

Can the agent log calls for me?

Yes! You can tell the agent to 'Log a call with John Doe about the new contract', and it will add an activity record to John's profile in Copper.

Copper CRM MCP Server for Claude Desktop 10 tools — connect in under 2 minutes

Name: Copper CRM
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 10 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

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 Copper CRM and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "copper-crm": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "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 Copper CRM MCP Server

Integrate Copper, the CRM designed for Google Workspace, directly into your AI workflow. Manage your entire sales pipeline and contact list using natural language.

Claude Desktop is the definitive way to connect Copper CRM to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

Lead Management — List, retrieve, and create leads to keep your pipeline moving.
Contact Tracking — Quickly find people and companies, and view their full profiles.
Sales Opportunities — Monitor deals and opportunities to stay on top of your revenue goals.
Activity Logging — Log calls, emails, and meetings directly to any record via chat.

The Copper CRM MCP Server exposes 10 tools through the Vinkius. Connect it to Claude Desktop 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 Copper CRM to Claude Desktop via MCP

Follow these steps to integrate the Copper CRM MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Copper CRM

Look for the 🔌 icon in the chat. your 10 tools are now available

Why Use Claude Desktop with the Copper CRM MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Copper CRM through the Model Context Protocol.

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Copper CRM + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Copper CRM MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Copper CRM MCP Tools for Claude Desktop (10)

These 10 tools become available when you connect Copper CRM to Claude Desktop via MCP:

create_lead

Creates a new lead record with identity properties and prepares it for pipeline entry. Create a new lead in the CRM

get_lead_details

Resolves granular profile data including contact history, custom field values, and system-level metadata. Get detailed information for a specific lead

get_person_details

Resolves individual profile data including email addresses, phone numbers, and associated entity linkages. Get detailed profile for a specific person

list_companies

Resolves company identity properties such as company IDs, legal names, and primary contact links. List all companies in the CRM

list_leads

Resolves lead identity properties including names, email addresses, and pipeline status across the CRM system boundary. List all leads in Copper CRM

list_opportunities

Resolves opportunity data including deal names, monetary values, closing dates, and current stage identifiers. List sales opportunities and deals

list_people

Resolves individual identity properties including unique identifiers, contact names, and associated organizations. List contacts (people) in Copper

list_projects

Resolves project identity properties and metadata for collaborative tracking. List all projects in Copper

list_tasks

Resolves actionable item properties including task descriptions, due dates, and associated CRM records. List tasks and follow-ups

log_activity

Resolves and links activity details, types, and parent entity identifiers across the CRM interaction boundary. Log a new activity (call, email, meeting) for a record

Example Prompts for Copper CRM in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Copper CRM immediately.

"List all leads that are currently in the 'New' status."

"Log a call activity for the lead 'TechCorp Solutions' regarding the pricing proposal."

"Show me my top 5 sales opportunities sorted by monetary value."

Troubleshooting Copper CRM MCP Server with Claude Desktop

Common issues when connecting Copper CRM to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Copper CRM + Claude Desktop FAQ

Common questions about integrating Copper CRM MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.