For sales teams on Pipedrive

A Pipedrive MCP server that reads the pipeline and does not move the stage

A Pipedrive MCP server reads open deals, stage, value and the person on the deal. Pipedrive ships the server on every plan and meters it with plan tokens. OAuth is the login. Pexon keeps updates and new activities out of the signed tool list, because the vendor server would otherwise allow both.

Checked 6 October 2026

Pipedrive at a glance: interfaces, access and what exists for AI

	What we found
Interfaces	Pipedrive MCP (MCP, docs public) · Deals API (REST/JSON, docs public)
Authentication	Marketplace apps use OAuth 2.0. The access token is sent as Authorization: Bearer on https://{company}.pipedrive.com. Tokens expire and are refreshed with the refresh token. The MCP product page uses the same OAuth login and does not describe an API token as the agent path.
Vendor MCP server	Vendor server, GA. Pipedrive publishes an MCP server for all plans, with OAuth and per-plan token limits. Read on 6 October 2026 from the product page. A separate tool catalogue with endpoint names was not on that page.
Vendor AI assistant	None found.
Other connectors	None found.

Pipedrive (US). Sales-led SMEs. The DACH overview of 14 May 2026 names Pipedrive, with HubSpot, as the CRM those teams pick when the job is the pipeline rather than a full suite.

Why Pipedrive is hard for agents

Where a Pipedrive connection needs engineering, not configuration

01 · Write

The vendor server can update the deal

The product page includes updates and new activities. A question about the pipeline does not need either. The signed list is read-only.

02 · Tokens

The plan meters the assistant

Pipedrive says MCP usage is subject to token limits on the plan, with extra tokens for sale. An empty answer can be a quota, and we do not hide that behind a retry.

03 · Domain

The API host is the company domain

Deal calls go to https://{company}.pipedrive.com, not to one global host. The blueprint records that domain before the first call.

04 · Custom

Custom deal fields are hashes

Pipedrive documents custom deal fields as long hashes, mapped through DealField. A question that names a label the org has not mapped is not answered by guessing the hash.

What we build

A first Pipedrive tool list, written as the manifest your IT team signs

Built on what Pipedrive documents: deals, persons, organizations, activities, pipelines and stages. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.

# pipedrive-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
  list_my_deals:   # user, status -> open deals in that user's pipeline
    backend: GET /api/v1/deals or the vendor MCP, read
    mode: read
  get_deal:        # deal -> stage, value, person, organization
    backend: Deals API
    mode: read
  list_activities: # deal -> activities on that deal
    backend: activities, read
    mode: read
  search_deals:    # title -> matching deals
    backend: GET /api/v2/deals/search
    mode: read
  draft_activity:  # deal, type, due date -> an activity a person saves
    backend: not created by the agent
    mode: propose
audit: every call logged with user, tool, arguments and the Pipedrive response

The manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.

One interface per row

How the Pipedrive interfaces differ

Pipedrive MCP

MCP. Documentation is public. Pipedrive documents a server for every plan. Connection is OAuth. The product page says an assistant can query CRM data, update records and create activities. Usage draws on plan token limits

MCP. Docs public.

Deals API

REST/JSON. Documentation is public. GET /api/v1/deals and the v2 deals search, on the company domain, with a bearer access token from the OAuth flow

REST/JSON. Docs public.

Pipedrive holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.

What the connector answers, and what it will not do

Questions it answers

Which of my open deals have had no activity in 14 days?
What stage is this deal in, and what is its value?
Which person and organization sit on this deal?

What it will not do

Update a deal, move a stage or create an activity. A person does that in Pipedrive.
Spend the plan's MCP tokens without the admin knowing the limit.
Read a deal the asking user cannot open.

When this is the wrong page

If the only need is Pipedrive's own MCP server inside ChatGPT or Claude, connect it and Pipedrive maintains it. A connector is right when updates must stay off, or when the deal has to be read next to a quote in another system.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your Pipedrive owners and checks every backend against your release and licence. Week two tests whether a person's own Pipedrive permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.

What we need from you: a named Pipedrive administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.

Sources: Pipedrive MCP server · Deals API · OAuth 2.0 · DACH CRM market overview, 14 May 2026. Read 6 October 2026. Vendor documentation changes; verify against the current release.

Connectors for 100 source systems — the dated catalogue this page belongs to
CAS genesisWorld connector — CRM, CAS Software AG
cobra CRM connector — CRM, cobra computer's brainware GmbH
HubSpot connector — CRM, HubSpot, Inc.
Claude MCP server development — how we build an MCP server for any internal system

Questions Pipedrive teams ask before the first tool call

Does Pipedrive ship its own MCP server?

Pipedrive publishes an MCP server for all plans, with OAuth and per-plan token limits. Read on 6 October 2026 from the product page. A separate tool catalogue with endpoint names was not on that page. This page describes what we add around that fact: a signed tool list and a test that the asking user only sees their own records.

Can the assistant change a deal or send a mail?

Not on the list we sign. The blueprint starts read-only. A draft the person saves in the CRM is the only write, and only after that is agreed.

Will two sellers see the same pipeline?

Only where the CRM would already show both of them the same records. Calls run as the person who asked. The blueprint tests that with two users before anything is called production.

What does a Pipedrive connector cost?

The two-week Readiness Blueprint is fixed at €4,900: the tool list, a check against your tenant, and a test that permissions survive the round trip. A production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.

Next step

Not a sales call. An architecture call.

Thirty minutes with the engineer who would build the connector, with your Pipedrive administrator in the room if you like.