Indraft vs Pipedrive MCP Server

A side-by-side look at the Indraft and Pipedrive MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Indraft logoIndraftCustomer Data Platforms · Remote HTTP/SSERead and write a CRM built for agents. Every change carries who asserted it and how.37FairAuth: not declaredPipedrive MCP Server logoPipedrive MCP ServerCustomer Data Platforms · Local subprocess (stdio)MCP server for Pipedrive CRM. 155 tools covering deals, persons, organizations, activities, products, projects, tasks, leads, notes, mail, and fields. stdio transport, API-key auth, delete tools gated behind an env flag. Published on npm as @ckalima/pipedrive-mcp-server. MIT.67GreatAuth: api key required

Verdict: choose Indraft for customer data platforms work over a hosted endpoint; choose Pipedrive MCP Server for customer data platforms as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Indraft logoChoose Indraft when

  • You need dedicated capabilities in the Customer Data Platforms domain.
  • You prefer a remote HTTP/SSE transport.
Explore Indraft

Pipedrive MCP Server logoChoose Pipedrive MCP Server when

  • You need dedicated capabilities in the Customer Data Platforms domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: PIPEDRIVE_API_KEY, PIPEDRIVE_MODE, PIPEDRIVE_ENABLE_DESTRUCTIVE, PIPEDRIVE_IMAGE_BASE_DIR.
  • You want tools like pipedrive_list_deals, pipedrive_get_deal, pipedrive_create_deal.
Explore Pipedrive MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecIndraft logoIndraftPipedrive MCP Server logoPipedrive MCP Server
CategoryCustomer Data PlatformsCustomer Data Platforms
Quality signal37/100 · Fair67/100 · Great
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsNone listedPIPEDRIVE_API_KEYPIPEDRIVE_MODEPIPEDRIVE_ENABLE_DESTRUCTIVEPIPEDRIVE_IMAGE_BASE_DIR
Verified ownerCommunity listingCommunity listing
GitHub stars010
Directory activity 1 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listed123

Tools & capabilities

Indraft tools

No tool names declared yet. Check the project README from the listing page.

Pipedrive MCP Server tools 123

  • pipedrive_list_dealsList deals from Pipedrive with optional filtering by owner, person, organization, pipeline, stage, or status. Returns paginated results.
  • pipedrive_get_dealGet detailed information about a specific deal by ID, including all standard and custom fields.
  • pipedrive_create_dealCreate a new deal in Pipedrive. Only title is required; all other fields are optional.
  • pipedrive_update_dealUpdate an existing deal in Pipedrive. Specify the deal ID and any fields to update.
  • pipedrive_search_dealsSearch for deals by text in title. Supports fuzzy matching by default.
  • pipedrive_list_deal_followersList all followers for a deal.
  • pipedrive_add_deal_followerAdd a follower to a deal.
  • pipedrive_get_deal_followers_changelogGet the followers changelog for a deal.
  • pipedrive_list_deal_productsList line-item products attached to a deal. Returns paginated results.
  • pipedrive_add_deal_productAttach a single product as a line item to a deal.
  • pipedrive_update_deal_productUpdate a line-item product attached to a deal. All body fields optional.
  • pipedrive_bulk_add_deal_productsBulk-add up to 100 line-item products to a deal in one request.
  • +111 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Indraft

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "indraft": {
      "url": "https://api.indraft.io/mcp"
    }
  }
}

Pipedrive MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ckalima-pipedrive-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@ckalima/pipedrive-mcp-server"
      ],
      "env": {
        "PIPEDRIVE_API_KEY": "YOUR_PIPEDRIVE_API_KEY_HERE",
        "PIPEDRIVE_MODE": "YOUR_PIPEDRIVE_MODE_HERE",
        "PIPEDRIVE_ENABLE_DESTRUCTIVE": "YOUR_PIPEDRIVE_ENABLE_DESTRUCTIVE_HERE",
        "PIPEDRIVE_IMAGE_BASE_DIR": "YOUR_PIPEDRIVE_IMAGE_BASE_DIR_HERE"
      }
    }
  }
}

Frequently asked questions

Indraft is categorized under Customer Data Platforms and uses a remote HTTP/SSE transport. Pipedrive MCP Server belongs to Customer Data Platforms and uses a local stdio subprocess. Pick Indraft for customer data platforms work and Pipedrive MCP Server for customer data platforms.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Indraft has no declared pricing — check the project's own site. Pipedrive MCP Server is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add indraft and ckalima-pipedrive-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Indraft has a quality signal of 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Pipedrive MCP Server has 67/100 (Great) with 5 views, 0 installs and 10 GitHub stars.