Copper MCP server for Claude, ChatGPT, Claude Code and Cursor

How to connect Copper

1. 1
   Click Connect Copper free and paste your Copper API key.
2. 2
   Add ContextGate to your AI app:

   ClaudeChatGPTClaude CodeCursorGitHub CopilotCodexGemini CLIOther

   1. 1

      In Claude, open Settings → Connectors and click Add custom connector.

   2. 2

      Name it ContextGate and paste this URL:

      https://api.contextgate.ai/mcp

   3. 3

      Click Add, then Connect, and sign in to ContextGate.

   4. 4

      In a chat, turn ContextGate on from the + menu → Connectors. Cowork and the desktop app use the same connectors.

   The full Claude guide

   1. 1

      In ChatGPT settings, open Apps & Connectors (or Connectors) → Advanced and turn on Developer mode.

   2. 2

      Create a connector, choose OAuth, and paste this URL:

      https://api.contextgate.ai/mcp

   3. 3

      Sign in to ContextGate when ChatGPT redirects you, then pick the connector in a chat.

   The full ChatGPT guide

   1. 1

      Run this in a terminal:

      claude mcp add --transport http contextgate https://api.contextgate.ai/mcp

   2. 2

      Start Claude Code, run /mcp, choose contextgate and sign in to ContextGate.

   The full Claude Code guide

   Add to Cursor

   1. 1

      Click Add to Cursor, or add this to ~/.cursor/mcp.json:

      {
        "mcpServers": {
          "contextgate": {
            "url": "https://api.contextgate.ai/mcp"
          }
        }
      }

   2. 2

      In Cursor Settings → MCP, sign in to ContextGate when Cursor asks.

   The full Cursor guide

   Add to VS Code

   1. 1

      Click Add to VS Code, or add this to .vscode/mcp.json:

      {
        "servers": {
          "contextgate": {
            "type": "http",
            "url": "https://api.contextgate.ai/mcp"
          }
        }
      }

   2. 2

      Start the server when VS Code asks, sign in to ContextGate, and use it from Copilot Chat in Agent mode.

   The full GitHub Copilot guide

   1. 1

      Run this in a terminal:

      codex mcp add contextgate --url https://api.contextgate.ai/mcp

   2. 2

      Then sign in to ContextGate:

      codex mcp login contextgate

   The full Codex guide

   1. 1

      Run this in a terminal:

      gemini mcp add --transport http contextgate https://api.contextgate.ai/mcp

   2. 2

      In Gemini CLI, run /mcp auth contextgate and sign in to ContextGate.

   The full Gemini CLI guide

   1. 1

      Add a remote (HTTP) MCP server with this URL:

      https://api.contextgate.ai/mcp

   2. 2

      Apps that support MCP sign-in ask you to sign in to ContextGate the first time they connect.

   3. 3

      An app that can't sign in can use a workspace API key instead: create one under API keys and add ?api_key=<your key> to the URL.

   More on adding it to any MCP app
3. 3
   Ask your AI app to use Copper, then open Activity to see the call.

What you get with Copper and ContextGate

• Your AI apps can use CopperClaude, Cursor, ChatGPT and other AI apps reach Copper through the one ContextGate connection you add to them.
• You choose which tools they can useSwitch off any Copper tool you don't want used. It's hidden from your AI apps and refused if called.
• Every call is checked and recordedYour policies check each call (for example, personal data is hidden and secrets are blocked), and Activity keeps a record of it.

ContextGate sees only the tool calls that go through it, not your AI app's built-in tools or your chats.

Copper tools

Examples of what your AI apps can do in Copper. You'll see the exact list of tools after you connect it.

• create_personCreate a Copper person with contact, company, ownership, tag, and custom-field data.
• update_personUpdate selected writable fields of an existing Copper person without replacing omitted fields.
• create_companyCreate a Copper company with domain, contact, ownership, tag, and custom-field data.
• update_companyUpdate selected writable fields of an existing Copper company without replacing omitted fields.
• bulk_create_companiesAttempt 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.
• create_opportunityCreate a Copper opportunity. Only the name is required; Copper can supply the default pipeline and stage, and the primary contact is optional.
• bulk_create_opportunitiesAttempt 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.
• update_opportunityUpdate selected writable fields of an existing Copper opportunity without replacing omitted fields.
• search_opportunitiesSearch Copper opportunities by pipeline, stage, status, contact, company, value, date, ownership, or custom-field criteria and return one page.
• bulk_create_peopleAttempt 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.
• bulk_update_peopleAttempt 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.
• search_peopleSearch Copper people by contact, company, ownership, tag, date, or custom-field criteria and return one page.
• bulk_create_activitiesAttempt 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.
• bulk_create_leadsCreate 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_update_companiesAttempt 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.
• bulk_update_leadsUpdate 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.
• convert_leadConvert a Copper lead into a person and optionally a company and opportunity; the original lead is removed.
• create_activityCreate 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_custom_activity_typeCreate 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_definitionCreate a Copper custom field for selected record types.
• create_leadCreate a Copper lead with contact, ownership, source, status, tag, and custom-field data.
• create_projectCreate a Copper project, optionally related to another record and assigned to a user.
• create_related_linkConnect two existing Copper records through a Connect custom field.
• create_taskCreate a Copper task with optional assignment, related record, due/reminder times, priority, tags, and custom fields.
• delete_attached_filePermanently delete one file attached to a Copper lead, person, opportunity, company, or project.
• delete_custom_field_definitionPermanently delete one Copper custom-field definition by ID.
• delete_leadPermanently delete one Copper lead by ID.
• delete_recordDelete 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_linkDelete one Copper Connect-field connection by related-link ID.
• get_accountReturn the connected Copper account, timezone, and feature settings; use it to preflight features such as Leads.
• get_attached_file_metadataGet metadata for one file attached to a Copper lead, person, opportunity, company, or project.
• get_current_userReturn the Copper user represented by the connected account, including the user ID used for assignments.
• get_custom_activity_typeReturn one Copper custom activity type's name, icon, enabled state, interaction behavior, and ownership metadata by ID.
• get_custom_field_definitionReturn one Copper custom field's data type, record availability, filterability, options, and currency configuration by definition ID.
• get_field_layoutReturn enabled and create/edit requiredness metadata for one Copper entity type. Opportunities require pipeline_id; other entity types do not accept it.
• get_leadReturn one Copper lead's contact, ownership, source, status, tags, and custom-field data by lead ID.
• get_person_by_emailReturn the unique Copper person record matching an exact email address.
• get_recordFetch one user, person, company, opportunity, project, task, or activity by its type and ID.
• list_attached_filesList all files attached to one Copper lead, person, opportunity, company, or project.
• list_custom_activity_typesList 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_definitionsReturn Copper custom-field IDs, types, availability, and options needed to read, filter, and write custom field values.
• list_entity_activitiesList selected activity types related to one Copper lead, person, or company; company results may also include activities from related people.
• list_lead_statusesList Copper lead status IDs, names, display order, and default selection for use in lead writes and searches.
• list_pipelinesReturn all configured Copper pipelines with their stages and win probabilities for opportunity creation and updates.
• list_pipeline_stagesList 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_valuesList one bounded set of Copper IDs used in write schemas: activity types, customer sources, contact types, or opportunity loss reasons.
• list_related_linksList Connect-field connections for one Copper source record, optionally narrowed to one Connect field.
• list_related_recordsList records related to one Copper entity, optionally restricted to a target record type.
• list_tagsReturn one alphabetical page of Copper tag names for filtering or assigning records.
• list_usersReturn one page of Copper users for resolving assignee and owner IDs.
• relate_recordsCreate a direct relationship between two existing Copper records, preserving both record types and IDs.
• search_activitiesSearch Copper activities globally or for one parent record by activity type and date range, returning one page.
• search_companiesSearch Copper companies by name, domain, ownership, contact type, location, date, or custom-field criteria and return one page.
• search_leadsSearch Copper leads by identity, ownership, status, source, location, value, activity, date, tags, socials, or custom fields and return one page.
• search_projectsSearch Copper projects by name, owner, tag, status, or custom-field criteria and return one page.
• search_tasksSearch Copper tasks by name, owner, tag, related project or opportunity, status, due date, or custom-field criteria and return one page.
• unrelate_recordsRemove a direct relationship between two existing Copper records without deleting either record.
• update_activityUpdate 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.
• update_custom_activity_typeRename, 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.
• update_custom_field_definitionUpdate one Copper custom-field definition by ID.
• update_leadUpdate selected fields of a Copper lead without replacing omitted fields.
• update_projectUpdate selected writable fields of an existing Copper project without replacing omitted fields.
• update_taskUpdate selected writable fields of an existing Copper task without replacing omitted fields.
• upload_attached_fileGet 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.
• upsert_leadCreate 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.