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 MCP Integration for CrewAI

Connect Pipedrive to CrewAI through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write API token auth

Submit Pipedrive feedback View package source

Connect Pipedrive to CrewAI

Expose KosmoKrator integrations to CrewAI workers as scoped local tools.

Wrap kosmo integrations:call for specific tasks or connect workers to a local MCP gateway. The gateway is local, scoped to this integration, and starts with --write=deny so CrewAI can inspect read-capable tools without receiving write access by default.

Pipedrive MCP Config for CrewAI

Use per-worker integration scopes to avoid giving every worker every tool.

{
  "mcpServers": {
    "kosmokrator-pipedrive": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=pipedrive",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=pipedrive --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Pipedrive instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Pipedrive Tools Visible to CrewAI

CrewAI sees stable MCP tool names generated from the Pipedrive integration catalog.

MCP tool	Source function	Type	Description
`integration__pipedrive__pipedrive_create_deal`	`pipedrive.pipedrive_create_deal`	Write	Create a new deal in Pipedrive. Provide a title and optionally set value, currency, person, organization, stage, and other deal fields.
`integration__pipedrive__pipedrive_get_current_user`	`pipedrive.pipedrive_get_current_user`	Read	Get the profile of the currently authenticated Pipedrive user — name, email, company, timezone, and other account details.
`integration__pipedrive__pipedrive_get_deal`	`pipedrive.pipedrive_get_deal`	Read	Get full details for a single deal in Pipedrive, including value, stage, person, organization, and custom fields.
`integration__pipedrive__pipedrive_get_person`	`pipedrive.pipedrive_get_person`	Read	Get full details for a single person (contact) in Pipedrive, including email, phone, organization, and custom fields.
`integration__pipedrive__pipedrive_list_deals`	`pipedrive.pipedrive_list_deals`	Read	List deals in Pipedrive with optional filters for user, person, organization, and status. Returns a paginated list of deals with key details.
`integration__pipedrive__pipedrive_list_organizations`	`pipedrive.pipedrive_list_organizations`	Read	List organizations in Pipedrive. Returns a paginated list with name, address, owner, and other details.
`integration__pipedrive__pipedrive_list_persons`	`pipedrive.pipedrive_list_persons`	Read	List persons (contacts) in Pipedrive. Returns a paginated list with name, email, phone, organization, and owner details.

Related Pipedrive Pages

Pipedrive CLIUse direct JSON commands instead of MCP discovery. Pipedrive MCPFull gateway reference and MCP tool names. KosmoKrator for CrewAIClient-level gateway setup.