Pipedrive CRM

The tool requires PIPEDRIVE_API_KEY, a sensitive credential that can directly grant access to CRM data and actions; if exposed, it could allow reading or modifying business data such as contacts, deals, and activities. PIPEDRIVE_MODE, PIPEDRIVE_ENABLE_DESTRUCTIVE, and PIPEDRIVE_IMAGE_BASE_DIR are not traditional secrets, but they affect runtime mode, destructive-action enablement, and local path scope, so they should be configured carefully.

No specific remote host is listed in the materials, but based on its Pipedrive CRM integration purpose and API key requirement, the tool will likely communicate with Pipedrive-related services and send CRM data handled through the tool to the expected remote system. There is no clear evidence here of exfiltration to unrelated or suspicious endpoints.

The system marks it as executes-code, meaning it runs an MCP server process locally and executes program logic. This is a normal capability for MCP tools; the available materials do not show requests for unusual system privileges, unrelated script execution, or obvious privilege overreach.

The description suggests broad access across CRM resources such as deals, persons, organizations, and activities, with 155 tools in total, indicating a wide data surface. PIPEDRIVE_ENABLE_DESTRUCTIVE indicates possible modify/delete operations, and PIPEDRIVE_IMAGE_BASE_DIR implies it may read or process image files from a specified local directory, but the materials do not show local data access beyond its stated function.

Positive signals include an official registry source, an auditable open-source repository, and updates within the last year, all of which materially reduce supply-chain risk. However, the lack of a README, no declared license, and very low community adoption (0 stars) add uncertainty around transparency and maturity, making caution more appropriate than safe.