Copper
Copper is a customer relationship management platform for managing contacts, companies, leads, opportunities, projects, tasks, activities, files, and webhooks.
Verdict
Common use cases
- Enrich inbound leads with research notes
- Log discovery call outcomes as activities
- Update pipeline stages after weekly review
- Create contacts from event attendee lists
- Draft quarterly account health summaries
Integration
- Vendor
- Copper
- Category
- crm
- Auth
- API_KEY
- Tools
- 50
- Composio slug
copper
Tools
- 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 r
- 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 re
- 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.
- 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
- 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 reque
- 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 re
- 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.
- 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 reque
- Convert Lead
Convert a Copper lead into a person and optionally a company and opportunity; the original lead is removed.
- 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.
- Create Company
Create a Copper company with domain, contact, ownership, tag, and custom-field data.
- 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.
- Create Custom Field Definition
Create a Copper custom field for selected record types.
- Create Lead
Create a Copper lead with contact, ownership, source, status, tag, and custom-field data.
- 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.
- Create Person
Create a Copper person with contact, company, ownership, tag, and custom-field data.
- Create Project
Create a Copper project, optionally related to another record and assigned to a user.
- Create Related Link
Connect two existing Copper records through a Connect custom field.
- Create Task
Create a Copper task with optional assignment, related record, due/reminder times, priority, tags, and custom fields.
- Delete Attached Filedestructive
Permanently delete one file attached to a Copper lead, person, opportunity, company, or project.
- Delete Custom Field Definitiondestructive
Permanently delete one Copper custom-field definition by ID.
- Delete Leaddestructive
Permanently delete one Copper lead by ID.
- Delete Recorddestructive
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.
- Delete Related Linkdestructive
Delete one Copper Connect-field connection by related-link ID.
- Get Account
Return the connected Copper account, timezone, and feature settings; use it to preflight features such as Leads.
- Get Attached File Metadata
Get metadata for one file attached to a Copper lead, person, opportunity, company, or project.
- Get Current User
Return the Copper user represented by the connected account, including the user ID used for assignments.
- Get Custom Activity Type
Return one Copper custom activity type's name, icon, enabled state, interaction behavior, and ownership metadata by ID.
- Get Custom Field Definition
Return one Copper custom field's data type, record availability, filterability, options, and currency configuration by definition ID.
- 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.
- Get Lead
Return one Copper lead's contact, ownership, source, status, tags, and custom-field data by lead ID.
- Get Person by Email
Return the unique Copper person record matching an exact email address.
- Get Record
Fetch one user, person, company, opportunity, project, task, or activity by its type and ID.
- List Attached Files
List all files attached to one Copper lead, person, opportunity, company, or project.
- 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.
- List Custom Field Definitions
Return Copper custom-field IDs, types, availability, and options needed to read, filter, and write custom field values.
- 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.
- List Lead Statuses
List Copper lead status IDs, names, display order, and default selection for use in lead writes and searches.
- List Pipelines
Return all configured Copper pipelines with their stages and win probabilities for opportunity creation and updates.
- 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.
- List Reference Values
List one bounded set of Copper IDs used in write schemas: activity types, customer sources, contact types, or opportunity loss reasons.
- List Related Links
List Connect-field connections for one Copper source record, optionally narrowed to one Connect field.
- List Related Records
List records related to one Copper entity, optionally restricted to a target record type.
- List Tags
Return one alphabetical page of Copper tag names for filtering or assigning records.
- List Users
Return one page of Copper users for resolving assignee and owner IDs.
- Relate Records
Create a direct relationship between two existing Copper records, preserving both record types and IDs.
- Search Activities
Search Copper activities globally or for one parent record by activity type and date range, returning one page.
- Search Companies
Search Copper companies by name, domain, ownership, contact type, location, date, or custom-field criteria and return one page.
- Search Leads
Search Copper leads by identity, ownership, status, source, location, value, activity, date, tags, socials, or custom fields and return one page.
- Search Opportunities
Search Copper opportunities by pipeline, stage, status, contact, company, value, date, ownership, or custom-field criteria and return one page.
Setup
Setup guide
- 11. Open your Switchy workspace settings and navigate to the Integrations tab. 2. Click 'Add MCP' and select Copper from the CRM category. 3. Log into your Copper account in a separate tab and go to Settings → Integrations → API Keys. 4. Generate a new API key and copy it to your clipboard. 5. Paste the key into Switchy's connection dialog and click 'Connect'. 6. Switchy will test the connection by fetching your Copper account metadata; wait for the green checkmark. 7. Inside any Project, type '@Copper' in a message to confirm the MCP appears in the autocomplete menu. 8. Send a test prompt like '@Copper list the five most recent leads' to verify the integration works. 9. If the response returns lead data, the setup is complete and your team can start invoking Copper tools in any Project conversation.
What teammates see: by default, memories from Copper are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Enrich New Leads
@Copper fetch the ten leads created this week, then research each company's recent news and suggest two personalized talking points per lead.
Log Meeting Notes
@Copper create activities for today's discovery call with Acme Corp: discussed pricing tier, next step is demo on Friday, assign to Sarah.
Update Pipeline Stages
@Copper move these five opportunity IDs to 'Proposal Sent' stage and add a note that we're waiting on procurement approval.
Bulk Add Contacts
@Copper create contacts for these attendees from yesterday's webinar: Jane Doe jane@example.com, John Smith john@another.com, tag them 'Webinar Q1'.
Draft Account Reviews
@Copper pull all activities and open opps for these three companies in the last 90 days, then draft a one-paragraph health summary for each.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@copper show me all open opportunities in the 'Enterprise' pipeline stage with a value over $50k
Found 7 open opportunities matching your criteria: 1. Acme Corp Expansion – $125,000 (stage: Negotiation, owner: Sarah Chen) 2. TechStart Platform Migration – $89,500 (stage: Proposal Sent, owner: Marcus Lee) 3. GlobalRetail Integration – $67,200 (stage: Discovery, owner: Sarah Chen) 4. DataFlow Enterprise License – $55,000 (stage: Negotiation, owner: Jordan Kim) 5. CloudSync Multi-Year Deal – $180,000 (stage: Proposal Sent, owner: Sarah Chen) 6. FinanceHub Upgrade – $72,300 (stage: Discovery, owner: Marcus Lee) 7. SecureNet Partnership – $95,400 (stage: Negotiation, owner: Jordan Kim) Total pipeline value: $684,400. This is an illustrative example showing typical search results from Copper's opportunity records.
Demonstrates Copper's core read capability for filtering CRM records by custom fields and standard properties. Requires API key with read access to opportunities. Results reflect your team's actual pipeline data, so output shape varies by account configuration and custom field definitions.
@copper create a new lead for Jamie Rodriguez at Vertex Solutions, email jamie@vertexsol.com, mark as 'Inbound Demo Request' status
Successfully created lead in Copper: **Jamie Rodriguez** – Vertex Solutions • Email: jamie@vertexsol.com • Status: Inbound Demo Request • Lead ID: 18472639 • Created: 2025-06-14 at 3:42 PM UTC • Assigned to: (unassigned – you can update owner separately) This lead is now visible in your Copper dashboard under the 'Inbound Demo Request' status filter. This example shows a typical creation response; actual field availability depends on your Copper workspace configuration.
Showcases Copper's write capability for capturing new leads. The MCP uses Copper's beta bulk endpoint even for single records, so you may see ordered success/failure arrays in raw responses. Side-effect: this creates a permanent record in your CRM until manually deleted or archived.
@copper review all activities logged for Acme Corp in the last 30 days and draft a summary email updating our VP of Sales on relationship progress
Based on 12 activities logged for Acme Corp over the past 30 days: **Key Highlights:** • 4 discovery calls completed (avg duration 45 min) with CTO and procurement team • 2 product demos delivered; technical requirements doc shared June 8 • 3 follow-up emails sent addressing security compliance questions • 1 in-person meeting at their Seattle office (June 12) • Pricing proposal sent June 10; awaiting feedback by June 18 **Draft Email:** Subject: Acme Corp – Deal Update (Strong Progress) Hi [VP Name], Quick update on Acme: we've had excellent engagement this month with four substantive calls and an on-site visit. Their CTO is aligned on technical fit, and procurement is reviewing our proposal. Next milestone: pricing feedback expected by June 18. Confidence level is high—recommend we prepare contract templates this week. This is an illustrative synthesis combining Copper activity data with AI-generated narrative.
Highlights Copper's ability to surface historical activity data paired with AI reasoning to generate executive summaries. Requires read access to activities and companies. Output quality depends on how consistently your team logs activities in Copper—sparse data yields thin summaries.
Use-case deep-dives
When bulk lead creation beats manual CRM entry after events
A three-person sales team returns from a conference with 80 business cards and a spreadsheet of booth conversations. The Copper MCP's bulk lead creation tool writes 1-10 records per call, so you'll batch the import into nine requests through Switchy. Each batch returns per-item success or validation errors, which means you catch duplicate emails or missing required fields without losing the entire import. The beta status matters: Copper can return HTTP 500 after the write succeeds, so your agent needs to read records back to confirm. If your team runs more than two conferences per quarter and the lead volume stays under 200 per event, this MCP pays off in the first month. Above that threshold, consider a dedicated ETL tool with retry logic.
Why this MCP works for small-team opportunity cleanup
A four-person customer success team reviews stale opportunities every Monday morning. They flag deals stuck in 'Proposal Sent' for over 30 days and bulk-update the stage to 'Closed Lost' or reassign the owner. The Copper MCP handles 1-10 opportunity updates per call, so a typical Monday session processes 20-40 records in three to five agent turns. The ordered per-item response tells you which updates failed validation, usually because a custom field constraint changed or a user was deactivated. This workflow breaks down when your pipeline grows past 500 active opportunities, because the search-and-filter step before the bulk update becomes the bottleneck. For teams under that size, the MCP keeps your pipeline accurate without opening the Copper UI.
When activity logging from Zendesk hits Copper's batch limits
A six-person support team wants every closed Zendesk ticket logged as a Copper activity against the customer's company record. The MCP's bulk activity creation writes 1-10 records per request, so syncing 50 daily ticket closures requires five to six agent calls. The soft-delete behavior means cleanup is messy: a failed batch leaves orphaned activities that show in Copper's UI but can't be hard-deleted via API. If your ticket volume stays under 100 per day and you tolerate occasional duplicate activities, this MCP automates the logging without a Zapier subscription. Above 100 tickets daily, or if your compliance team requires audit-clean deletes, you need a purpose-built integration that handles Copper's beta endpoint quirks and retry logic natively.
Frequently asked
What does the Copper MCP let me do in Switchy?
The Copper MCP gives your AI agents direct read-write access to your CRM: create and update leads, people, companies, opportunities, and activities in bulk. Agents can pull pipeline data, log customer interactions, and keep deal stages current without switching tabs. All 50 tools use your Copper API key, so changes appear instantly in your team's CRM.
Do I need admin access to connect Copper?
You need a Copper API key, which any user can generate from their personal settings. Admin rights are not required to connect the MCP, but the key inherits your Copper permissions—if you can't edit a record in Copper's UI, the agent can't either. One team member connecting the integration makes it available to everyone in your Switchy workspace.
Can the Copper MCP delete records or is it read-only?
The MCP can create and update records in bulk (up to 10 at a time) and soft-delete activities. It cannot hard-delete leads, people, companies, or opportunities—Copper's API doesn't expose that. If you need to remove a record permanently, do it in Copper's UI. The integration is not read-only; agents will write to your live CRM.
Why use this instead of Copper's native automations?
Copper's automations trigger on fixed rules; the MCP lets an AI agent decide what to update based on conversation context, Slack threads, or data from other tools in Switchy. If your workflow is predictable, stick with Copper's built-in triggers. If you need an agent to enrich a lead by cross-referencing three other apps, the MCP is faster than building Zapier chains.
Who on the team should connect the Copper integration?
Connect it once with an API key from someone who has visibility into the records your agents will touch—typically a sales ops lead or CRM admin. That person's permissions apply to every agent action. If your team has strict role boundaries in Copper, create a dedicated service account with the right scope before plugging in the key.