Pipedrive CRM
MCPB · PIPEDRIVE-MCP-SERVER-2.5.0.MCPB · 2 COMPONENTS · SCANNED AUG 4
MCP server for Pipedrive CRM. 155 tools for deals, persons, organizations, activities, and more.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security13
- Malware scan not yet available for this package.Unverified
- CVE data not yet available for this package.Unverified
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 14161 tokens (~115/item across 123 items; 123 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
mcpb · pipedrive-mcp-server-2.5.0.mcpb
Download bundleEvery change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +18
- Security disclosure: fail → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Stability: unverified → 0.23 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 1 Aug 26 −5
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- 31 Jul 26 +17
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −21
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 37
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Aug 2026 · Analysed mcpb/https://github.com/ckalima/pipedrive-mcp-server/releases/download/v2.5.0/[email protected]
Provenance none
Ecosystem: mcpb · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
pipedrive_update_deal_field ~183
Update a deal custom field by field_code. field_type and field_code cannot be changed.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string|null | — | Field description (null to clear) |
| field_code | string | yes | The field_code (40-char hash for custom fields) from the field create/list response. NOT the human field name. |
| field_name | string | — | New field name (1-255 chars) |
| important_fields | object | — | Important-field highlighting: enabled, stage_ids (always references DEAL stages, even on person/org fields). |
| required_fields | object | — | Required-field config: enabled, stage_ids (deal stages), statuses (per-pipeline won/lost map). |
| ui_visibility | object | — | UI visibility: add_visible_flag, details_visible_flag, projects_detail_visible_flag, show_in_pipelines{show_in_all, pipeline_ids}. |
No output schema declared.
No examples provided.
pipedrive_update_deal_field_options ~98
Bulk-update option labels of a deal enum/set field. Atomic: the whole request fails if any option ID does not exist.
| Name | Type | Req | Description |
|---|---|---|---|
| field_code | string | yes | The field_code (40-char hash for custom fields) from the field create/list response. NOT the human field name. |
| options | array | yes | Options to update (at least one). Atomic: the whole request fails if any option ID does not exist. |
No output schema declared.
No examples provided.
pipedrive_update_deal_installment ~91
Update an installment on a deal. Growth+ plan required; all body fields optional.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | — | Installment amount, must be positive |
| billing_date | string | — | Billing date in YYYY-MM-DD format |
| description | string | — | Installment description |
| id | number | yes | The deal ID |
| installment_id | number | yes | The installment ID |
No output schema declared.
No examples provided.
pipedrive_update_deal_product ~247
Update a line-item product attached to a deal. All body fields optional.
| Name | Type | Req | Description |
|---|---|---|---|
| billing_frequency | string | — | Billing frequency for recurring products |
| billing_frequency_cycles | number|null | — | Number of billing cycles (null = unlimited) |
| billing_start_date | string|null | — | Billing start date (YYYY-MM-DD, null to clear) |
| comments | string | — | Free-text comments for this line item |
| discount | number | — | Discount applied to the line item |
| discount_type | string | — | Whether discount is a percentage or fixed amount |
| id | number | yes | The deal ID |
| is_enabled | boolean | — | Whether the product is enabled on the deal |
| item_price | number | — | Price of one unit |
| product_attachment_id | number | yes | The product-attachment ID (the line item's own ID on the deal) |
| product_id | number | — | The product ID to attach |
| product_variation_id | number|null | — | Product variation ID (null to clear) |
| quantity | number | — | Quantity of the product |
| tax | number | — | Tax percentage |
| tax_method | string | — | How tax is applied |
No output schema declared.
No examples provided.
pipedrive_update_lead ~164
Update an existing lead in Pipedrive.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_close_date | string | — | New expected close date (YYYY-MM-DD) |
| id | string | yes | Lead UUID to update |
| is_archived | boolean | — | Archive or unarchive the lead |
| label_ids | array | — | New lead label UUIDs |
| organization_id | number | — | New linked organization ID |
| owner_id | number | — | New owner user ID |
| person_id | number | — | New linked person ID |
| title | string | — | New lead title |
| value | object | — | New monetary value |
| visible_to | number | — | New visibility: 1=Owner, 3=Group, 5=Subgroups, 7=Company |
No output schema declared.
No examples provided.
pipedrive_update_note ~139
Update an existing note in Pipedrive.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | — | New note content (HTML supported) |
| deal_id | number | — | New linked deal ID |
| id | number | yes | Note ID to update |
| lead_id | string | — | New linked lead ID (UUID format) |
| org_id | number | — | New linked organization ID |
| person_id | number | — | New linked person ID |
| pinned_to_deal_flag | boolean | — | Pin note to deal |
| pinned_to_organization_flag | boolean | — | Pin note to organization |
| pinned_to_person_flag | boolean | — | Pin note to person |
No output schema declared.
No examples provided.
pipedrive_update_organization ~140
Update an existing organization in Pipedrive.
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | — | New organization address as a structured object (v2). Provide 'value' for the full address. |
| custom_fields | object | — | Custom field values as object with field keys |
| id | number | yes | Organization ID to update |
| label_ids | array | — | Label IDs to set on organization |
| name | string | — | New name |
| owner_id | number | — | New owner user ID |
| visible_to | number | — | New visibility: 1=Owner, 3=Group, 5=Subgroups, 7=Company |
No output schema declared.
No examples provided.
pipedrive_update_organization_field ~165
Update an organization custom field by field_code. field_type and field_code cannot be changed.
| Name | Type | Req | Description |
|---|---|---|---|
| field_code | string | yes | The field_code (40-char hash for custom fields) from the field create/list response. NOT the human field name. |
| field_name | string | — | New field name (1-255 chars) |
| important_fields | object | — | Important-field highlighting: enabled, stage_ids (always references DEAL stages, even on person/org fields). |
| required_fields | object | — | Required-field config: enabled (person/org fields support only this flag). |
| ui_visibility | object | — | UI visibility: add_visible_flag, details_visible_flag, show_in_add_deal_dialog{show, order}, show_in_add_person_dialog{show, order}. |
No output schema declared.
No examples provided.
pipedrive_update_organization_field_options ~98
Bulk-update option labels of an organization enum/set field. Atomic: the whole request fails if any option ID does not exist.
| Name | Type | Req | Description |
|---|---|---|---|
| field_code | string | yes | The field_code (40-char hash for custom fields) from the field create/list response. NOT the human field name. |
| options | array | yes | Options to update (at least one). Atomic: the whole request fails if any option ID does not exist. |
No output schema declared.
No examples provided.
pipedrive_update_person ~163
Update an existing person in Pipedrive.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_fields | object | — | Custom field values as object with field keys |
| emails | array | — | New email addresses (array of objects) |
| id | number | yes | Person ID to update |
| label_ids | array | — | Label IDs to set on person |
| marketing_status | string | — | New marketing status |
| name | string | — | New name |
| org_id | number | — | New organization ID |
| owner_id | number | — | New owner user ID |
| phones | array | — | New phone numbers (array of objects) |
| visible_to | number | — | New visibility: 1=Owner, 3=Group, 5=Subgroups, 7=Company |
No output schema declared.
No examples provided.
pipedrive_update_person_field ~154
Update a person custom field by field_code. field_type and field_code cannot be changed.
| Name | Type | Req | Description |
|---|---|---|---|
| field_code | string | yes | The field_code (40-char hash for custom fields) from the field create/list response. NOT the human field name. |
| field_name | string | — | New field name (1-255 chars) |
| important_fields | object | — | Important-field highlighting: enabled, stage_ids (always references DEAL stages, even on person/org fields). |
| required_fields | object | — | Required-field config: enabled (person/org fields support only this flag). |
| ui_visibility | object | — | UI visibility: add_visible_flag, details_visible_flag, show_in_add_deal_dialog{show, order}. |
No output schema declared.
No examples provided.
pipedrive_update_person_field_options ~97
Bulk-update option labels of a person enum/set field. Atomic: the whole request fails if any option ID does not exist.
| Name | Type | Req | Description |
|---|---|---|---|
| field_code | string | yes | The field_code (40-char hash for custom fields) from the field create/list response. NOT the human field name. |
| options | array | yes | Options to update (at least one). Atomic: the whole request fails if any option ID does not exist. |
No output schema declared.
No examples provided.
pipedrive_update_phase ~110
Update an existing project phase. Only id is required; all other fields are optional. Set board_id to move this phase to a different board. (Projects add-on; Projects API in public beta.)
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | number | — | ID of the board (set to move this phase to a different board) |
| id | number | yes | The phase ID to update |
| name | string | — | Phase name |
| order_nr | number | — | Phase order number (integer >= 1) |
No output schema declared.
No examples provided.
pipedrive_update_pipeline ~72
Update an existing pipeline. Provide the pipeline id and any fields to change.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | The ID of the pipeline to update |
| is_deal_probability_enabled | boolean | — | Whether deal probability is enabled for this pipeline |
| name | string | — | The new name of the pipeline |
No output schema declared.
No examples provided.
pipedrive_update_product ~214
Update an existing product in Pipedrive.
| Name | Type | Req | Description |
|---|---|---|---|
| billing_frequency | string | — | Billing frequency |
| billing_frequency_cycles | number|null | — | Number of billing cycles (max 208, null = unlimited) |
| category | number | — | New product category ID |
| code | string | — | New product code |
| custom_fields | object | — | Custom field values as object with field keys |
| description | string | — | New product description |
| id | number | yes | Product ID to update |
| is_linkable | boolean | — | Whether the product can be linked to deals |
| name | string | — | New product name |
| owner_id | number | — | New owner user ID |
| prices | array | — | Array of price objects per currency |
| tax | number | — | New tax percentage |
| unit | string | — | New unit of measurement |
| visible_to | number | — | New visibility: 1=Owner, 3=Group, 5=Subgroups, 7=Company |
No output schema declared.
No examples provided.
pipedrive_update_product_field ~115
Update a product custom field by field_code. Only field_name and ui_visibility can be changed (product fields have no description/important_fields/required_fields).
| Name | Type | Req | Description |
|---|---|---|---|
| field_code | string | yes | The field_code (40-char hash for custom fields) from the field create/list response. NOT the human field name. |
| field_name | string | — | New field name (1-255 chars) |
| ui_visibility | object | — | UI visibility (product fields use a simpler model): add_visible_flag, details_visible_flag. |
No output schema declared.
No examples provided.
pipedrive_update_product_field_options ~97
Bulk-update option labels of a product enum/set field. Atomic: the whole request fails if any option ID does not exist.
| Name | Type | Req | Description |
|---|---|---|---|
| field_code | string | yes | The field_code (40-char hash for custom fields) from the field create/list response. NOT the human field name. |
| options | array | yes | Options to update (at least one). Atomic: the whole request fails if any option ID does not exist. |
No output schema declared.
No examples provided.
pipedrive_update_product_image ~217
Update (replace) the image of a product. Provide the image via EITHER file_path OR base64_data (exactly one required). Supports png, jpeg, gif, and webp. Note: file_path is read by the SERVER process via the filesystem and is disabled by default; the operator must set PIPEDRIVE_IMAGE_BASE_DIR and the path must resolve within it; otherwise use base64_data, which is transport-safe.
| Name | Type | Req | Description |
|---|---|---|---|
| base64_data | string | — | Base64-encoded image bytes (transport-safe). Mutually exclusive with file_path. |
| file_name | string | yes | Original filename including extension (e.g. product.png) |
| file_path | string | — | Path the server reads via fs.readFile, confined to PIPEDRIVE_IMAGE_BASE_DIR (filesystem reads are disabled unless that variable is set). Mutually exclusive with base64_data. |
| id | number | yes | The product ID |
| mime_type | string | — | MIME type. Inferred from file_name if omitted. |
No output schema declared.
No examples provided.
pipedrive_update_product_variation ~71
Update an existing product variation.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | The product ID |
| name | string | — | Product variation name (max 255 chars) |
| prices | array | — | Array of price objects per currency |
| product_variation_id | number | yes | The product variation ID |
No output schema declared.
No examples provided.
pipedrive_update_project ~209
Update an existing project in Pipedrive. (Requires the Projects add-on; Projects API is in public beta.)
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | number | — | New board ID the project belongs to |
| deal_ids | array | — | New deal IDs linked to the project |
| description | string | — | New project description |
| end_date | string | — | New project end date (YYYY-MM-DD) |
| id | number | yes | Project ID to update |
| label_ids | array | — | New label IDs to attach to the project |
| org_ids | array | — | New organization IDs linked to the project |
| owner_id | number | — | New owner user ID |
| person_ids | array | — | New person IDs linked to the project |
| phase_id | number | — | New phase ID within the board |
| start_date | string | — | New project start date (YYYY-MM-DD) |
| status | string | — | New project status |
| title | string | — | New project title |
No output schema declared.
No examples provided.
pipedrive_update_stage ~157
Update an existing stage. Provide the stage id and any fields to change. Set pipeline_id to move the stage to another pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| days_to_rotten | number|null | — | Days until a deal not updated in this stage becomes rotten (applies only when is_deal_rot_enabled is set; null to clear) |
| deal_probability | number | — | The success probability percentage of deals in this stage (0-100) |
| id | number | yes | The ID of the stage to update |
| is_deal_rot_enabled | boolean | — | Whether deals in this stage can become rotten |
| name | string | — | The new name of the stage |
| pipeline_id | number | — | Move the stage to this pipeline ID |
No output schema declared.
No examples provided.
pipedrive_update_task ~280
Update an existing task. Only id is required; all other fields are optional. Use boolean is_done/is_milestone (same field names as the GET response); a milestone task must have a due_date. (Projects add-on; Projects API in public beta.)
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_id | number|null | — | Assignee user ID (null to unassign) |
| assignee_ids | array | — | Array of assignee user IDs (max 10) |
| description | string|null | — | Task description (null to clear) |
| due_date | string|null | — | Task due date (YYYY-MM-DD, null to clear) |
| id | number | yes | The task ID to update |
| is_done | boolean | — | Mark as done (true/false) |
| is_milestone | boolean | — | Mark as milestone (true/false); a milestone task must have a due_date |
| parent_task_id | number|null | — | ID of the parent task (null to make root-level) |
| priority | number|null | — | Task priority (integer >= 0, or null to unset) |
| project_id | number | — | ID of the project this task belongs to |
| start_date | string|null | — | Task start date (YYYY-MM-DD, null to clear) |
| title | string | — | Task title (1-255 chars) |
No output schema declared.
No examples provided.
pipedrive_upload_product_image ~214
Upload an image for a product. Provide the image via EITHER file_path OR base64_data (exactly one required). Supports png, jpeg, gif, and webp. Note: file_path is read by the SERVER process via the filesystem and is disabled by default; the operator must set PIPEDRIVE_IMAGE_BASE_DIR and the path must resolve within it; otherwise use base64_data, which is transport-safe.
| Name | Type | Req | Description |
|---|---|---|---|
| base64_data | string | — | Base64-encoded image bytes (transport-safe). Mutually exclusive with file_path. |
| file_name | string | yes | Original filename including extension (e.g. product.png) |
| file_path | string | — | Path the server reads via fs.readFile, confined to PIPEDRIVE_IMAGE_BASE_DIR (filesystem reads are disabled unless that variable is set). Mutually exclusive with base64_data. |
| id | number | yes | The product ID |
| mime_type | string | — | MIME type. Inferred from file_name if omitted. |
No output schema declared.
No examples provided.