Pipedrive MCP by usefulapi

Reviewed 1d ago.

• tools: 19 tools scanned
• metadata: scanned

No findings.

Tools (19)

• pipedrive_list_deals

  List deals, optionally filtered by filter/owner/person/org/pipeline/stage/status and sorted. Pipedrive REST: GET /api/v2/deals.

• pipedrive_get_deal

  Get a single deal by its id. Pipedrive REST: GET /api/v2/deals/{id}.

• pipedrive_search_deals

  Search deals by term across selected fields. Pipedrive REST: GET /api/v2/deals/search.

• pipedrive_list_persons

  List persons (contacts), optionally filtered by filter/owner/org and sorted. Pipedrive REST: GET /api/v2/persons.

• pipedrive_get_person

  Get a single person (contact) by its id. Pipedrive REST: GET /api/v2/persons/{id}.

• pipedrive_search_persons

  Search persons (contacts) by term across selected fields. Pipedrive REST: GET /api/v2/persons/search.

• pipedrive_list_organizations

  List organizations, optionally filtered by filter/owner and sorted. Pipedrive REST: GET /api/v2/organizations.

• pipedrive_get_organization

  Get a single organization by its id. Pipedrive REST: GET /api/v2/organizations/{id}.

• pipedrive_search_organizations

  Search organizations by term across selected fields. Pipedrive REST: GET /api/v2/organizations/search.

• pipedrive_list_activities

  List activities (tasks/events), optionally filtered by filter/owner/deal/person/org/done/updated_since. Pipedrive REST: GET /api/v2/activities.

• pipedrive_list_pipelines

  List all pipelines. Pipedrive REST: GET /api/v2/pipelines.

• pipedrive_list_stages

  List stages, optionally restricted to a single pipeline. Pipedrive REST: GET /api/v2/stages.

• pipedrive_search_items

  Global search across multiple item types (deals, persons, organizations, products, leads, files, etc.). Pipedrive REST: GET /api/v2/itemSearch.

• pipedrive_get_current_user

  Get the authenticated user's profile (name, email, company, locale, timezone). Pipedrive REST: GET /api/v1/users/me.

• pipedrive_list_notes

  List notes, optionally filtered by user/deal/person/org/lead. Uses v1 (v2 has no notes endpoint) with start+limit pagination. Pipedrive REST: GET /api/v1/notes.

• pipedrive_create_deal

  Create a new deal. `title` is required; link it to a person/org/pipeline/stage/owner as needed. Pipedrive REST: POST /api/v2/deals.

• pipedrive_create_person

  Create a new person (contact). `name` is required; `email`/`phone` are convenience strings mapped to Pipedrive's structured emails/phones arrays. Pipedrive REST: POST /api/v2/persons.

• pipedrive_create_activity

  Create a new activity (task/event). `subject` is required; link it to a deal/person/org and set type/date/time as needed. Pipedrive REST: POST /api/v2/activities.

• pipedrive_add_note

  Add a note, linked to at least one of a deal/person/organization/lead. `content` is required (HTML or plain text). Uses v1 (v2 has no notes endpoint). Pipedrive REST: POST /api/v1/notes.