Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
Pipedrive is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
100/100
trust score
18
downloads a day
local
runs on your machine
402
downloads in 30d
What it does
Complete Pipedrive CRM integration with 254 MCP tools for deals, contacts, and pipelines
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'PIPEDRIVE_API_TOKEN=${PIPEDRIVE_API_TOKEN}' --env 'PIPEDRIVE_COMPANY_DOMAIN=${PIPEDRIVE_COMPANY_DOMAIN}' --transport stdio nubiia-dev-pipedrive-mcp '--' npx -y @nubiia/mcp-pipedrive
# 2 — ask your agent for something these tools do
# deals_list, deals_list_all_auto, deals_list_archived and 4 more
It needs PIPEDRIVE_API_TOKEN, PIPEDRIVE_COMPANY_DOMAIN: this reads them from your environment, so export them first.
Pipedrive costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NDAll 5 servers
nubiia-dev5 servers
3 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Pipedrive as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads PIPEDRIVE_API_TOKEN (Your Pipedrive API token (found in Settings → Personal Preferences → API)), PIPEDRIVE_COMPANY_DOMAIN (Your Pipedrive company domain (e.g., 'mycompany' if your URL is mycompany.pipedrive.com)) from your environment each time it starts the server, so the value stays out of its config: export them in your shell profile (macOS, Linux), or run setx PIPEDRIVE_API_TOKEN …, setx PIPEDRIVE_COMPANY_DOMAIN … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'PIPEDRIVE_API_TOKEN=${PIPEDRIVE_API_TOKEN}' --env 'PIPEDRIVE_COMPANY_DOMAIN=${PIPEDRIVE_COMPANY_DOMAIN}' --transport stdio nubiia-dev-pipedrive-mcp '--' npx -y @nubiia/mcp-pipedriveReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: PIPEDRIVE_API_TOKEN — Your Pipedrive API token (found in Settings → Personal Preferences → API); PIPEDRIVE_COMPANY_DOMAIN — Your Pipedrive company domain (e.g., 'mycompany' if your URL is mycompany.pipedrive.com). You set them in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List deals with cursor-based pagination and filtering options. Backed by Pipedrive API v2 (GET /api/v2/deals). Returns a page of deals. Use filters to narrow results by status, stage, owner, person, organization, or pipeline. Workflow tips: - Use status filter to get only 'open', 'won', 'lost',…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by deal status. 'all_not_deleted' is v1-only and is translated to 'no status filter' since v2 has no such value. |
| stage_id | number | no | Filter by stage ID |
| user_id | number | no | Filter by user (owner) ID — sent as owner_id to v2. If owned_by_you=1 is also set, owned_by_you takes precedence and this value is ignored. |
| person_id | number | no | Filter by person ID |
| org_id | number | no | Filter by organization ID |
| pipeline_id | number | no | Filter by pipeline ID |
| filter_id | number | no | ID of the filter to use |
| sort | string | no | Field to sort by. v2 only accepts a small enum — confirmed working: id, add_time, update_time. |
| sort_by | string | no | Sort direction |
| owned_by_you | number | no | Filter deals owned by the authorized user (1 = yes, 0 = no). Takes precedence over user_id when both are provided. |
| add_time_from | string | no | Filter deals created on or after this date (YYYY-MM-DD). Applied client-side. |
| add_time_until | string | no | Filter deals created on or before this date (YYYY-MM-DD). Applied client-side. |
| cursor | string | no | Opaque cursor from a previous response (additional_data.next_cursor) to fetch the next page. |
| start | number | no | DEPRECATED — ignored. v2 uses cursor-based pagination; see "cursor". |
| limit | number | no | Number of items to return |
Automatically fetch ALL deals with pagination handling. Backed by Pipedrive API v2 (GET /api/v2/deals), paginated via cursor. This tool automatically handles cursor pagination and fetches all deals matching the filters. Unlike deals/list, this returns ALL results in a single response. WARNING:…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by deal status. 'all_not_deleted' is v1-only and is translated to 'no status filter'. |
| stage_id | number | no | Filter by stage ID |
| user_id | number | no | Filter by user (owner) ID — sent as owner_id to v2. If owned_by_you=1 is also set, owned_by_you takes precedence and this value is ignored. |
| person_id | number | no | Filter by person ID |
| org_id | number | no | Filter by organization ID |
| pipeline_id | number | no | Filter by pipeline ID |
| filter_id | number | no | ID of the filter to use |
| sort | string | no | Field to sort by. v2 only accepts a small enum — confirmed: id, add_time, update_time. |
| sort_by | string | no | Sort direction |
| owned_by_you | number | no | Filter deals owned by the authorized user. Takes precedence over user_id when both are provided. |
| add_time_from | string | no | Filter deals created on or after this date (YYYY-MM-DD). Applied client-side. |
| add_time_until | string | no | Filter deals created on or before this date (YYYY-MM-DD). Applied client-side. |
| max_items | number | no | Maximum number of items to return |
List archived deals with pagination and filtering options. Returns a paginated list of archived deals. Archived deals are deals that have been removed from active pipelines. Workflow tips: - Use same filters as deals/list (status, stage_id, user_id, person_id, org_id, etc.) - Filter by user_id…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by deal status |
| stage_id | number | no | Filter by stage ID |
| user_id | number | no | Filter by user (owner) ID |
| person_id | number | no | Filter by person ID |
| org_id | number | no | Filter by organization ID |
| pipeline_id | number | no | Filter by pipeline ID |
| filter_id | number | no | ID of the filter to use |
| sort | string | no | Field to sort by (e.g., title, value, stage_id) |
| owned_by_you | number | no | Filter deals owned by the authorized user (1 = yes, 0 = no) |
| start | number | no | Pagination start |
| limit | number | no | Number of items to return |
Create a new deal in Pipedrive. Creates a new deal with the specified information. Only title is required. Custom fields: - Pass display names: { "custom_fields": { "Industria": "Tech", "Budget": 5000 } } - Or hash keys directly: { "custom_fields": { "abc123...": "raw value" } } - For enum/set…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | Deal title (required) |
| value | number | no | Deal value |
| currency | string | no | 3-letter currency code (e.g., USD, EUR) |
| user_id | number | no | ID of the user who will own this deal |
| person_id | number | no | ID of the person this deal is associated with |
| org_id | number | no | ID of the organization this deal is associated with |
| pipeline_id | number | no | ID of the pipeline this deal will be in |
| stage_id | number | no | ID of the stage this deal will be in |
| status | string | no | Deal status (default: open) |
| expected_close_date | string | no | Expected close date in YYYY-MM-DD format |
| probability | number | no | Deal success probability (0-100) |
| lost_reason | string | no | Reason why the deal was lost |
| visible_to | string | no | Visibility: 1=Owner, 3=Owner's group, 5=Owner's group and sub-groups, 7=Entire company |
| add_time | string | no | Creation time in ISO 8601 format |
| custom_fields | object | no | Custom field values keyed by display name or hash. See description for format. |
Get detailed information about a specific deal by ID. Retrieves complete information about a single deal, including all custom fields. Workflow tips: - Use deals/search or deals/list to find deal IDs first - Response includes person, organization, pipeline, and stage information - Cached for 5…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | number | yes | ID of the deal to retrieve |
Update an existing deal. Updates one or more fields of an existing deal. Only provide fields you want to change. Custom fields: - Pass display names: { "id": 123, "custom_fields": { "Industria": "Tech", "Budget": 5000 } } - Or hash keys directly: { "id": 123, "custom_fields": { "abc123...": "raw…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | number | yes | ID of the deal to update |
| title | string | no | Deal title |
| value | number | no | Deal value |
| currency | string | no | 3-letter currency code |
| user_id | number | no | ID of the user who will own this deal |
| person_id | number | no | ID of the person |
| org_id | number | no | ID of the organization |
| pipeline_id | number | no | ID of the pipeline |
| stage_id | number | no | ID of the stage |
| status | string | no | Deal status |
| expected_close_date | string | no | Expected close date in YYYY-MM-DD format |
| probability | number | no | Deal success probability (0-100) |
| lost_reason | string | no | Reason why the deal was lost |
| visible_to | string | no | Visibility setting |
| custom_fields | object | no | Custom field values keyed by display name or hash. See description for format. |
Move a deal to a different stage in the pipeline. Convenience tool to move a deal to another stage. Use this instead of deals/update when only changing stages. Workflow tips: - Use pipelines/list to get available stages - Moving stages may trigger automations in Pipedrive - Stage must be in the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | number | yes | ID of the deal to move |
| stage_id | number | yes | ID of the stage to move the deal to |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Pipedrive or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 100 / 100
Release 2.7.1 · scanned 28 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest7f4a0b2f7833114b6010502db858b5ed654743573b9b8b04c821b3ec12cefa48
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
dist/tools/stages/create.d.ts (1 KB) was not read: over the file-count budget.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest7f4a0b2f7833114b
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 2.7.1. Pin a release below and the command asks for exactly that one.
2.7.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Pipedrive can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.