Pipedrive MCP Server - Integrate your Agent with Pipedrive in Minutes

Knit's Pipedrive MCP Server gives your AI agents instant, code-free access to every Pipedrive API endpoint-read, write, and automate without OAuth headaches or custom endpoints.

Installing

Pipedrive

MCP Server

Watch an agent automate workflows-all with knit's plug-and-play MCP Servers.

MCP Servers thumbnail

Key Features

All the power of AI-ready tools-serverless hosting, mix-and-match APIs, live updates, semantic search, and built-in auth-in a single, plug-and-play platform.

Serverless by Default

Spin up MCP Servers with zero infrastructure-Knit scales, patches, and monitors everything for you.

Plug-In Your Own APIs

Expose custom endpoints as AI-ready tools alongside knit's catalog, unifying proprietary logic and third-party apps in one place.

Hot-Swap Tools at Runtime

Add or remove tools without downtime; your agents see new capabilities instantly-no server restarts required.

Mix-and-Match Tool Bundles

Deploy only the API tools you need from any app in a single lightweight server-no bloat, no duplication.

Semantic Tool Search

Natural-language search surfaces the right tools for each use case, shrinking token costs and boosting LLM accuracy.

Auth Handled for You

OAuth, SAML, service accounts-Knit manages credentials and refreshes so your team never wrestles with tokens.

Actions available via

Pipedrive

MCP Server

  • Unified Action

Create CRM Engagement

The Create CRM Engagement API allows users to create a new engagement in the CRM system. The API requires a POST request to the endpoint with headers specifying 'accept' and 'content-type' as 'application/json'. The request body must include details such as the type of engagement (CALL, MEETING, EMAIL, etc.), subject, direction (INBOUND or OUTBOUND), content, owner details (id and email), start and end date-time, channel for communication, custom fields, and metadata. The response will indicate success with a boolean and may include data or an error message if the request fails.

Read more

  • Unified Action

Create CRM Account

The Create CRM Account API allows users to create a new account in the CRM system. It requires a POST request to the endpoint https://api.getknit.dev/v1.0/crm.account.create with headers specifying 'accept' and 'content-type' as 'application/json'. The request body must include the account's name and owner details, and can optionally include additional information such as description, industry, website, number of employees, address, phone number, and custom fields. The response will indicate success and provide the ID of the created account, or an error message if the request fails.

Read more

  • Unified Action

Create CRM Custom Object Schema

This API endpoint allows the creation of a custom object schema in the CRM system. It requires a POST request to the specified URL with headers 'accept' and 'content-type' set to 'application/json'. The request body must include the schemaId, title, titlePluralized, description, fields, and metadata. The response will indicate success with a boolean and return the schemaId if successful. In case of an error, a descriptive error message will be provided.

Read more

  • Unified Action

Delete CRM Account

The Delete CRM Account API allows users to delete a CRM account by providing the account ID. The request is made using the POST method to the endpoint https://api.getknit.dev/v1.0/crm.account.delete. The request headers must include 'accept' and 'content-type' both set to 'application/json'. The request body must contain the 'accountId' of the account to be deleted. On success, the API returns a response with 'success' set to true and 'data' as null. If there is an error, 'success' is false and an 'error' object with a descriptive message is returned.

Read more

  • Unified Action

Update CRM Deal

The Update CRM Deal API allows users to update the details of an existing deal in the CRM system. The API requires a POST request to the specified endpoint with headers indicating the content type as application/json. The request body must include the 'dealId' as a required field, along with optional fields such as 'name', 'description', 'amount', 'currency', 'owner', 'stageId', 'pipelineId', 'account', 'contact', and 'customFields'. The response will indicate success with a boolean value and may include additional data or an error message if the operation fails.

Read more

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Other

CRM MCP Servers

we support

Non sed sit aliquet iaculis turpis eget sed netus suspendisse ac vel dolor vitae et cursus nibh rhoncus et mauris nibh.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Check Circle
Request Successfully Placed

We’ll let you know as soon as this app is available

Oops! Something went wrong while submitting the form.
Close Icon

Customer Stories

See how leading technology firms are scaling their operations and driving measurable growth using Knit

“Amazing Product With Exceptional Support from the team. By using Knit we managed to speed up our development by orders of magnitude.”

Huynh H

Developer

Multiplier

“A brilliant tool to let you seamlessly integrate with many different systems. It is very easy to integrate with and customer support is next level.”

Jayesh

Co-Founder

“Seamless integration experience. Well-documented, self-explanatory APIs, and excellent service and support.”

Poorvi

Product Manager

“Easy to integrate. Knit's dashboard is intuitive for setting up and testing integrations, and the sandbox is extremely useful during development.”

Aditya

Product Lead

“Adding integrations has never been easier. Knit has been a game-changer for our team, enabling effortless custom workflows across Slack, HubSpot, Xero, and more.”

Shreelekha S

Content

#1 in Ease of Integrations

g2-logo

4.9 out of 5 stars on G2

g2-logo

4.9 out of 5 stars on G2

Put Integrations on Autopilot. Talk to Experts.

Ready to Get Started?
Try for Free today

Pipedrive

MCP Server FAQ’s