Available

Pipedrive MCP server

Look up opportunities and record agreed sales follow-ups with Arc0’s Pipedrive tools. Searches are limited to person names, organization names, and deal titles. Connect through Arc0 to use the actions your identity is allowed to call.

CRMAPI keyMCP + RESTpipedrive.com
AUDIT LOG · PIPEDRIVEPOLICY: acme-support
09:41:07 · claude · u_8f2read
pipedrive.list_stages
List stages✓ allowed · 212ms
09:41:08 · claude · u_8f2read
pipedrive.get_deal
Get deal✓ allowed · 164ms
09:41:09 · claude · u_8f2write
pipedrive.create_deal
Create deal✓ approved · approved by user
ILLUSTRATIVE POLICY TRACE · NOT A LIVE RECEIPT

Working with Pipedrive

Before a pipeline review, find the opportunity with pipedrive.search_deals and read it through pipedrive.get_deal. Searches match deal titles rather than notes or custom fields. pipedrive.search_persons and pipedrive.search_organizations similarly search names, so they should not be presented as email or phone reverse-lookup tools.

For a stage change, pipedrive.list_pipelines and pipedrive.list_stages provide the actual IDs. Check whether a returned pipeline or stage is deleted before choosing it. pipedrive.update_deal changes supplied fields on a known deal; pipedrive.create_deal opens a new opportunity after a duplicate check. These actions do not delete deals.

pipedrive.add_activity schedules a follow-up using an account activity type key, without inviting attendees. pipedrive.add_note attaches reviewed HTML context to the deal, subject to Pipedrive’s sanitization. It adds a note rather than replacing an existing one. If a creation, activity, or note loses its response, inspect the corresponding deal in Pipedrive before repeating the request. Another attempt can leave duplicate sales records or follow-ups.

01 · USE CASES

Agent workflows for Pipedrive.

01

Find an opportunity

Use pipedrive.search_deals by title and pipedrive.get_deal to inspect its value, stage, and expected close date.

02

Choose a valid stage

Use pipedrive.list_pipelines and pipedrive.list_stages before pipedrive.update_deal moves the opportunity.

03

Open a reviewed deal

Use pipedrive.search_persons and pipedrive.search_organizations to find existing relationships before pipedrive.create_deal.

04

Record the next step

Use pipedrive.add_activity for a follow-up and pipedrive.add_note for approved context on the deal.

02 · ACTIONS

10 Pipedrive actions, graded by risk.

These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.

read

6

Look things up, subject to your permissions.

  • pipedrive.search_persons
    Search persons

    Use when finding contacts by name only. Not for email, phone, notes or custom-field reverse lookups. Returns one page; pass the cursor for more.

  • pipedrive.search_organizations
    Search organizations

    Use when finding organizations by name only. Not for address, note or custom-field lookup. Returns one page; pass the cursor for more.

  • pipedrive.search_deals
    Search deals

    Use when finding opportunities by title only. Not for known IDs; use get_deal instead. Notes and custom fields are not searched.

  • pipedrive.get_deal
    Get deal

    Use when reading a known deal ID, including value, status, expected close date and stage. Not for discovery; use search_deals.

  • pipedrive.list_pipelines
    List pipelines

    Use when choosing a pipeline before placing a deal. Not for listing its stages; use list_stages. Check is_deleted before selection; pass the cursor for more.

  • pipedrive.list_stages
    List stages

    Use when choosing a stage in a pipeline before moving a deal. Not for moving the deal; use update_deal. Check is_deleted before selection; pass the cursor for more.

write

4

Create and change things. Allow, or ask the user first.

  • pipedrive.create_deal
    Create deal

    Use when opening a new opportunity; search first to avoid duplicates. Not for changing an existing deal; use update_deal. Reconcile a lost response before retrying.

  • pipedrive.update_deal
    Update deal

    Use when changing supplied fields on a known deal. Not for creating or deleting deals. Reconcile an uncertain write before retrying.

  • pipedrive.add_activity
    Add activity

    Use when scheduling a follow-up on a deal with an account activity type key. Not for editing existing activities or inviting attendees. Reconcile uncertain writes before retrying.

  • pipedrive.add_note
    Add note

    Use when saving HTML context on a deal; Pipedrive sanitizes it. Not for replacing existing notes. Reconcile uncertain writes before retrying.

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · POLICIES AND AUDIT

Control access to Pipedrive.

Connect the intended Pipedrive account, authorize your AI client and set policies for its tools.

Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.

Configure policies and approvals

Example policy choices

  • Read actions: allow where authorized
  • pipedrive.create_deal: require approval

Arc0 MCP endpoint: https://api.arc0.ai/mcp

04 · AUTH AND DATA

How Pipedrive connects.

Connect Pipedrive using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.

The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · AI CLIENTS

Use Pipedrive with your AI client.

Sign in to Arc0 and connect Pipedrive in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.

Pipedrive with Claude

Claude Desktop + Claude Code

  1. In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
  2. For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
  3. Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Claude
Pipedrive with ChatGPT

ChatGPT on the web

  1. Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
  2. Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
  3. Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for ChatGPT
Pipedrive with OpenAI Codex

Codex app + CLI

  1. Run the registration command below. The app and CLI share ~/.codex/config.toml.
  2. Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
  3. Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for OpenAI Codex
Pipedrive with Cursor

Remote MCP setup

  1. Add Arc0 in your client’s remote MCP settings using the server URL below.
  2. Choose OAuth, sign in to Arc0, select the intended workspace and review access.
  3. Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Cursor
Pipedrive with VS Code

Remote MCP setup

  1. Add a remote HTTP MCP server named Arc0 using the URL below.
  2. Use OAuth and finish Arc0 sign-in, workspace selection and consent.
  3. Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
Pipedrive with Any MCP client

Streamable HTTP

  1. Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
  2. For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
  3. Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting

After setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.

07 · FAQ

Pipedrive and Arc0, answered.

Q01

Is there an official Pipedrive MCP server, and how does Arc0 differ?

Check Pipedrive’s docs for current official MCP availability. Arc0’s tools use Pipedrive’s API with a specific set of deal, pipeline, activity, and note operations; this page does not claim vendor MCP parity.

Q02

Which permissions does Arc0 need for Pipedrive?

Use a Pipedrive API token with the configured company subdomain. The lane requests no OAuth scopes and inherits the token user’s permissions. The current version does not offer OAuth login.

Q03

Does this work with Claude, ChatGPT, Codex and Cursor?

Yes, through Arc0 MCP when your Claude, ChatGPT, Codex, or Cursor client supports remote MCP and your account permits it. Connect the app in Arc0 and configure your client using the Arc0 setup guide. App permissions still apply.

Q04

How are credentials stored, refreshed and revoked?

Arc0 stores the API token encrypted and does not refresh it. Disconnect removes local access. Rotate the token in Pipedrive to invalidate its use elsewhere.

Q05

What happens with rate limits or errors?

Pipedrive applies API budgets and endpoint limits. Arc0 reports throttling and invalid or unauthorized operations. No deduplication guarantee is declared for these writes; inspect the deal and its activity before repeating an uncertain request.

Q06

What is the availability of these Pipedrive tools?

These tools are available. Connect the app in Arc0 and authorize your AI client. The action list describes the current implementation.

Get started

Plug Pipedrive into your agent.

Pipedrive MCP server: 10 actions including search persons, search organizations, search deals. Connect through Arc0.

Free to build · MCP + REST · Audit log on every plan

Pipedrive and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Pipedrive.