Pipedrive
Read and update Pipedrive deals, contacts, activities, and pipelines
Maverick
@maverick
Install
$ openclaw skills install @maverick/maverick-pipedrive-mcpPipedrive
Quick start
This skill is a thin pass-through to a local stdio MCP server. mcporter spawns the skill's Python server on each call, refreshes the OAuth access token when needed, and injects the fresh token into the server env.
mcporter --config {baseDir}/mcporter.json list maverick-pipedrive --schema
For structured output:
mcporter --config {baseDir}/mcporter.json call --output json maverick-pipedrive.<tool> key=value
Safety
Write operations that create records, update properties, change deal stages, mark activities done, create notes, or delete data modify Pipedrive CRM state visible to the connected account. Confirm clear user intent before invoking write tools — search and read tools are safe to call freely while exploring. Search deals, people, organizations, and activities before assuming IDs, and read current deal stage, owner, value, and activity history before updating.
Authentication
Credentials are provisioned at setup time by scripts/setup.sh (a thin delegator to scripts/init-mcporter-oauth.sh) and stored in mcporter's local vault. The setup hook requires these credential env vars:
MAVERICK_PIPEDRIVE_MCP_REFRESH_TOKENMAVERICK_PIPEDRIVE_MCP_CLIENT_IDMAVERICK_PIPEDRIVE_MCP_CLIENT_SECRETMAVERICK_PIPEDRIVE_MCP_ACCESS_TOKENMAVERICK_PIPEDRIVE_MCP_API_BASE
For refresh-aware seeding, setup also reads optional expiry metadata env vars when the provisioner supplies them:
MAVERICK_PIPEDRIVE_MCP_EXPIRES_ATMAVERICK_PIPEDRIVE_MCP_EXPIRES_INMAVERICK_PIPEDRIVE_MCP_REFRESH_TOKEN_EXPIRES_AT
mcporter refreshes expired Pipedrive access tokens through Pipedrive's token endpoint before spawning the stdio server, then injects the token into MAVERICK_PIPEDRIVE_MCP_ACCESS_TOKEN. If calls keep returning auth errors after retry, the OAuth grant has likely been revoked or expired; reconnect the integration.
Data flow
Tool calls run locally: mcporter spawns this skill's Python MCP server as a subprocess, and that server forwards Pipedrive API requests with the refreshed OAuth bearer token. Pipedrive sees the deal, person, organization, activity, pipeline, and sales-workflow data referenced by each call. Use this skill for Pipedrive-related work only; do not pass unrelated sensitive content through these tools.
Dependencies
mcporter(github.com/steipete/mcporter) — MCP CLI used to invoke the local MCP server. If it is missing from PATH, the frontmatter installs the exactmcporter@0.13.10package with npm install scripts disabled.uv(docs.astral.sh/uv) — runs the Python wrapper and local MCP server from their inline dependency metadata.
Top skills in this category
API Gateway
@byungkyuCall third-party APIs through the Maton gateway, which injects the credential for an app the user has already connected. Use this skill when the user names a connected app and a concrete action in it - read a mailbox, query a CRM, file an issue, update a spreadsheet, etc.
HubSpot
@hith3shHubSpot CRM API integration with managed OAuth. Manage contacts, companies, deals, pipelines, tickets, products, line items, marketing emails, and workflows....
Master Marketing
@tevfikgulepAll-in-one marketing engine combining growth strategy, content remixing, and trend monitoring. Drive growth with data-driven strategies, repurposed content across all platforms, and real-time trend analysis.
Feishu Bridge
@alexanysConnect a Feishu (Lark) bot to Clawdbot via WebSocket long-connection. No public server, domain, or ngrok required. Use when setting up Feishu/Lark as a messaging channel, troubleshooting the Feishu bridge, or managing the bridge service (start/stop/logs). Covers bot creation on Feishu Open Platform, credential setup, bridge startup, macOS launchd auto-restart, and group chat behavior tuning.
Zoho CRM
@byungkyuZoho CRM API integration with managed OAuth. Manage leads, contacts, accounts, deals, and other CRM records. Use this skill when users want to read, create, update, or delete CRM records, search contacts, manage sales pipelines, access organization settings, manage users, or retrieve module metadata in Zoho CRM. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key. Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Zoho CRM connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Zoho CRM action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Zoho CRM examples; they add no Zoho CRM capability - Zoho CRM is not an event source, a trigger cannot read Zoho CRM data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).