Pipedrive CRM MCP server

Read from the package source without running it. The installed server may list more.

• pipedrive_add_deal_discount

  Add an additional discount to a deal.

• pipedrive_add_deal_follower

  Add a follower to a deal.

• pipedrive_add_deal_installment

  Add an installment (payment schedule entry) to a deal. Growth+ plan required; the deal must have at least one one-time product and no recurring products.

• pipedrive_add_deal_product

  Attach a single product as a line item to a deal.

• pipedrive_add_organization_follower

  Add a follower to an organization.

• pipedrive_bulk_add_deal_products

  Bulk-add up to 100 line-item products to a deal in one request.

• pipedrive_convert_deal_to_lead

  Convert a deal to a lead (async job). DESTRUCTIVE: a successful conversion marks the source deal as deleted. Returns a conversion_id; the conversion runs asynchronously, so you MUST poll pipedrive_get_deal_conversion_status with the conversion_id until a terminal status. Requires PIPEDRIVE_MODE=full (back-compat: PIPEDRIVE_ENABLE_DESTRUCTIVE=true).

• pipedrive_convert_lead_to_deal

  Convert a lead into a deal (Pipedrive v2). DESTRUCTIVE: a successful conversion marks the source lead as deleted. The conversion runs asynchronously; this tool polls until it completes (typically under 5s) and returns the new deal ID. If it is still running after ~30s, it returns the conversion_id and status for manual follow-up. Requires PIPEDRIVE_MODE=full (back-compat: PIPEDRIVE_ENABLE_DESTRUCT

• pipedrive_create_activitywrite action

  Create a new activity in Pipedrive. Subject and type are required.

• pipedrive_create_boardwrite action

  Create a new project board. name is required. (Projects add-on; Projects API in public beta.)

• pipedrive_create_dealwrite action

  Create a new deal in Pipedrive. Only title is required; all other fields are optional.

• pipedrive_create_deal_fieldwrite action

  Create a deal custom field. field_name and field_type are required. For enum/set types, options is required. The response data.field_code is the 40-char hash you must keep to update or delete the field later.

• pipedrive_create_leadwrite action

  Create a new lead in Pipedrive. Title is required; link to at least one of person_id or organization_id.

• pipedrive_create_notewrite action

  Create a new note in Pipedrive. Content is required. Link to a deal, person, organization, or lead.

• pipedrive_create_organizationwrite action

  Create a new organization in Pipedrive. Only name is required.

• pipedrive_create_organization_fieldwrite action

  Create an organization custom field. field_name and field_type are required. For enum/set types, options is required. The response data.field_code is the 40-char hash to keep for later updates.

• pipedrive_create_personwrite action

  Create a new person (contact) in Pipedrive. Only name is required.

• pipedrive_create_person_fieldwrite action

  Create a person custom field. field_name and field_type are required. For enum/set types, options is required. The response data.field_code is the 40-char hash to keep for later updates.

• pipedrive_create_phasewrite action

  Create a new project phase. name and board_id are required. (Projects add-on; Projects API in public beta.)

• pipedrive_create_product_fieldwrite action

  Create a product custom field. field_name and field_type are required. For enum/set types, options is required. Product fields use a simpler model: no description, important_fields, or required_fields. The response data.field_code is the 40-char hash to keep for later updates.

• pipedrive_delete_activitywrite action

  Delete an activity.

• pipedrive_delete_boardwrite action

  Delete a project board. Requires PIPEDRIVE_MODE=full (back-compat: PIPEDRIVE_ENABLE_DESTRUCTIVE=true). (Projects add-on; Projects API in public beta.)

• pipedrive_delete_dealwrite action

  Delete a deal. The deal will be marked as deleted and permanently removed after 30 days.

• pipedrive_delete_deal_discountwrite action

  Delete an additional discount from a deal.

• pipedrive_delete_deal_fieldwrite action

  Delete a deal custom field by field_code. Requires PIPEDRIVE_MODE=full (back-compat: PIPEDRIVE_ENABLE_DESTRUCTIVE=true).

• pipedrive_delete_deal_field_optionswrite action

  Bulk-delete options of a deal enum/set field. Atomic: fails if any ID does not exist. Requires PIPEDRIVE_MODE=full (back-compat: PIPEDRIVE_ENABLE_DESTRUCTIVE=true).

• pipedrive_delete_deal_followerwrite action

  Remove a follower from a deal.

• pipedrive_delete_deal_installmentwrite action

  Delete an installment from a deal. Growth+ plan required.

• pipedrive_delete_deal_productwrite action

  Remove a line-item product from a deal.

• pipedrive_delete_leadwrite action

  Delete a lead. Requires PIPEDRIVE_MODE=full (back-compat: PIPEDRIVE_ENABLE_DESTRUCTIVE=true).

• pipedrive_delete_notewrite action

  Delete a note.

• pipedrive_delete_organizationwrite action

  Delete an organization. The organization will be marked as deleted and permanently removed after 30 days.

• pipedrive_delete_organization_fieldwrite action

  Delete an organization custom field by field_code. Requires PIPEDRIVE_MODE=full (back-compat: PIPEDRIVE_ENABLE_DESTRUCTIVE=true).

• pipedrive_delete_organization_field_optionswrite action

  Bulk-delete options of an organization enum/set field. Atomic: fails if any ID does not exist. Requires PIPEDRIVE_MODE=full (back-compat: PIPEDRIVE_ENABLE_DESTRUCTIVE=true).

• pipedrive_delete_organization_followerwrite action

  Remove a follower from an organization.

• pipedrive_delete_person_fieldwrite action

  Delete a person custom field by field_code. Requires PIPEDRIVE_MODE=full (back-compat: PIPEDRIVE_ENABLE_DESTRUCTIVE=true).

• pipedrive_delete_person_field_optionswrite action

  Bulk-delete options of a person enum/set field. Atomic: fails if any ID does not exist. Requires PIPEDRIVE_MODE=full (back-compat: PIPEDRIVE_ENABLE_DESTRUCTIVE=true).

• pipedrive_delete_phasewrite action

  Delete a project phase. Requires PIPEDRIVE_MODE=full (back-compat: PIPEDRIVE_ENABLE_DESTRUCTIVE=true). (Projects add-on; Projects API in public beta.)

• pipedrive_delete_product_fieldwrite action

  Delete a product custom field by field_code. Requires PIPEDRIVE_MODE=full (back-compat: PIPEDRIVE_ENABLE_DESTRUCTIVE=true).

• pipedrive_delete_product_field_optionswrite action

  Bulk-delete options of a product enum/set field. Atomic: fails if any ID does not exist. Requires PIPEDRIVE_MODE=full (back-compat: PIPEDRIVE_ENABLE_DESTRUCTIVE=true).

• pipedrive_get_activity

  Get detailed information about a specific activity by ID.

• pipedrive_get_board

  Get detailed information about a specific project board by ID. (Projects add-on; Projects API in public beta.)

• pipedrive_get_deal

  Get detailed information about a specific deal by ID, including all standard and custom fields.

• pipedrive_get_deal_conversion_status

  Get the status of a deal-to-lead conversion job. Status contract: 'completed' (terminal, carries lead_id), 'failed'/'rejected' (terminal, stop polling, no lead produced), 'not_started'/'running' (in-progress, re-poll). Only 'completed' carries lead_id, and conversion status is purged after a few days, so a 404 returned after a prior valid status means the status was purged (terminal stop-polling s

• pipedrive_get_deal_emails

  Get email messages linked to a deal (company-wide, all users' emails). Returns metadata for emails from any user's mailbox that are linked to this deal. Note: To get full message body, use pipedrive_get_mail_message, but only for emails in YOUR mailbox.

• pipedrive_get_deal_followers_changelog

  Get the followers changelog for a deal.

• pipedrive_get_field

  Get details of a specific field by its key. Useful for looking up what a 40-character hash field key means.

• pipedrive_get_lead

  Get detailed information about a specific lead by UUID.

• pipedrive_get_lead_conversion_status

  Get the status of an async lead-to-deal conversion by conversion ID (Pipedrive v2 GET /leads/{id}/convert/status/{conversion_id}).

• pipedrive_get_mail_message

  Get full email message with body. Access depends on visibility settings - messages linked to deals/persons you can access should work, even if sent by other users.

• pipedrive_get_mail_thread

  Get a mail thread with messages. Access depends on visibility settings - threads visible within deals/persons you can access should work. Returns 404 if the thread isn't accessible to you.

• pipedrive_get_note

  Get detailed information about a specific note by ID.

• pipedrive_get_organization

  Get detailed information about a specific organization by ID.

• pipedrive_get_organization_followers_changelog

  Get the followers changelog for an organization.

• pipedrive_get_person

  Get detailed information about a specific person by ID.

• pipedrive_get_person_emails

  Get email messages linked to a person (company-wide, all users' emails). Returns metadata for emails from any user's mailbox that are linked to this person. Note: To get full message body, use pipedrive_get_mail_message, but only for emails in YOUR mailbox.

• pipedrive_get_phase

  Get detailed information about a specific project phase by ID. (Projects add-on; Projects API in public beta.)

• pipedrive_list_activities

  List activities from Pipedrive with optional filtering by owner, deal, person, organization, type, or completion status.

• pipedrive_list_archived_deals

  List archived deals with the same filtering as the active deals list (owner, person, organization, pipeline, stage, status). Returns paginated results.

• pipedrive_list_archived_leads

  List archived leads from Pipedrive with optional filtering by owner, person, or organization.

• pipedrive_list_boards

  List all project boards. Returns the complete list (no pagination — the boards endpoint returns all records at once). (Projects add-on; Projects API in public beta.)

• pipedrive_list_deal_discounts

  List all additional discounts applied to a deal.

• pipedrive_list_deal_fields

  List all deal field definitions, including custom fields. Essential for understanding deal data structure.

• pipedrive_list_deal_followers

  List all followers for a deal.

• pipedrive_list_deal_installments

  List installments across one or more deals. Requires deal_ids. Growth+ plan required.

• pipedrive_list_deal_products

  List line-item products attached to a deal. Returns paginated results.

• pipedrive_list_deals

  List deals from Pipedrive with optional filtering by owner, person, organization, pipeline, stage, or status. Returns paginated results.

• pipedrive_list_leads

  List active (non-archived) leads from Pipedrive with optional filtering by owner, person, or organization.

• pipedrive_list_mail_threads

  List mail threads from YOUR mailbox only (authenticated user). Other users' threads are not accessible. Use folder parameter to filter by inbox, drafts, sent, or archive.

• pipedrive_list_notes

  List notes from Pipedrive with optional filtering by deal, person, organization, or lead.

• pipedrive_list_organization_fields

  List all organization field definitions, including custom fields. Use this to map 40-character field keys to human-readable names.

• pipedrive_list_organization_followers

  List all followers for an organization.

• pipedrive_list_organizations

  List organizations from Pipedrive with optional filtering by owner or first letter of name.

• pipedrive_list_person_fields

  List all person field definitions, including custom fields. Use to understand contact data structure.

• pipedrive_list_persons

  List persons (contacts) from Pipedrive with optional filtering by owner, organization, or first letter of name.

• pipedrive_list_phases

  List all phases for a project board. board_id is required. Returns the complete list (no pagination — the phases endpoint returns all records for a board at once). (Projects add-on; Projects API in public beta.)

• pipedrive_list_product_fields

  List all product field definitions, including custom fields.

• pipedrive_list_project_fields

  List all project field definitions, including custom fields. (Projects add-on; Projects API in public beta.)

• pipedrive_search_deals

  Search for deals by text in title. Supports fuzzy matching by default.

• pipedrive_search_leads

  Search for leads in Pipedrive by title or associated contacts.

• pipedrive_search_organizations

  Search for organizations by name or address.

• pipedrive_update_activitywrite action

  Update an existing activity in Pipedrive. Use this to mark activities as done.

• pipedrive_update_boardwrite action

  Update an existing project board. Only id is required; all other fields are optional. (Projects add-on; Projects API in public beta.)

• pipedrive_update_dealwrite action

  Update an existing deal in Pipedrive. Specify the deal ID and any fields to update.

• pipedrive_update_deal_discountwrite action

  Update an additional discount on a deal. All fields except IDs are optional.

• pipedrive_update_deal_fieldwrite action

  Update a deal custom field by field_code. field_type and field_code cannot be changed.

• pipedrive_update_deal_field_optionswrite action

  Bulk-update option labels of a deal enum/set field. Atomic: the whole request fails if any option ID does not exist.

• pipedrive_update_deal_installmentwrite action

  Update an installment on a deal. Growth+ plan required; all body fields optional.

• pipedrive_update_deal_productwrite action

  Update a line-item product attached to a deal. All body fields optional.

• pipedrive_update_leadwrite action

  Update an existing lead in Pipedrive.

• pipedrive_update_notewrite action

  Update an existing note in Pipedrive.

• pipedrive_update_organizationwrite action

  Update an existing organization in Pipedrive.

• pipedrive_update_organization_fieldwrite action

  Update an organization custom field by field_code. field_type and field_code cannot be changed.

• pipedrive_update_organization_field_optionswrite action

  Bulk-update option labels of an organization enum/set field. Atomic: the whole request fails if any option ID does not exist.

• pipedrive_update_personwrite action

  Update an existing person in Pipedrive.

• pipedrive_update_person_fieldwrite action

  Update a person custom field by field_code. field_type and field_code cannot be changed.

• pipedrive_update_person_field_optionswrite action

  Bulk-update option labels of a person enum/set field. Atomic: the whole request fails if any option ID does not exist.

• pipedrive_update_phasewrite action

  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.)

• pipedrive_update_product_fieldwrite action

  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).

• pipedrive_update_product_field_optionswrite action

  Bulk-update option labels of a product enum/set field. Atomic: the whole request fails if any option ID does not exist.

• Code scan93 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 3 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Pipedrive CRM: common questions

Is Pipedrive CRM MCP server safe?

Mostly: it is graded B (83/100). Read the Pipedrive CRM safety report

How do I install Pipedrive CRM?

It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.

Does Pipedrive CRM need an API key?

Yes. The registry entry asks for PIPEDRIVE_API_KEY.

Is Pipedrive CRM maintained?

The last commit was 4 days ago (2026-09-19). The latest release is v2.7.0.

What can I use instead of Pipedrive CRM?

Servers from other publishers that do the same job: Pipedrive MCP server, Pipedrive MCP server and Pinlyx MCP server. Compare all Pipedrive CRM alternatives.