Backengine MCP vs Pipedrive MCP Server
A side-by-side look at the Backengine MCP 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.
Verdict: choose Backengine MCP 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?
Choose Backengine MCP when
- You need dedicated capabilities in the Customer Data Platforms domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
list_projects, get_project, get_project_overview.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Customer Data Platforms | Customer Data Platforms |
| Quality signal | 48/100 · Fair | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | PIPEDRIVE_API_KEYPIPEDRIVE_MODEPIPEDRIVE_ENABLE_DESTRUCTIVEPIPEDRIVE_IMAGE_BASE_DIR |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 10 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 10 | 123 |
| Full listing | View Backengine MCP | View Pipedrive MCP Server |
Tools & capabilities
Backengine MCP tools 10
list_projectsList customers and prospects; filter by name, type, etc.get_projectRetrieve a customer or prospect, optionally with its overview.get_project_overviewPre-computed rolling 12-week summary for a customer or prospect.list_signalsList signals (categorized moments); filter by project, role, and time.find_similar_signalsSemantic search across signals from a natural-language query.list_sourcesList sources — transcripts, emails, Slack threads, and tickets.get_sourceRetrieve a source's content (summary, verbatim, or metadata only).list_rolesList the perspective lenses (e.g. product, sales, CS) used to filter signals.find_contactsFind contacts by name, email, job title, or project.list_signal_speakersList who has been speaking across signals.
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.
Backengine MCP
{
"mcpServers": {
"backengine-mcp": {
"url": "https://backengine-prod.backengine.ai/mcp"
}
}
}
Pipedrive MCP Server
{
"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
Backengine MCP 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 Backengine MCP 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.
Backengine MCP 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 backengine-mcp and ckalima-pipedrive-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Backengine MCP has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. Pipedrive MCP Server has 67/100 (Great) with 5 views, 0 installs and 10 GitHub stars.