# How to connect Copper to Claude

```json
{
  "title": "How to connect Copper to Claude",
  "toolkit": "Copper",
  "toolkit_slug": "copper",
  "framework": "Claude Cowork",
  "framework_slug": "claude-cowork",
  "url": "https://composio.dev/toolkits/copper/framework/claude-cowork",
  "markdown_url": "https://composio.dev/toolkits/copper/framework/claude-cowork.md",
  "updated_at": "2026-10-04T16:13:48.071Z"
}
```

## Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.
This guide walks you through the easiest and most secure way to connect your Copper account to Claude via Composio Connect, enabling it to create a new lead from email, list open opportunities assigned to me, log a call and attach meeting notes, and more such actions on your behalf without compromising your account security.
Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

## Also integrate Copper with

- [ChatGPT](https://composio.dev/toolkits/copper/framework/chatgpt)
- [Hermes](https://composio.dev/toolkits/copper/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/copper/framework/atomic-agent)

## Connect Copper to Claude Cowork

### Connecting Copper to Claude Web, Desktop, and Cowork
Two ways to add the Composio connector. Pick whichever you prefer.
### 1. Add with one click
Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.
[Add to Claude](https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Composio&connectorUrl=https%3A%2F%2Fconnect.composio.dev%2Fmcp)
### Add manually
In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.
Click Add custom connector and paste in the Composio MCP server URL:

```bash
https://connect.composio.dev/mcp
```

## What is the Copper MCP server, and what's possible with it?

The Copper MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Copper account. It provides structured and secure access to your CRM records, activities, files, pipelines, and account settings, so your agent can create leads, find contacts, track opportunities, assign tasks, and review customer activity on your behalf.
- Lead and contact management: Have your agent create leads, people, and companies, find people by email, update records in bulk, or convert qualified leads into contacts, companies, and opportunities.
- Opportunity and pipeline tracking: Let the agent create opportunities and review your configured pipelines, stages, and win probabilities before adding new deals.
- Projects, tasks, and activities: Direct your agent to create projects, assign tasks with due dates and priorities, add notes or other activities, and review activity tied to leads, people, or companies.
- CRM record organization: Instruct your agent to connect related records, apply tags and custom fields, inspect field requirements, and remove records or relationships you no longer need.
- Files and account context: Have your agent list attached files, inspect file details, delete outdated attachments, and check the connected account or current user before assigning work.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `COPPER_BULK_CREATE_ACTIVITIES` | Bulk Create Activities (Beta) | Attempt to create 1-10 user-category Copper activities and return ordered per-item successes or validation failures. Deleting these activities is a soft delete: successful cleanup may leave an activity fetchable as an is_deleted=true stub rather than make it fully disappear. This Copper bulk endpoint is beta, accepts 1-10 records per request, returns results in request order, and has an additional limit of 3 requests per second. |
| `COPPER_BULK_CREATE_COMPANIES` | Bulk Create Companies (Beta) | Attempt to create 1-10 Copper companies and return ordered per-item successes or validation failures. This Copper bulk endpoint is beta, accepts 1-10 records per request, returns results in request order, and has an additional limit of 3 requests per second. |
| `COPPER_BULK_CREATE_LEADS` | Bulk Create Leads | Create 1-10 Copper leads in one beta bulk request and return ordered per-item outcomes. Copper can return HTTP 500 after applying the write; treat failures as indeterminate and read records back before retrying to avoid duplicates. |
| `COPPER_BULK_CREATE_OPPORTUNITIES` | Bulk Create Opportunities (Beta) | Attempt to create 1-10 Copper opportunities and return ordered per-item successes or validation failures. This Copper bulk endpoint is beta, accepts 1-10 records per request, returns results in request order, and has an additional limit of 3 requests per second. |
| `COPPER_BULK_CREATE_PEOPLE` | Bulk Create People (Beta) | Attempt to create 1-10 Copper people and return ordered per-item successes or validation failures. This Copper bulk endpoint is beta, accepts 1-10 records per request, returns results in request order, and has an additional limit of 3 requests per second. |
| `COPPER_BULK_UPDATE_COMPANIES` | Bulk Update Companies (Beta) | Attempt to update 1-10 Copper companies and return ordered per-item successes or validation failures. This Copper bulk endpoint is beta, accepts 1-10 records per request, returns results in request order, and has an additional limit of 3 requests per second. |
| `COPPER_BULK_UPDATE_LEADS` | Bulk Update Leads | Update 1-10 Copper leads in one beta bulk request and return ordered per-item outcomes. Copper can return HTTP 500 after applying the write; treat failures as indeterminate and read records back before retrying. |
| `COPPER_BULK_UPDATE_PEOPLE` | Bulk Update People (Beta) | Attempt to update 1-10 Copper people and return ordered per-item successes or validation failures. This Copper bulk endpoint is beta, accepts 1-10 records per request, returns results in request order, and has an additional limit of 3 requests per second. |
| `COPPER_CONVERT_LEAD` | Convert Lead | Convert a Copper lead into a person and optionally a company and opportunity; the original lead is removed. |
| `COPPER_CREATE_ACTIVITY` | Create Activity | Create a user-category activity such as a note on an existing Copper lead, person, company, opportunity, project, or task; system activities are read-only. |
| `COPPER_CREATE_COMPANY` | Create Company | Create a Copper company with domain, contact, ownership, tag, and custom-field data. |
| `COPPER_CREATE_CUSTOM_ACTIVITY_TYPE` | Create Custom Activity Type | Create a named Copper custom activity type with a supported icon. Custom activity types cannot be deleted; retire one with UPDATE_CUSTOM_ACTIVITY_TYPE using is_disabled=true. |
| `COPPER_CREATE_CUSTOM_FIELD_DEFINITION` | Create Custom Field Definition | Create a Copper custom field for selected record types. |
| `COPPER_CREATE_LEAD` | Create Lead | Create a Copper lead with contact, ownership, source, status, tag, and custom-field data. |
| `COPPER_CREATE_OPPORTUNITY` | Create Opportunity | Create a Copper opportunity. Only the name is required; Copper can supply the default pipeline and stage, and the primary contact is optional. |
| `COPPER_CREATE_PERSON` | Create Person | Create a Copper person with contact, company, ownership, tag, and custom-field data. |
| `COPPER_CREATE_PROJECT` | Create Project | Create a Copper project, optionally related to another record and assigned to a user. |
| `COPPER_CREATE_RELATED_LINK` | Create Related Link | Connect two existing Copper records through a Connect custom field. |
| `COPPER_CREATE_TASK` | Create Task | Create a Copper task with optional assignment, related record, due/reminder times, priority, tags, and custom fields. |
| `COPPER_DELETE_ATTACHED_FILE` | Delete Attached File | Permanently delete one file attached to a Copper lead, person, opportunity, company, or project. |
| `COPPER_DELETE_CUSTOM_FIELD_DEFINITION` | Delete Custom Field Definition | Permanently delete one Copper custom-field definition by ID. |
| `COPPER_DELETE_LEAD` | Delete Lead | Permanently delete one Copper lead by ID. |
| `COPPER_DELETE_RECORD` | Delete Record | Delete one Copper person, company, opportunity, project, task, or activity by type and ID. Deleting an activity is a soft delete: successful cleanup may leave it fetchable as an is_deleted=true stub rather than make it fully disappear. |
| `COPPER_DELETE_RELATED_LINK` | Delete Related Link | Delete one Copper Connect-field connection by related-link ID. |
| `COPPER_GET_ACCOUNT` | Get Account | Return the connected Copper account, timezone, and feature settings; use it to preflight features such as Leads. |
| `COPPER_GET_ATTACHED_FILE_METADATA` | Get Attached File Metadata | Get metadata for one file attached to a Copper lead, person, opportunity, company, or project. |
| `COPPER_GET_CURRENT_USER` | Get Current User | Return the Copper user represented by the connected account, including the user ID used for assignments. |
| `COPPER_GET_CUSTOM_ACTIVITY_TYPE` | Get Custom Activity Type | Return one Copper custom activity type's name, icon, enabled state, interaction behavior, and ownership metadata by ID. |
| `COPPER_GET_CUSTOM_FIELD_DEFINITION` | Get Custom Field Definition | Return one Copper custom field's data type, record availability, filterability, options, and currency configuration by definition ID. |
| `COPPER_GET_FIELD_LAYOUT` | Get Field Layout | Return enabled and create/edit requiredness metadata for one Copper entity type. Opportunities require pipeline_id; other entity types do not accept it. |
| `COPPER_GET_LEAD` | Get Lead | Return one Copper lead's contact, ownership, source, status, tags, and custom-field data by lead ID. |
| `COPPER_GET_PERSON_BY_EMAIL` | Get Person by Email | Return the unique Copper person record matching an exact email address. |
| `COPPER_GET_RECORD` | Get Record | Fetch one user, person, company, opportunity, project, task, or activity by its type and ID. |
| `COPPER_LIST_ATTACHED_FILES` | List Attached Files | List all files attached to one Copper lead, person, opportunity, company, or project. |
| `COPPER_LIST_CUSTOM_ACTIVITY_TYPES` | List Custom Activity Types | List Copper's default user-entered activity types and account-created custom activity types; system activity types and Notes are available through LIST_REFERENCE_VALUES with activity_types. |
| `COPPER_LIST_CUSTOM_FIELD_DEFINITIONS` | List Custom Field Definitions | Return Copper custom-field IDs, types, availability, and options needed to read, filter, and write custom field values. |
| `COPPER_LIST_ENTITY_ACTIVITIES` | List Lead, Person, or Company Activities | List selected activity types related to one Copper lead, person, or company; company results may also include activities from related people. |
| `COPPER_LIST_LEAD_STATUSES` | List Lead Statuses | List Copper lead status IDs, names, display order, and default selection for use in lead writes and searches. |
| `COPPER_LIST_PIPELINES` | List Pipelines | Return all configured Copper pipelines with their stages and win probabilities for opportunity creation and updates. |
| `COPPER_LIST_PIPELINE_STAGES` | List Pipeline Stages | List Copper opportunity stages for one pipeline, or omit pipeline_id for a flat cross-pipeline list; use LIST_PIPELINES when pipeline context and win probabilities are needed. |
| `COPPER_LIST_REFERENCE_VALUES` | List Reference Values | List one bounded set of Copper IDs used in write schemas: activity types, customer sources, contact types, or opportunity loss reasons. |
| `COPPER_LIST_RELATED_LINKS` | List Related Links | List Connect-field connections for one Copper source record, optionally narrowed to one Connect field. |
| `COPPER_LIST_RELATED_RECORDS` | List Related Records | List records related to one Copper entity, optionally restricted to a target record type. |
| `COPPER_LIST_TAGS` | List Tags | Return one alphabetical page of Copper tag names for filtering or assigning records. |
| `COPPER_LIST_USERS` | List Users | Return one page of Copper users for resolving assignee and owner IDs. |
| `COPPER_RELATE_RECORDS` | Relate Records | Create a direct relationship between two existing Copper records, preserving both record types and IDs. |
| `COPPER_SEARCH_ACTIVITIES` | Search Activities | Search Copper activities globally or for one parent record by activity type and date range, returning one page. |
| `COPPER_SEARCH_COMPANIES` | Search Companies | Search Copper companies by name, domain, ownership, contact type, location, date, or custom-field criteria and return one page. |
| `COPPER_SEARCH_LEADS` | Search Leads | Search Copper leads by identity, ownership, status, source, location, value, activity, date, tags, socials, or custom fields and return one page. |
| `COPPER_SEARCH_OPPORTUNITIES` | Search Opportunities | Search Copper opportunities by pipeline, stage, status, contact, company, value, date, ownership, or custom-field criteria and return one page. |
| `COPPER_SEARCH_PEOPLE` | Search People | Search Copper people by contact, company, ownership, tag, date, or custom-field criteria and return one page. |
| `COPPER_SEARCH_PROJECTS` | Search Projects | Search Copper projects by name, owner, tag, status, or custom-field criteria and return one page. |
| `COPPER_SEARCH_TASKS` | Search Tasks | Search Copper tasks by name, owner, tag, related project or opportunity, status, due date, or custom-field criteria and return one page. |
| `COPPER_UNRELATE_RECORDS` | Unrelate Records | Remove a direct relationship between two existing Copper records without deleting either record. |
| `COPPER_UPDATE_ACTIVITY` | Update Activity | Update the details, date, or both for an existing user-category Copper activity; at least one change is required, and system or deleted activities cannot be modified. |
| `COPPER_UPDATE_COMPANY` | Update Company | Update selected writable fields of an existing Copper company without replacing omitted fields. |
| `COPPER_UPDATE_CUSTOM_ACTIVITY_TYPE` | Update Custom Activity Type | Rename, change the icon, or enable or disable a Copper custom activity type. To retire a type, disable it with is_disabled=true; custom activity types cannot be deleted. |
| `COPPER_UPDATE_CUSTOM_FIELD_DEFINITION` | Update Custom Field Definition | Update one Copper custom-field definition by ID. |
| `COPPER_UPDATE_LEAD` | Update Lead | Update selected fields of a Copper lead without replacing omitted fields. |
| `COPPER_UPDATE_OPPORTUNITY` | Update Opportunity | Update selected writable fields of an existing Copper opportunity without replacing omitted fields. |
| `COPPER_UPDATE_PERSON` | Update Person | Update selected writable fields of an existing Copper person without replacing omitted fields. |
| `COPPER_UPDATE_PROJECT` | Update Project | Update selected writable fields of an existing Copper project without replacing omitted fields. |
| `COPPER_UPDATE_TASK` | Update Task | Update selected writable fields of an existing Copper task without replacing omitted fields. |
| `COPPER_UPLOAD_ATTACHED_FILE` | Upload Attached File | Get upload authorization from Copper, upload up to 20 MB of file bytes to Copper's fixed Amazon S3 bucket, and attach the uploaded key to one Copper lead, person, opportunity, company, or project. If a failure occurs after the S3 upload starts, the file may already be uploaded or attached; verify the record before retrying to avoid duplicate attachments. |
| `COPPER_UPSERT_LEAD` | Upsert Lead | Create or update a Copper lead by exact name, email, or custom-field match. Copper resolves matches through a search index that can lag recent writes by seconds, so upserting a just-created lead may insert a duplicate; wait and verify before retrying. Copper rejects ambiguous matches. |

## Supported Triggers

None listed.

## Troubleshooting

### 1. Why does Claude not use the Composio connector for Copper?

The connector can show as connected, but Claude must use it in each Copper conversation.
- Click + at the lower left of the chat, or type /.
- Hover Connectors.
- Turn on Composio.
- Ask Claude to connect to Copper again.

### 2. Why does Claude show an MCP server error before Copper connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Copper.
- Check that the connector URL is https://connect.composio.dev/mcp.
- Connectors run from Anthropic's cloud, so your device network is usually not the problem.
- Add the connector again from Customize > Connectors, then ask Claude to connect Copper.
- If it fails again, send the error and the ofid_ reference id to support@composio.dev.

### 3. Why does the Copper authorization link not work?

The Composio connector is one server. Your Copper account connects separately when Claude asks for it.
- If the browser does not open, or the link expires, ask Claude to retry the Copper connection.
- Composio creates a fresh Copper authorization link.
- Open that link in your browser and finish the Copper sign-in.

### 4. Why do Copper actions fail after they worked before?

The Copper connection can expire or lose permission.
- Ask Claude to inspect the Copper connection.
- If the connection is unhealthy, disconnect it when Claude prompts you.
- Reconnect the Copper account and retry the action.
- If Claude shows a permission prompt, approve it before Claude changes data in Copper.
- If the action still fails with a permission error, check that the connected account has that permission in Copper itself.

### 5. How do I switch to a different Copper account?

Claude can manage the Copper connection for you.
- Ask Claude to disconnect or delete the current Copper account.
- Ask Claude to connect Copper again.
- Open the new Composio authorization link for Copper.
- Sign in with the other Copper account in the browser.
- After the account connects, ask Claude to retry the Copper task.

### 6. Why is my Copper connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Copper connection works in Claude Web, Desktop, and Cowork.
- In Claude Desktop, open Customize > Connectors.
- Next to Composio, click ⋮ and click Clear cache.
- If Copper tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
- On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Copper.

## Creating MCP Server - Stand-alone vs Composio SDK

The Copper MCP server connects Claude Web, Desktop, and Cowork to your Copper account through Composio. Once connected, Claude can use the available Copper tools and triggers to complete tasks on your behalf.

## Complete Code

None listed.

## How to build Copper MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/copper/framework/chatgpt)
- [Hermes](https://composio.dev/toolkits/copper/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/copper/framework/atomic-agent)

## Related Toolkits

- [HubSpot](https://composio.dev/toolkits/hubspot) - HubSpot is an all-in-one marketing, sales, and customer service platform. It lets teams nurture leads, automate outreach, and track every customer interaction in one place.
- [Pipedrive](https://composio.dev/toolkits/pipedrive) - Pipedrive is a sales management platform offering pipeline visualization, lead tracking, and workflow automation. It helps sales teams keep deals moving forward efficiently and never miss a follow-up.
- [Salesforce](https://composio.dev/toolkits/salesforce) - Salesforce is a leading CRM platform that helps businesses manage sales, service, and marketing. It centralizes customer data, enabling teams to drive growth and build strong relationships.
- [Apollo](https://composio.dev/toolkits/apollo) - Apollo is a CRM and lead generation platform that helps businesses discover contacts and manage sales pipelines. Use it to streamline customer outreach and track your deals from one place.
- [Attio](https://composio.dev/toolkits/attio) - Attio is a customizable CRM and workspace for managing your team's relationships and workflows. It helps teams organize contacts, automate tasks, and collaborate more efficiently.
- [Acculynx](https://composio.dev/toolkits/acculynx) - AccuLynx is a cloud-based roofing business management software for contractors. It streamlines project tracking, lead management, and document sharing.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Affinity](https://composio.dev/toolkits/affinity) - Affinity is a relationship intelligence CRM that helps private capital investors find, manage, and close more deals. It streamlines deal flow and surfaces key connections to help you win opportunities.
- [Agencyzoom](https://composio.dev/toolkits/agencyzoom) - AgencyZoom is a sales and performance platform built for P&C insurance agencies. It helps agents boost sales, retain clients, and analyze producer results in one place.
- [Agile CRM](https://composio.dev/toolkits/agile_crm) - Agile CRM is a unified customer management platform combining contacts, sales pipelines, marketing, and support. Use it to centralize customer data, automate campaigns, and manage deals and tickets in one place.
- [Bettercontact](https://composio.dev/toolkits/bettercontact) - Bettercontact is a smart contact enrichment tool for finding emails and phone numbers. It helps boost lead generation with automated, waterfall search across multiple sources.
- [Blackbaud](https://composio.dev/toolkits/blackbaud) - Blackbaud provides cloud-based software for nonprofits, schools, and healthcare institutions. It streamlines fundraising, donor management, and mission-driven operations.
- [Blitz API](https://composio.dev/toolkits/blitz_api) - Blitz API is a people, company, and job search API with contact and company enrichment. Use it to enrich leads and accelerate sales outreach with accurate contact and firmographic data.
- [Brilliant directories](https://composio.dev/toolkits/brilliant_directories) - Brilliant Directories is an all-in-one platform for building and managing online membership communities and business directories. It streamlines listings, member management, and engagement tools into a single, easy interface.
- [Capsule crm](https://composio.dev/toolkits/capsule_crm) - Capsule CRM is a user-friendly CRM platform for managing contacts and sales pipelines. It helps businesses organize relationships and streamline their sales process efficiently.
- [Centralstationcrm](https://composio.dev/toolkits/centralstationcrm) - CentralStationCRM is an easy-to-use CRM software focused on collaboration and long-term customer relationships. It helps teams manage contacts, deals, and communications all in one place.
- [Clarify MCP](https://composio.dev/toolkits/clarify_mcp) - Clarify MCP is a CRM platform for managing companies, people, deals, meetings, tasks, lists, and campaigns. Use it to centralize CRM data and streamline sales and marketing workflows.
- [Clay](https://composio.dev/toolkits/clay) - Clay is a go-to-market data enrichment and workflow automation platform for searching people and companies, running routines, and querying workspace tables. It helps teams enrich leads, automate GTM workflows, and keep workspace data synchronized.
- [Clay MCP](https://composio.dev/toolkits/clay_mcp) - Clay MCP is a prospect enrichment service for researching companies and contacts. It runs enrichment providers and Clay functions to return enriched prospect data.
- [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Copper MCP?

With a standalone Copper MCP server, the agents and LLMs can only access a fixed set of Copper tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Copper and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Claude Cowork?

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Copper tools.

### Can I manage the permissions and scopes for Copper while using Tool Router?

Yes, absolutely. You can configure which Copper scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Copper data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)