The Pipedrive connector.
Deals, contacts and pipeline. Connect once with your own key. Every agent your team runs reads the same 6 tools under one permission model.
How access is governed
6
Read tools
Open by default. They run when called, and every call is logged with the endpoint, tool and capability.
0
Write tools
Pipedrive exposes no write tools. Nothing it does mutates external state.
0
Destructive tools
Pipedrive defines no destructive tools. Nothing here deletes data.
Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.
Every Pipedrive tool
6 tools, named as the agent sees them.
- find_dealsread
Find deals. Pass `term` to text-search deal titles/notes/custom fields, or omit it and pass filters (status, pipeline_id, stage_id, owner_id, person_id, org_id) to list a slice of the pipeline. Returns deal ids for get_deal, plus pipeline_id/stage_id that list_pipelines decodes into names, and person_id/org_id that match list_persons / list_organizations.
- get_dealread
Get one deal in full, including custom fields. Use after find_deals to read everything on a specific deal.
- list_personsread
List contacts (persons) with name, emails, phones and their linked organization. Returns person ids you can pass to find_deals(person_id) to see everything that contact is involved in.
- list_organizationsread
List companies (organizations) with name, address and owner. Returns org ids for find_deals(org_id) and list_persons(org_id).
- list_activitiesread
List activities (calls, meetings, tasks, emails) with subject, type, due date and done flag. Use to answer "what is scheduled" or "what happened on this deal" — filter by deal_id, person_id or org_id from the other tools.
- list_pipelinesread
List every pipeline together with its stages, in order. Call this first when a deal report needs stage NAMES: deals only carry numeric pipeline_id / stage_id, and this is the lookup that decodes them. Also gives each stage's deal_probability for weighted forecasting.
Use it from any agent
The same Pipedrive tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.
{
"mcpServers": {
"growth": {
"type": "http",
"url": "https://app.notara.ai/mcp/g/acme/growth",
"headers": {
"Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
}
}
}
}The URL and token are placeholders. Real endpoints are issued per group from the dashboard.
Setup
- 01
Create a Pipedrive API Token in your Pipedrive account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.
- 02
Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.
- 03
The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.
Connect Pipedrive once. Use it everywhere.
Use Notara directly, or bring us the workflow that needs to be redesigned and built.