Skip to content
Agentmart
Submit a tool

MCP Pipedrive

Complete Pipedrive CRM integration with 254 MCP tools for deals, contacts, and pipelines

Connector by nubiia-dev · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 12
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/nubiia-dev-mcp-pipedrive

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Complete Pipedrive CRM integration with 254 MCP tools for deals, contacts, and pipelines

Use cases: crm

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools
62 read · 26 write · 17 delete · 2 not yet classified
Secrets
1 (API keys, tokens or passwords)
Install scripts
None found
Runs as
Node.js package

Tools by what they do 107

Read from the source code; the running server may list different tools.

Read 62 · Look things up without changing anything.

  • activities_get
  • activities_list
  • activities_list_all_auto
  • activities_list_by_deal
  • mailbox_get_message
  • mailbox_get_thread
  • mailbox_get_thread_messages
  • mailbox_get_threads
  • org_relationships_get
  • org_relationships_get_all
  • organizations_get
  • organizations_get_collection
Show 50 more tools
  • organizations_list
  • organizations_list_activities
  • organizations_list_all_auto
  • organizations_list_deals
  • organizations_list_field_updates
  • organizations_list_files
  • organizations_list_followers
  • organizations_list_mail_messages
  • organizations_list_permitted_users
  • organizations_list_persons
  • organizations_list_updates
  • organizations_search
  • persons_get
  • persons_get_collection
  • persons_list
  • persons_list_activities
  • persons_list_all_auto
  • persons_list_deals
  • persons_list_field_updates
  • persons_list_files
  • persons_list_followers
  • persons_list_mail_messages
  • persons_list_permitted_users
  • persons_list_products
  • persons_list_updates
  • persons_search
  • products_get
  • products_list
  • products_list_all_auto
  • products_list_deals
  • products_list_files
  • products_list_followers
  • products_list_permitted_users
  • products_search
  • project_templates_get
  • project_templates_list
  • projects_activities_list
  • projects_boards_get
  • projects_boards_list
  • projects_get
  • projects_groups_list
  • projects_list
  • projects_phases_get
  • projects_phases_list
  • projects_plan_get
  • projects_tasks_list
  • teams_get
  • teams_get_all
  • teams_get_user_teams
  • teams_get_users

Write 26 · Create, change, send or run things.

  • activities_create
  • activities_mark_as_done
  • activities_update
  • channels_create
  • channels_receive_message
  • mailbox_update_thread
  • org_relationships_create
  • org_relationships_update
  • organizations_add_follower
  • organizations_create
  • organizations_merge
  • organizations_update
Show 14 more tools
  • persons_add_follower
  • persons_add_picture
  • persons_create
  • persons_merge
  • persons_update
  • products_add_follower
  • products_create
  • products_update
  • projects_archive
  • projects_create
  • projects_update
  • teams_add_user
  • teams_create
  • teams_update

Delete 17 · Delete, drop, revoke or wipe things.

  • activities_bulk_delete
  • activities_delete
  • channels_delete
  • channels_delete_conversation
  • mailbox_delete_thread
  • org_relationships_delete
  • organizations_bulk_delete
  • organizations_delete
  • organizations_delete_follower
  • persons_bulk_delete
  • persons_delete
  • persons_delete_follower
Show 5 more tools
  • persons_delete_picture
  • products_delete
  • products_delete_follower
  • projects_delete
  • teams_delete_user

Not yet classified 2 · We could not tell from the name and description.

  • projects_plan_activities_update
  • projects_plan_tasks_update

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • PIPEDRIVE_API_TOKEN

Other settings (environment variables or headers).

  • PIPEDRIVE_COMPANY_DOMAIN
  • PIPEDRIVE_READ_ONLY
  • PIPEDRIVE_TOOLSETS

Network hosts it talks to 5

  • api.pipedrive.com · found in code
  • app.pipedrive.com · found in code
  • github.com · found in code
  • my-domain.com · found in code
  • my-server.com · found in code

Files it touches

  • Any path the agent passes to its tools

Tools (107)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • activities_bulk_delete

    Delete multiple activities in a single request. This endpoint allows you to delete up to 100 activities at once by providing an array of activity IDs. Workflow tips: - Maximum 100 activities per request - All activities must exist and be accessible to the user - Deletion is permanent and cannot be undone - Failed deletions for individual activities won't stop others from being deleted Common use cases: - Clean up completed activities in bulk - Remove outdated or duplicate activities - Archive old activities by deleting them Example: { "ids": [123, 456, 789] }

  • activities_create

    Create a new activity. Subject, type, and due_date are required. Can link to deals, persons, organizations, projects, or leads.

  • activities_delete

    Delete an activity by ID.

  • activities_get

    Get details of a specific activity by ID.

  • activities_list

    List activities with pagination and filtering options. Can filter by user, type, done status, and date range.

  • activities_list_all_auto

    Automatically fetch all activities across all pages. Use this when you need complete data without manual pagination.

  • activities_list_by_deal

    List all activities associated with a specific deal.

  • activities_mark_as_done

    Mark an activity as done. This is a convenience tool that updates the activity with done: true.

  • activities_update

    Update an existing activity. Only provided fields will be updated.

  • channels_create

    Create a new messaging channel in Pipedrive. Only admins are able to register new channels. This endpoint requires the **Messengers integration** OAuth scope and the Messaging manifest ready for the Messaging app extension. Required fields: - name: Name of the channel - provider_channel_id: ID of the channel in the provider system Optional fields: - avatar_url: Avatar URL for the channel - template_support: Whether the channel supports message templates (default: false) - provider_type: Type of messaging provider (other, facebook, instagram, whatsapp, telegram, line, viber) (default: other)…

  • channels_delete

    Delete an existing messenger's channel and all related entities (conversations and messages). This endpoint requires the **Messengers integration** OAuth scope and the Messaging manifest ready for the Messaging app extension. Warning: This action cannot be undone. The channel and all related conversations and messages will be permanently deleted. Required fields: - id: The ID of the channel provided by the integration Example: { "id": "e283f878-7ef9-4294-8e5c-04a7d003fd92" }

  • channels_delete_conversation

    Delete an existing conversation from a channel. This endpoint requires the **Messengers integration** OAuth scope and the Messaging manifest ready for the Messaging app extension. Warning: This action cannot be undone. The conversation and all its messages will be permanently deleted. Required fields: - channel_id: ID of the channel - conversation_id: ID of the conversation to delete Example: { "channel_id": "e283f878-7ef9-4294-8e5c-04a7d003fd92", "conversation_id": "063ffa46-831c-4027-a04c-b65e17f077b7" }

  • channels_receive_message

    Add an incoming message to a conversation in Pipedrive. This endpoint requires the **Messengers integration** OAuth scope and the Messaging manifest ready for the Messaging app extension. Required fields: - id: ID of the message - channel_id: ID of the channel the message was sent to - sender_id: ID of the message sender - conversation_id: ID of the conversation this message belongs to - message: Content of the message - status: Status of the message (e.g., sent, delivered, read) - created_at: When the message was created (ISO 8601 format) Optional fields: - reply_by: When a reply is expect…

  • mailbox_delete_thread

    Mark a mail thread as deleted.

  • mailbox_get_message

    Get details of a specific mail message by ID.

Show 92 more tools
  • mailbox_get_thread

    Get details of a specific mail thread by ID.

  • mailbox_get_thread_messages

    Get all mail messages inside a specific mail thread.

  • mailbox_get_threads

    Get mail threads in a specified folder ordered by the most recent message within.

  • mailbox_update_thread

    Update the properties of a mail thread.

  • org_relationships_create

    Create a new organization relationship.

  • org_relationships_delete

    Delete an organization relationship.

  • org_relationships_get

    Get details of a specific organization relationship by ID.

  • org_relationships_get_all

    Get all relationships for a specific organization.

  • org_relationships_update

    Update the properties of an organization relationship.

  • organizations_add_follower

    Add a follower to an organization.

  • organizations_bulk_delete

    Delete multiple organizations in bulk. Efficiently deletes multiple organization records in a single operation. This is useful for: - Data cleanup and maintenance - Removing duplicate records - Batch operations after data imports - CRM hygiene improvements - GDPR and data retention compliance WARNING: This action is irreversible. All specified organizations will be permanently deleted, including: - Organization data and custom fields - Associated notes (if configured) - Follow relationships - Activity history (may be preserved depending on settings) Best practices: 1. Always verify the IDs …

  • organizations_create

    Create a new organization. Name is required. Supports address fields and custom fields. Custom fields: - Pass display names: { "custom_fields": { "Industry": "Tech", "Tier": "Gold" } } - Or hash keys directly: { "custom_fields": { "abc123...": "raw value" } } - For enum/set fields, pass option labels (not ids).

  • organizations_delete

    Delete an organization by ID.

  • organizations_delete_follower

    Delete a follower from an organization. Removes a user from the list of followers for this organization. After removal: - The user will no longer receive notifications about organization updates - They will still have access to the organization if permissions allow - This only affects notification settings, not access rights This is useful for: - Managing notification preferences - Adjusting team involvement - Reducing notification noise - Changing account ownership responsibilities Note: The follower_id is the user ID of the follower to remove.

  • organizations_get

    Get details of a specific organization by ID.

  • organizations_get_collection

    Get all organizations using the collection endpoint. This endpoint provides an alternative way to fetch organizations with different capabilities: - Cursor-based pagination (more efficient for large datasets) - Date range filtering (since/until) - Optimized for data synchronization - Better performance for large-scale operations Key differences from organizations/list: - Uses cursor pagination instead of offset/limit - Supports date-based filtering for incremental sync - More efficient for fetching large volumes - Better for ETL and data integration scenarios Parameters: - cursor: Paginatio…

  • organizations_list

    List organizations with pagination support. Returns paginated list of organizations with filtering options.

  • organizations_list_activities

    List all activities associated with a specific organization.

  • organizations_list_all_auto

    Automatically fetch all organizations across all pages. Use this when you need complete data without manual pagination.

  • organizations_list_deals

    List all deals associated with a specific organization.

  • organizations_list_field_updates

    List updates about organization field values (changelog). Returns a chronological list of changes made to organization fields. This is useful for: - Auditing field changes - Tracking data modifications - Understanding update history - Compliance and reporting The changelog shows: - Which fields were changed - Old and new values - Who made the change - When the change occurred Uses cursor-based pagination for efficient navigation through large change histories.

  • organizations_list_files

    List all files attached to a specific organization.

  • organizations_list_followers

    List all followers of a specific organization. Returns the users that are following this organization and will receive notifications about updates. Each follower entry includes: - User ID - User name - User email - When they started following This is useful for: - Checking who is tracking an organization - Auditing team access - Managing notifications

  • organizations_list_mail_messages

    List mail messages associated with an organization. Returns all email messages linked to this organization, including: - Emails sent to the organization - Emails received from the organization - Email threads and conversations - Message subjects and snippets - Send/receive timestamps - Associated deals or persons This is useful for: - Reviewing email communication history - Understanding customer interactions - Preparing for meetings or calls - Tracking email engagement - CRM integration and context Supports pagination for handling large email histories.

  • organizations_list_permitted_users

    List users permitted to access an organization. Returns a list of all users who have permission to view and/or edit this organization record. This is determined by: - The organization's visibility settings - User roles and permissions - Team assignments - Sharing rules Each entry includes: - User ID - User name and email - Access level (view/edit) - Permission source This is useful for: - Security auditing - Access management - Understanding data visibility - Compliance and governance - Team coordination Note: Results depend on the visibility settings of the organization (e.g., owner only,…

  • organizations_list_persons

    List all persons associated with a specific organization.

  • organizations_list_updates

    List updates about an organization (activity stream). Returns a comprehensive timeline of all activities and changes related to an organization: - Field changes and updates - Activities (calls, meetings, emails) - Notes added - Deals created or updated - Files attached - Followers added - Other related events This provides a complete audit trail and activity history for the organization. Parameters: - all_changes: Set to show all field changes (not just recent) - items: Filter which types of items to include in the stream Useful for: - Getting a complete overview of interactions - Understa…

  • organizations_merge

    Merge two organizations into one. Combines two organization records, moving all related data to the primary organization: - All deals are transferred - All activities are transferred - All notes are transferred - All files are transferred - All persons are transferred - Custom field data is merged - The secondary organization is deleted WARNING: This action is irreversible. The organization specified in merge_with_id will be deleted permanently. Best practices: 1. Review both organizations thoroughly before merging 2. Ensure you're merging duplicates, not different organizations 3. The orga…

  • organizations_search

    Search organizations by name or other fields. Returns matching organizations.

  • organizations_update

    Update an existing organization. Only provided fields will be updated. Custom fields: - Pass display names: { "custom_fields": { "Industry": "Tech", "Tier": "Gold" } } - Or hash keys directly: { "custom_fields": { "abc123...": "raw value" } } - For enum/set fields, pass option labels (not ids).

  • persons_add_follower

    Add a follower to a person. Followers are users who will receive notifications about updates to this person. This is useful for team collaboration and keeping stakeholders informed. When a user follows a person, they will be notified about: - Changes to person details - New activities - New deals - New notes - Other updates Note: Users can only be added as followers if they have access to the person.

  • persons_add_picture

    Add or update a person's profile picture. Uploads an image file to set as the person's profile picture. The image will be: - Displayed in person records - Shown in lists and search results - Visible to users with access to the person - Used across the Pipedrive interface Image requirements: - Format: JPEG, PNG, GIF - Recommended size: 512x512 pixels - Maximum file size: Typically 5-10 MB (check Pipedrive limits) Cropping parameters (optional): - Use crop_x, crop_y to set the top-left corner of the crop area - Use crop_width, crop_height to define the crop dimensions - All crop values are in…

  • persons_bulk_delete

    Delete multiple persons in bulk. Efficiently deletes multiple person records in a single operation. This is useful for: - Data cleanup and maintenance - Removing duplicate records - Batch operations after data imports - CRM hygiene improvements - GDPR and data retention compliance WARNING: This action is irreversible. All specified persons will be permanently deleted, including: - Person data and custom fields - Associated notes (if configured) - Follow relationships - Activity history (may be preserved depending on settings) Best practices: 1. Always verify the IDs before deletion 2. Consi…

  • persons_create

    Create a new person in Pipedrive. Required fields: - name: Full name of the person Optional fields: - owner_id: User who will own this person - org_id: Organization this person belongs to - email: Array of email addresses with format: [{"value": "john@company.com", "primary": true, "label": "work"}] - phone: Array of phone numbers with format: [{"value": "+1234567890", "primary": true, "label": "mobile"}] - job_title: Job title / function of the person (max 255 characters) - visible_to: Visibility level (1=owner only, 3=entire company, 5=owner's followers, 7=visibility group) - marketing_sta…

  • persons_delete

    Delete a person from Pipedrive. Warning: This action cannot be undone. The person will be permanently deleted. Note: Deleting a person does not automatically delete associated: - Deals (they will remain but without the person link) - Activities (they will remain but without the person link) - Notes (they will remain but without the person link)

  • persons_delete_follower

    Delete a follower from a person. Removes a user from the list of followers for this person. After removal: - The user will no longer receive notifications about person updates - They will still have access to the person if permissions allow - This only affects notification settings, not access rights This is useful for: - Managing notification preferences - Adjusting team involvement - Reducing notification noise - Changing account ownership responsibilities Note: The follower_id is the user ID of the follower to remove.

  • persons_delete_picture

    Delete a person's profile picture. Removes the profile picture from the person record. The person will revert to: - Default avatar - Or initials-based placeholder - Depending on Pipedrive settings This is useful for: - Updating outdated photos - Privacy compliance (GDPR, etc.) - Data cleanup - Resetting profile images Note: This does not delete the image file from Pipedrive storage, it only removes the association with the person.

  • persons_get

    Get detailed information about a specific person by ID. Returns all person data including: - Basic info (name, owner, organization) - Contact details (emails, phones) - Visibility and marketing status - Activity counts (deals, activities, files, etc.) - Timeline info (next activity, last activity) - Custom fields

  • persons_get_collection

    Get all persons using the collection endpoint. This endpoint provides an alternative way to fetch persons with different capabilities: - Cursor-based pagination (more efficient for large datasets) - Date range filtering (since/until) - Optimized for data synchronization - Better performance for large-scale operations Key differences from persons_list: - Uses cursor pagination instead of offset/limit - Supports date-based filtering for incremental sync - More efficient for fetching large volumes - Better for ETL and data integration scenarios Parameters: - cursor: Pagination cursor from prev…

  • persons_list

    List all persons with optional filtering and pagination. Supports filtering by: - user_id: Filter by owner - org_id: Filter by organization - first_char: Filter by first character of name (single letter) - filter_id: Apply a saved filter Returns paginated results. Use start/limit for manual pagination.

  • persons_list_activities

    List all activities associated with a specific person. Returns all activities (calls, meetings, tasks, etc.) linked to the person, including: - Activity details (type, subject, description) - Due date and time - Completion status - Owner/assignee information - Related deal/organization Filters: - done: Filter by completion status (true=completed, false=pending) Supports pagination for large result sets.

  • persons_list_all_auto

    Automatically fetch ALL persons using pagination. This tool handles pagination automatically and returns all persons matching the filters. Use this when you need the complete list without managing pagination manually. Warning: This can return a large dataset if you have many persons. Supports the same filters as persons_list: - user_id: Filter by owner - org_id: Filter by organization - first_char: Filter by first character of name - filter_id: Apply a saved filter

  • persons_list_deals

    List all deals associated with a specific person. Returns all deals where the person is linked, including: - Deal details (title, value, stage, status) - Timeline information - Owner information - Organization information Filters: - status: Filter by deal status (open, won, lost, deleted, all_not_deleted) - sort: Sort by specific field Supports pagination for large result sets.

  • persons_list_field_updates

    List updates about person field values (changelog). Returns a chronological list of changes made to person fields. This is useful for: - Auditing field changes - Tracking data modifications - Understanding update history - Compliance and reporting The changelog shows: - Which fields were changed - Old and new values - Who made the change - When the change occurred Uses cursor-based pagination for efficient navigation through large change histories.

  • persons_list_files

    List all files attached to a specific person. Returns all files associated with the person, including: - File metadata (name, type, size) - Upload information (uploader, timestamps) - File URL for download - Associated deal/organization if applicable Supports: - Pagination for large file lists - Sorting by various fields This includes files uploaded directly to the person and files from related deals/activities.

  • persons_list_followers

    List all followers of a specific person. Returns a list of users who are following this person and will receive notifications about updates. Each follower entry includes: - User ID - User name - User email - When they started following This is useful for: - Checking who is tracking a person - Auditing team access - Managing notifications

  • persons_list_mail_messages

    List mail messages associated with a person. Returns all email messages linked to this person, including: - Emails sent to the person - Emails received from the person - Email threads and conversations - Message subjects and snippets - Send/receive timestamps - Associated deals or organizations This is useful for: - Reviewing email communication history - Understanding customer interactions - Preparing for meetings or calls - Tracking email engagement - CRM integration and context Supports pagination for handling large email histories.

  • persons_list_permitted_users

    List users permitted to access a person. Returns a list of all users who have permission to view and/or edit this person record. This is determined by: - The person's visibility settings - User roles and permissions - Team assignments - Sharing rules Each entry includes: - User ID - User name and email - Access level (view/edit) - Permission source This is useful for: - Security auditing - Access management - Understanding data visibility - Compliance and governance - Team coordination Note: Results depend on the visibility settings of the person (e.g., owner only, owner's team, everyone, …

  • persons_list_products

    List products associated with a person. Returns all products that have been sold to or associated with this person through deals. This provides an overview of: - All products the person has purchased - Products in active deals - Historical product associations - Product preferences and patterns Each entry includes: - Product details (name, code, price) - Deal information - Quantities and pricing - Dates and status - Custom product fields This is useful for: - Understanding customer purchase history - Cross-selling and upselling opportunities - Product preferences analysis - Revenue tracking…

  • persons_list_updates

    List updates about a person (activity stream). Returns a comprehensive timeline of all activities and changes related to a person: - Field changes and updates - Activities (calls, meetings, emails) - Notes added - Deals created or updated - Files attached - Followers added - Other related events This provides a complete audit trail and activity history for the person. Parameters: - all_changes: Set to show all field changes (not just recent) - items: Filter which types of items to include in the stream Useful for: - Getting a complete overview of interactions - Understanding person engagem…

  • persons_merge

    Merge two persons into one. Combines two person records, moving all related data to the primary person: - All deals are transferred - All activities are transferred - All notes are transferred - All files are transferred - Email and phone numbers are combined - Custom field data is merged - The secondary person is deleted WARNING: This action is irreversible. The person specified in merge_with_id will be deleted permanently. Best practices: 1. Review both persons thoroughly before merging 2. Ensure you're merging duplicates, not different people 3. The person with ID 'id' will be kept (prim…

  • persons_search

    Search for persons by name, email, phone, or notes. The search uses Pipedrive's intelligent search that: - Searches across multiple fields (name, email, phone, notes, custom fields) - Supports fuzzy matching by default - Returns ranked results Search options: - term: Search term (minimum 2 characters) - fields: Specific fields to search in (default: all fields) - exact_match: Use exact matching instead of fuzzy search - org_id: Filter results by organization - include_fields: Additional fields to include in response The search is case-insensitive and supports partial matches.

  • persons_update

    Update an existing person's information. Required fields: - id: Person ID to update Optional fields (only provide fields you want to change): - name: Full name - owner_id: User who will own this person - org_id: Organization this person belongs to - email: Array of email addresses with format: [{"value": "john@company.com", "primary": true, "label": "work"}] - phone: Array of phone numbers with format: [{"value": "+1234567890", "primary": true, "label": "mobile"}] - job_title: Job title / function of the person (max 255 characters) - visible_to: Visibility level (1=owner only, 3=entire compa…

  • products_add_follower

    Add a follower to a product. Followers are users who will receive notifications about updates to this product. This is useful for team collaboration and keeping stakeholders informed. When a user follows a product, they will be notified about: - Changes to product details - Product being added to deals - Price changes - Other updates Note: Users can only be added as followers if they have access to the product.

  • products_create

    Create a new product in Pipedrive. Required fields: - name: Product name Optional fields: - code: Product code (SKU) - description: Product description - unit: Unit type (e.g., "pcs", "kg", "hours") - tax: Tax percentage (0-100) - active_flag: Whether product is active (default: true) - selectable: Whether product can be selected in deals (default: true) - visible_to: Visibility level (1=owner only, 3=entire company) - owner_id: User who will own this product - prices: Array of price objects with format: [{"price": 100, "currency": "USD", "cost": 50}] - billing_frequency: One of: one-time, w…

  • products_delete

    Delete a product from Pipedrive. The product will be marked as deleted and after 30 days will be permanently deleted. Note: Deleting a product does not automatically remove it from existing deals. Deals that already have this product attached will keep the product information. This is useful for: - Discontinuing products - Cleaning up old inventory - Removing test products

  • products_delete_follower

    Remove a follower from a product. Stops a user from receiving notifications about this product. Note: You need the follower_id (the relationship ID), not the user_id. Get this from the products/list_followers endpoint.

  • products_get

    Get detailed information about a specific product. Returns complete product data including: - Basic information (name, code, description, unit) - Pricing information (prices array with different currencies) - Billing information (frequency, cycles) - Metadata (owner, visibility, timestamps) - Tax and category information Use this when you need full details about a product, such as: - Viewing complete product specifications - Getting pricing information - Checking product availability and status

  • products_list

    List all products with optional filtering and pagination. Supports filtering by: - user_id: Filter by owner - filter_id: Apply a saved filter - ids: Array of specific product IDs to return - first_char: Filter by first character of name (single letter) - get_summary: Include total count in response Returns paginated results. Use start/limit for manual pagination.

  • products_list_all_auto

    Automatically fetch ALL products using pagination. This tool handles pagination automatically and returns all products matching the filters. Use this when you need the complete list without managing pagination manually. Warning: This can return a large dataset if you have many products. Supports the same filters as products/list: - user_id: Filter by owner - filter_id: Apply a saved filter - first_char: Filter by first character of name

  • products_list_deals

    Get all deals where a specific product is attached. Returns a list of deals that have this product in their products list. This is useful for: - Tracking product usage across deals - Analyzing product performance - Finding deals with specific products - Revenue forecasting by product Filter options: - status: Filter by deal status (open, won, lost, deleted, all_not_deleted) Each deal includes full deal information plus product attachment details.

  • products_list_files

    List all files attached to a specific product. Returns files associated with the product such as: - Product images - Documentation - Specifications - Contracts - Other attachments Supports sorting by: - id: File ID - update_time: Last update time Use this for: - Viewing product documentation - Accessing product images - Managing product attachments

  • products_list_followers

    List all followers of a specific product. Returns a list of users who are following this product and will receive notifications about updates. Each follower entry includes: - User ID - Follower ID (relationship ID) - Product ID - When they started following This is useful for: - Checking who is tracking a product - Auditing team access - Managing notifications

  • products_list_permitted_users

    List all users who have access to view and edit a specific product. Returns a list of users who have permission to access this product based on visibility settings and team structure. Workflow tips: - Product visibility determines which users can access it - Visibility can be: owner only, owner's team, entire company, or custom - This is useful for understanding who can see and modify the product - Access permissions affect whether users can add the product to deals Common use cases: - Audit product access permissions - Verify team members can see a product - Check visibility before sharing…

  • products_search

    Search for products by name, code, or custom fields. This is a powerful search tool that finds products matching your query across multiple fields. Search features: - Searches product name, code, and custom fields by default - Minimum 1 character required (or use exact_match for single chars) - Returns relevance-scored results - Supports pagination Use cases: - Finding products by partial name - Looking up products by code/SKU - Searching custom product attributes - Quick product lookup during deal creation

  • products_update

    Update an existing product in Pipedrive. All fields are optional except id. Only provide the fields you want to update. Updatable fields: - name: Product name - code: Product code (SKU) - description: Product description - unit: Unit type - tax: Tax percentage - active_flag: Whether product is active - selectable: Whether product can be selected in deals - visible_to: Visibility level - owner_id: Product owner - prices: Array of price objects - billing_frequency: Billing frequency - billing_frequency_cycles: Number of billing cycles Note: When updating prices, the entire prices array is rep…

  • project_templates_get

    Get details of a single project template by ID. Returns complete information about a project template including its structure, phases, groups, tasks, and activities. Workflow tips: - Templates contain the blueprint for creating standardized projects - Use this to inspect template details before using it to create a project - Template structure includes phases, task groups, tasks, and activities - You can create a project from this template using projects/create Common use cases: - View template structure before creating a project - Inspect phases and tasks included in the template - Review …

  • project_templates_list

    List all project templates with cursor-based pagination. Project templates are reusable blueprints for creating new projects with predefined phases, tasks, and activities. Workflow tips: - Templates include project structure (phases, groups, tasks, activities) - Use templates to standardize project creation across your organization - Templates can be created from existing projects - Cursor-based pagination for large template lists Common use cases: - List all available templates: {} - Get templates with custom page size: { "limit": 50 } - Paginate through templates: { "cursor": "abc123", "l…

  • projects_activities_list

    Get all activities linked to a specific project. Returns activity details including type, due date, and completion status.

  • projects_archive

    Archive a project. Archived projects can be retrieved by using the include_archived filter.

  • projects_boards_get

    Get details of a specific project board by ID.

  • projects_boards_list

    Get all project boards that are not deleted. Returns boards ordered by their order number.

  • projects_create

    Create a new project. Requires title, board_id, and phase_id. Optionally include description, dates, deals, and labels.

  • projects_delete

    Delete a project by marking it as deleted. This does not permanently remove the project.

  • projects_get

    Get details of a specific project by ID. Returns complete project information including custom fields.

  • projects_groups_list

    Get all active groups under a specific project. Returns groups ordered by their order number.

  • projects_list

    List projects with cursor-based pagination. Returns projects with filtering options by status, phase, and archive state.

  • projects_phases_get

    Get details of a specific project phase by ID.

  • projects_phases_list

    Get all active project phases under a specific board. Returns phases ordered by their order number.

  • projects_plan_activities_update

    Update an activity phase or group in a project plan. Allows moving activities between phases and groups.

  • projects_plan_get

    Get project plan showing all tasks and activities with their phases and groups. Returns plan structure.

  • projects_plan_tasks_update

    Update a task phase or group in a project plan. Allows moving tasks between phases and groups.

  • projects_tasks_list

    Get all tasks linked to a specific project. Returns task details including assignee and completion status.

  • projects_update

    Update an existing project. Provide the project ID and fields to update.

  • teams_add_user

    Add a user to a team.

  • teams_create

    Add a new team to the company.

  • teams_delete_user

    Remove a user from a team.

  • teams_get

    Get details of a specific team by ID.

  • teams_get_all

    Get all teams within the company.

  • teams_get_user_teams

    Get all teams that a specific user belongs to.

  • teams_get_users

    Get all users in a team.

  • teams_update

    Update the properties of a team.

Signals

Stars
12
Forks
10
Open issues
0
Weekly downloads
230
Last commit
Oct 22, 2026 (7 days ago)
Last release
Oct 22, 2026 (7 days ago)
Last package publish
Oct 22, 2026 (7 days ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.nubiia-dev/mcp-pipedrive
Version
2.7.1
Auth
API key
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from nubiia-dev

Cite this page

MCP Pipedrive. Agent Mart. https://agentmart.dev/connectors/nubiia-dev-mcp-pipedrive (last updated 2026-10-24)