Pipedrive

Live

OAUTH 2.0

CRM

CRM & Sales

Every deal, contact, and pipeline stage your sales team manages lives in Pipedrive. Pipedrive MCP gives your agent authenticated access to CRM data scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the Pipedrive account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: Permissions enforced. 90-day audit trail.
Pipedrive
agent · Acme Q3
Run
Which deals are stuck in negotiation for over 14 days and what is the combined value?
S
pipedrive_deals_list
72ms
CRM agent
6 deals stuck in negotiation over 14 days. Combined value: $284,000. Oldest: Acme Corp (28 days, $80K, owner T. Barnes). Next steps: 4 have no activity in the last 7 days.
Sources: Pipedrive pipeline, negotiation stage
pipedrivemcp
6 deals
18:29
Message Claude...

Tools your crm agent reaches for on Pipedrive, scoped per user.

CALL ANY TOOL
List and inspect deals, search contacts, surface activities, and retrieve notes across the pipeline.
pipedrive_deals_list
List deals
List Pipedrive deals with stage, owner, and status filters.
Parameters
Name
Type
Required
Description
status
string
Optional
Filter: open, won, lost, deleted
owner_id
integer
Optional
Owner user ID filter
stage_id
integer
Optional
Pipeline stage ID filter
limit
integer
Optional
Max deals
pipedrive_deal_get
Get deal
pipedrive_persons_list
List contacts
pipedrive_activities_list
List activities
pipedrive_notes_list
List notes
Build your Agent
Drop the toolkit in, point it at the user, and your crm agent can use Pipedrive from the first run.
import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["pipedrive"], toolNames: ["pipedrive_deals_list", "pipedrive_deal_get", "pipedrive_persons_list"] },
pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
name: t.tool.definition.name,
description: t.tool.definition.description,
schema: z.object({}).passthrough(),
func: async (args) => {
const { data } = await sk.tools.executeTool({
toolName: t.tool.definition.name,
identifier: "user_123",
params: args,
});
return JSON.stringify(data);
},
}));

const agent = createReactAgent({ llm, tools: lcTools });
import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["pipedrive"], toolNames: ["pipedrive_deals_list", "pipedrive_deal_get", "pipedrive_persons_list"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
type: "function",
function: {
name: t.tool.definition.name,
description: t.tool.definition.description,
parameters: t.tool.definition.input_schema,
},
}));

const resp = await openai.responses.create({
model: "gpt-4o", input: prompt, tools: llmTools,
});
import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["pipedrive"], toolNames: ["pipedrive_deals_list", "pipedrive_deal_get", "pipedrive_persons_list"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
name: t.tool.definition.name,
description: t.tool.definition.description,
input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
model: "claude-sonnet-4-6", max_tokens: 1024,
tools: llmTools,
messages: [{ role: "user", content: prompt }],
});
import { Agent } from "@google/adk/agents";
import {
MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
connectionParams: new StreamableHTTPConnectionParams({
url: "https://mcp.scalekit.com/pipedrive",
headers: { Authorization: `Bearer ${userScopedToken}` },
}),
});

const agent = new Agent({
name: "agent", model: "gemini-2.0-flash",
tools: await toolset.getTools(),
});
Try these prompts
Paste any prompt into your agent to start using Pipedrive.
Pipeline & deals
Copy the prompt
Copied
List all open deals in [stage name].
Copy the prompt
Copied
Which deals have no activity in the last 7 days?
Copy the prompt
Copied
Get full details for deal [id].
Copy the prompt
Copied
List deals closing this month.
Contacts & notes
Copy the prompt
Copied
Find contacts at [company name].
Copy the prompt
Copied
List all notes on deal [id].
Copy the prompt
Copied
Get activities due today.
Copy the prompt
Copied
Which contacts have no associated deal?
Reporting
Copy the prompt
Copied
Combined value of deals in negotiation.
Copy the prompt
Copied
Win rate by pipeline stage this quarter.
Copy the prompt
Copied
Top 5 deals by value currently open.
Copy the prompt
Copied
Activities completed this week by rep.
SEE HOW AUTH WORKS
Users authorize Pipedrive once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Pipedrive
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Pipedrive
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Pipedrive
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Pipedrive
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
Same per-user auth pattern across other crm agents and MCP connectors. Working code, live demos, fork what fits.
GTM
Salesforce customer insights agent
Surface Salesforce account activity, NPS signals, and renewal flags into Slack threads for the account team.
SALES
Deal intelligence agent
Combine Gong, Attio, and Slack signals to surface deal risks and next-best actions. Updated after every call.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.
// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Pipedrive today. Others tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Pipedrive as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.
Where is the Pipedrive oauth 2.0 stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.
Can I limit what the agent is allowed to do in Pipedrive?
Yes. Pass a tool name filter to listScopedTools so the CRM agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Pipedrive.
What happens when a user revokes Pipedrive access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Can the agent see deals owned by other reps?
Depends on the authorizing user's Pipedrive visibility settings. Admin users see all deals; regular users see deals scoped to their visibility group. Pipedrive sharing rules apply at every agent call.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""pipedrive"": {
""url"": ""https://mcp.scalekit.com/pipedrive"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.pipedrive]
url = ""https://mcp.scalekit.com/pipedrive""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""pipedrive"": {
""url"": ""https://mcp.scalekit.com/pipedrive"",
""type"": ""http""
}
}
}