io.github.mmedum/pipedrive-mcp
io.github.mmedum/pipedrive-mcp
Is the io.github.mmedum/pipedrive-mcp MCP server down? No. It is up and needs network, probed 2026-11-06.
Pipedrive CRM as MCP tools: find deals, people and companies, and move deals through a pipeline.
needs network probed 2026-11-14 · unchanged since 2026-11-06
MCP error -32000: Connection closed time=2026-11-09T08:47:03.368Z level=WARN msg="pipedrive request failed" path=/api/v2/dealFields method=GET attempt=1 duratio
- Bundle
- https://github.com/mmedum/pipedrive-mcp/releases/download/v1.3.1/pipedrive-mcp_1.3.1.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
- Host
- github.com
- Repository
- https://github.com/mmedum/pipedrive-mcp
- Website
- https://github.com/mmedum/pipedrive-mcp#readme
- Registry
- active, updated 2026-11-05 · registry entry
Compare this server with others.
More servers
Other registry entries on github.com, the ones next to this name; all of them.
- io.github.mmedum/google-docs-mcp · alive
- Google Drive io.github.mmedum/google-drive-mcp · alive
- io.github.mmedum/google-mail-mcp · alive
- io.github.mmedum/google-sheets-mcp · alive
- Clipboard MCP io.github.mnardit/clipboard-mcp · install failed
- Mazarbul io.github.mo-cmyk/mazarbul · crashed on start
- rpfd io.github.molchalih/rpfd · alive
- Software Dock io.github.molidestroyer/software-dock · error
Servers that mention pipedrive.
- Pipedrive MCP by usefulapi io.usefulapi/pipedrive · timeout
- Pipedrive io.github.pipeworx-io/pipedrive · alive
- io.github.enzoemir1/leadpipe-mcp · no executable
- Pipedrive CRM io.github.ckalima/pipedrive-mcp-server · alive
- io.github.nubiia-dev/mcp-pipedrive · alive
- Pipedrive MCP io.github.Servosity/pipedrive-mcp · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server tries to reach the network on start. The probe runs in a container with the network off, so a server that connects lazily, on the first tool call, is measured.