Can I use Pipedrive as a CLI?

Yes. KosmoKrator exposes a Pipedrive CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Pipedrive through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Pipedrive tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Pipedrive credentials stored?

Pipedrive credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Pipedrive MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Pipedrive CLI for Headless Automation

Use the Pipedrive CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write API token auth

Submit Pipedrive feedback View package source

Pipedrive CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Pipedrive CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Pipedrive CLI for Headless Automation
kosmokrator integrations:configure pipedrive --set api_token="$PIPEDRIVE_API_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call pipedrive.pipedrive_create_deal '{"title":"example_title","value":1,"currency":"example_currency","person_id":1,"org_id":1,"stage_id":1,"pipeline_id":1,"status":"example_status"}' --json

Discovery Before Execution

Agents and scripts can inspect Pipedrive docs and schemas before choosing a function.

kosmo integrations:docs pipedrive --json
kosmo integrations:docs pipedrive.pipedrive_create_deal --json
kosmo integrations:schema pipedrive.pipedrive_create_deal --json
kosmo integrations:search "Pipedrive" --json
kosmo integrations:list --json

Useful Pipedrive CLI Functions

Function	Type	Parameters	Description
`pipedrive.pipedrive_create_deal`	Write	title, value, currency, person_id, org_id, stage_id, pipeline_id, status, probability, note	Create a new deal in Pipedrive. Provide a title and optionally set value, currency, person, organization, stage, and other deal fields.
`pipedrive.pipedrive_get_current_user`	Read	none	Get the profile of the currently authenticated Pipedrive user — name, email, company, timezone, and other account details.
`pipedrive.pipedrive_get_deal`	Read	id	Get full details for a single deal in Pipedrive, including value, stage, person, organization, and custom fields.
`pipedrive.pipedrive_get_person`	Read	id	Get full details for a single person (contact) in Pipedrive, including email, phone, organization, and custom fields.
`pipedrive.pipedrive_list_deals`	Read	user_id, person_id, org_id, status, limit, start	List deals in Pipedrive with optional filters for user, person, organization, and status. Returns a paginated list of deals with key details.
`pipedrive.pipedrive_list_organizations`	Read	limit, start	List organizations in Pipedrive. Returns a paginated list with name, address, owner, and other details.
`pipedrive.pipedrive_list_persons`	Read	limit, start	List persons (contacts) in Pipedrive. Returns a paginated list with name, email, phone, organization, and owner details.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Pipedrive CLI Pages

CI Pipedrive CLI for CI. Cron Jobs Pipedrive CLI for cron jobs. Shell Scripts Pipedrive CLI for shell scripts. Coding Agents Pipedrive CLI for coding agents.