---
title: "Freshworks"
url: "https://lb.getknit.dev/mcp-servers/freshworks/"
date: "2026-08-13T12:31:03+00:00"
modified: "2026-08-13T12:57:28+00:00"
type: "mcp_server"
---

# Freshworks

[MCP Servers](https://lb.getknit.dev/mcp-servers) / [CRM](https://lb.getknit.dev/mcp-servers-categories/crm-mcp-servers/) / Freshworks ![Freshworks](https://storage.googleapis.com/knit-website-media/2026/08/68279e0ca0c82e4990bf6394_Freshworks-1.svg)Freshworks MCP Server
=====================

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

 [See Docs](https://developers.getknit.dev/docs/getting-started-with-knit-mcp-server-for-ides-and-clis) [Set Up Freshworks CRM MCP Server](https://mcphub.getknit.dev/) 

 

  Building Integrations Together·![4.9 out of 5 stars](https://lb.getknit.dev/wp-content/themes/knit/assets/images/g2/g2-star-rating.svg)4.9/5 on G2·![Google](https://lb.getknit.dev/wp-content/themes/knit/assets/images/investor-logos/google-g.png)Google for Startups Accelerator

![prismforce](https://storage.googleapis.com/knit-website-media/2026/08/6a1eebbdaa38eb74c2d39fc9_prismforce-1.svg)![Hackerearth](https://storage.googleapis.com/knit-website-media/2026/08/6a1eeb591e00bd216f61488b_hackerearth-1.svg)![Isotopes AI](https://storage.googleapis.com/knit-website-media/2026/08/691596a13b8cd38e2f3dc822_isotopes_ai_greyscale-1.svg)![Infojobs](https://storage.googleapis.com/knit-website-media/2026/08/68fc54d2ee31fc7f0e2f7ce1_infojobs_bnw-1.svg)![Payoneer](https://storage.googleapis.com/knit-website-media/2026/08/payoneer.png)![Outsolve](https://storage.googleapis.com/knit-website-media/2026/08/683469796fef776e21802928_outsolve-1.svg)![Skuad](https://storage.googleapis.com/knit-website-media/2026/08/68346986ac834ab404bc57d8_Skuad-1.svg)![Payworks](https://storage.googleapis.com/knit-website-media/2026/08/6879e68c044e681ac17de2b8_payworks_logo-1.svg)![Itilite](https://storage.googleapis.com/knit-website-media/2026/08/itilite.svg)![Onsurity](https://storage.googleapis.com/knit-website-media/2026/08/onsurity.svg)![RazorpayX](https://storage.googleapis.com/knit-website-media/2026/08/razorpay.png)![Multiplier](https://storage.googleapis.com/knit-website-media/2026/08/multiplier.svg)![Peoplestrong](https://storage.googleapis.com/knit-website-media/2026/08/68346a01a0576f307fa7b51c_people-strong-1.svg)![Scrut](https://storage.googleapis.com/knit-website-media/2026/08/scrut.svg)![Ceipal](https://storage.googleapis.com/knit-website-media/2026/08/ceipal.svg)

 

  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.

![](https://lb.getknit.dev/wp-content/themes/knit/assets/images/mcp-features/serverless-deployment.svg)

### Serverless by Default

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

 

![](https://lb.getknit.dev/wp-content/themes/knit/assets/images/mcp-features/package-tools-across-apps.svg)

### Mix-and-Match Tool Bundles

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

 

![](https://lb.getknit.dev/wp-content/themes/knit/assets/images/mcp-features/bring-your-own-apis.svg)

### 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.

 

![](https://lb.getknit.dev/wp-content/themes/knit/assets/images/mcp-features/semantic-search.svg)

### Semantic Tool Search

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

 

![](https://lb.getknit.dev/wp-content/themes/knit/assets/images/mcp-features/dynamic-tool-loading.svg)

### Hot-Swap Tools at Runtime

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

 

![](https://lb.getknit.dev/wp-content/themes/knit/assets/images/mcp-features/managed-auth.svg)

### Auth Handled for You

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

 

 

 

  See It In Action
----------------

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

    

 

  Actions Available via Freshworks MCP Server
-------------------------------------------

Every action below is real and already live — not a roadmap item. [Browse the full API reference →](https://developers.getknit.dev/)

 Get CRM Deal Stages 

The Get CRM Deal Stages API retrieves the stages of deals in a CRM system. It requires an 'accept' header specifying 'application/json'. The response includes a success flag and data containing an array of stages, each with a stageId, stageName, pipelineId, and pipelineName. In case of an error, an error message is provided.

 

 Update CRM Custom Objects Schema 

The Update CRM Custom Objects Schema API allows users to update the schema of custom objects in the CRM system. The request requires headers specifying the content type as 'application/json'. The request body must include 'schemaId', 'title', 'titlePluralized', and 'description' as required fields. The response will indicate success with a boolean and may include data or an error message if unsuccessful.

 

 Create CRM Lead 

The Create CRM Lead API allows users to create a new lead in the CRM system. The API requires a POST request to the specified endpoint with headers specifying 'accept' and 'content-type' as 'application/json'. The request body should include details about the lead such as first name, last name, job title, company, description, owner information, industry, number of employees, and address details. The response will indicate success or failure of the operation, with a success flag and optional data or error message.

 

 Update CRM Account 

The Update CRM Account API allows users to update details of an existing CRM account. 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 accountId and owner details, and can optionally include other account details such as name, description, industry, website, number of employees, address, phone number, and custom fields. The response will indicate success or failure of the operation, with a success flag and optional data or error message.

 

 Create CRM Deal 

The Create CRM Deal API allows users to create a new deal in the CRM system. The API requires a POST request to the endpoint https://api.getknit.dev/v1.0/crm.deal.create with headers specifying 'accept' and 'content-type' as 'application/json'. The request body must include the 'name', 'owner', and 'stageId' fields, along with optional fields such as 'description', 'amount', 'currency', 'pipelineId', 'account', 'contact', and 'customFields'. The response will indicate success with a boolean and provide the ID of the created deal. In case of an error, a descriptive error message will be returned.

 

 Delete CRM Engagement 

The Delete CRM Engagement API allows users to delete a specific engagement from 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 'engagementId' and 'type' as required fields. On success, the API returns a response with 'success' set to true and 'data' as null. In case of an error, 'success' is false and an 'error' object with a descriptive message is returned.

 

 Create CRM Custom Object Record 

This API endpoint allows the creation of a CRM custom object record. It requires a POST request to the specified URL with headers 'accept' and 'content-type' set to 'application/json'. The request body must include 'schemaId', 'name', 'description', 'fields', and 'metadata'. The response will indicate success with a 'recordId' if successful, or an error message if not.

 

 List CRM Users 

The List CRM Users API endpoint retrieves a list of users from the CRM system. It requires an 'accept' header specifying 'application/json'. The response includes a 'success' boolean indicating the request status, and if successful, a 'data' object containing an array of 'users', each with 'email' and 'id'. If unsuccessful, an 'error' object with a 'msg' is returned.

 

 Update CRM Contact 

The Update CRM Contact API allows users to update the details of an existing contact 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 contactId of the contact to be updated, and can optionally include other fields such as firstName, lastName, email, industry, jobTitle, owner details, address, phoneNumber, account ID, and custom fields. The response will indicate success or failure of the operation, with a success flag and optional data or error message.

 

 Create CRM Contact 

The Create CRM Contact API allows users to create a new contact in the CRM system. The API requires a POST request to the specified endpoint with headers specifying 'accept' and 'content-type' as 'application/json'. The request body must include the contact's first name, last name, email, and owner information. Optional fields include industry, job title, address, phone number, account ID, and custom fields. The response will indicate success with the ID of the created contact or provide an error message if the operation fails.

 

 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.

 

 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.

 

 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.

 

 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.

 

 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.

 

 List CRM Fields 

The List CRM Fields API allows users to retrieve a list of fields for a specified CRM object type. The API requires a query parameter 'object' to specify the CRM object type such as 'account', 'contact', 'deal', 'lead', or 'engagement'. An optional 'subType' parameter can be used for CRMs where the engagement object is made up of sub-objects. The response includes a success flag and data containing mapped and unmapped fields with their IDs and labels.

 

 Create Custom Object Field in CRM 

This API endpoint allows the creation of a custom object field 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 'schemaId', 'fieldId', 'title', and 'type' as required fields, with 'metadata' being optional. The response will indicate success with the 'success' field and return the 'schemaId' and 'fieldId' in the 'data' object. In case of an error, the 'success' field will be false, and an 'error' object will provide a descriptive message.

 

 Delete CRM Custom Object Field 

This API endpoint is used to delete a field from a custom object in the CRM. It requires a POST request to the specified URL with headers specifying 'accept' and 'content-type' as 'application/json'. The request body must include 'schemaId' and 'fieldId' to identify the field to be deleted. On success, it 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.

 

 Delete CRM Custom Object Record 

This API endpoint deletes a record from a custom object in the CRM. It requires the schema ID and record ID as input in the request body. The response indicates whether the operation was successful. If successful, the response contains a success flag and null data. If unsuccessful, it contains an error message.

 

 Delete CRM Deal 

The Delete CRM Deal API allows users to delete a specific deal from the CRM system. The request requires the 'dealId' in the request body to identify which deal to delete. The request headers must include 'accept' and 'content-type' set to 'application/json'. A successful response will return a 'success' boolean set to true and 'data' as null. If the operation fails, 'success' will be false and an 'error' object with a descriptive message will be provided.

 

 Get CRM Custom Object Fields 

This API endpoint retrieves the fields of a custom object in a CRM system. It requires the schema ID as input in the request body. The response includes a success flag and a list of fields with details such as field ID, title, type, creation and update timestamps, description, and the IDs of the user who created and last updated the field. In case of an error, an error message is returned.

 

 Delete CRM Custom Object Schema 

This API endpoint deletes a CRM custom object schema identified by the provided schemaId. It requires the schemaId to be specified in the request body. The request must include headers specifying 'accept' and 'content-type' as 'application/json'. On success, it returns a response with 'success' set to true and 'data' as null. If an error occurs, 'success' is false and an 'error' object with a descriptive message is returned.

 

 Delete CRM Contact 

The Delete CRM Contact API allows users to delete a contact from the CRM system. It requires a POST request to the endpoint with a JSON body containing the 'contactId' of the contact to be deleted. The request headers must include 'accept' and 'content-type' set to 'application/json'. On success, the API returns a JSON response with 'success' set to true and 'data' as null. If an error occurs, 'success' is false and an 'error' object with a descriptive message is returned.

 

 Update CRM Custom Object Fields 

This API endpoint allows updating fields of custom objects in a 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 'schemaId', 'fieldId', 'title', and 'type' to specify the field to be updated and its new attributes. The response will indicate success with a boolean 'success' field and may include additional data or error information.

 

 Update CRM Engagement 

The Update CRM Engagement API allows users to update details of an existing CRM engagement. The API requires a POST request to the specified endpoint with headers 'accept' and 'content-type' set to 'application/json'. The request body must include the 'engagementId' as a required field, along with optional fields such as 'type', 'subject', 'direction', 'content', 'owner', 'startDateTime', 'endDateTime', and 'channel'. The response will indicate success with a boolean 'success' field and may include an error message if the operation fails.

 

 Update CRM Lead 

The Update CRM Lead API allows users to update the details of a lead 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 leadId, which is mandatory, and can optionally include other details such as firstName, lastName, jobTitle, company, description, owner information, industry, number of employees, and address details. The response will indicate success or failure of the operation, with a success flag and optional data or error message.

 

 Get CRM Custom Objects Schemas 

This API endpoint retrieves the schemas of custom objects in the CRM. It requires an 'accept' header with the value 'application/json'. The response includes a success flag and a data object containing an array of schema objects. Each schema object includes details such as schemaId, createdAt, updatedAt, title, titlePluralized, description, createdById, and updatedById. In case of an error, the response includes a success flag set to false and an error object with a descriptive message.

 

 Delete CRM Lead 

The Delete CRM Lead API allows users to delete a lead from the CRM system. It requires a POST request to the endpoint with the leadId in the request body. The request headers must include 'accept' and 'content-type' set to 'application/json'. On success, it 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.

 

 Update CRM Custom Object Record 

This API endpoint updates a CRM custom object record. It requires a POST request to the specified URL with headers 'accept' and 'content-type' set to 'application/json'. The request body must include 'schemaId', 'recordId', 'name', 'description', 'fields', and 'metadata'. The response will indicate success or failure, with an optional error message if the operation fails.

 

 [  Missing an action? 

Our AI Agent builds it instantly.

 Try Now  ](/products/integrations-agent/) 

 

  Knit vs. building a standalone Freshworks MCP Server
----------------------------------------------------

#### Building it yourself

- A custom MCP server for Freshworks, hosted and maintained in-house
- Handle Freshworks's OAuth, rate limits, and pagination yourself
- Re-test and patch every time Freshworks changes their API
- No tool search — every tool sits in your agent's context at once
- Engineering time spent on plumbing, not your product
- Weeks of dev time before you ship
 
 

#### With Knit

- Freshworks MCP Server already built, hosted, and maintained
- Knit handles Freshworks's OAuth, storage, and refresh for you
- Knit absorbs Freshworks's API changes — nothing breaks on your end
- Semantic tool search keeps agent context lean
- Your team ships your product, not integration plumbing
- Live in minutes, not weeks
 
 

 

 

 

  Other CRM MCP Servers
---------------------

 [ ![Close CRM](https://storage.googleapis.com/knit-website-media/2026/08/6826fbd53476ea323af285ba_Close20CRM-1.svg)### Close CRM

 ](https://lb.getknit.dev/mcp-servers/close-crm-mcp-server/) [ ![Hubspot](https://storage.googleapis.com/knit-website-media/2026/08/6826fd7f01313f70f3ea9c7f_Hubspot-1.svg)### HubSpot

 ](https://lb.getknit.dev/mcp-servers/hubspot-mcp-server/) [ ![Salesforce API](https://storage.googleapis.com/knit-website-media/2026/08/6826ff92689a6add2450324b_Salesforce-1.svg)### Salesforce

 ](https://lb.getknit.dev/mcp-servers/salesforce-mcp-server/) [ ![Salesflare CRM](https://storage.googleapis.com/knit-website-media/2026/08/6826ff81e6c11e2cd27a16a7_Salesflare20CRM-1.svg)### Salesflare CRM

 ](https://lb.getknit.dev/mcp-servers/salesflare-crm-mcp-server/) [ ![Pipedrive](https://storage.googleapis.com/knit-website-media/2026/08/6826ff1cecfd4b64130b6b93_Pipedrive-1.svg)### Pipedrive

 ](https://lb.getknit.dev/mcp-servers/pipedrive-mcp-server/) [ ![Zendesk Sell](https://storage.googleapis.com/knit-website-media/2026/08/68270097b7843483781579d3_Zendesk20Sell-1.svg)### Zendesk Sell

 ](https://lb.getknit.dev/mcp-servers/zendesk-sell-mcp-server/) [ ![Zoho CRM](https://storage.googleapis.com/knit-website-media/2026/08/682700b18ac502f067ad377d_Zoho20CRM-1.svg)### Zoho CRM

 ](https://lb.getknit.dev/mcp-servers/zoho-crm-mcp-server/) [ ![Pipeline CRM](https://storage.googleapis.com/knit-website-media/2026/08/6a2f0a04635d5e15f3cc699a_Pipeline20CRM-1.svg)### Pipeline CRM

 ](https://lb.getknit.dev/mcp-servers/pipeline-crm/) [ ![GoHighLevel](https://storage.googleapis.com/knit-website-media/2026/08/6a2f09497b5b07887565a0e4_GoHighLevel-1.svg)### GoHighLevel

 ](https://lb.getknit.dev/mcp-servers/gohighlevel/) 

 [See all CRM MCP Servers](https://lb.getknit.dev/mcp-servers-categories/crm-mcp-servers/)

 

  Real Use Cases for Freshworks
-----------------------------

See how teams put Freshworks to work as part of a bigger workflow.

 [### Integrations for Lead Sourcing and Enrichment

Deduplicate and cleanse leads, auto-assign leads based on enrichment fields.

 ](https://lb.getknit.dev/solutions/integrations-for-lead-sourcing-and-enrichment-platforms/) [### Integrations for AI SDRs and Sales agents

Power AI-driven outreach with real-time CRM data and calendar integrations.

 ](https://lb.getknit.dev/solutions/integrations-for-ai-sdr-platforms/) [### Integrations for Sales Engagement platforms

Knit gives you 100+ prebuilt CRM, ERP, and Ticketing connectors — so you can sell faster and onboard…

 ](https://lb.getknit.dev/solutions/integrations-for-sales-engagement-platforms/) 

 

  Enterprise-grade security
-------------------------

 ![SOC 2 certified](/wp-content/themes/knit/assets/images/security-logos/soc2.svg) ![GDPR compliant](/wp-content/themes/knit/assets/images/security-logos/gdpr.svg) ![ISO 27001 certified](/wp-content/themes/knit/assets/images/security-logos/iso.png) 

[Visit our Security Center](https://compliance.getknit.dev/) [Review the DPA](/dpa)

 

  Customer Stories
----------------

See how leading technology firms are scaling their operations

![Multiplier](https://storage.googleapis.com/knit-website-media/2026/08/multiplier.svg)[Case Study ](https://lb.getknit.dev/case-studies/multiplier-closes-enterprise-deals-by-shipping-a-workday-integration-in-one-week-through-knit/)

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

HHuynh H

Developer, Multiplier







![Scrut](https://storage.googleapis.com/knit-website-media/2026/08/scrut.svg)[Case Study ](https://lb.getknit.dev/case-studies/how-scrut-automation-automates-grc-automation-with-knits-unified-hris-api/)

> 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.

JJayesh

Co-Founder, Scrut







![Onsurity](https://storage.googleapis.com/knit-website-media/2026/08/onsurity.svg)

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

PPoorvi

Product Manager, Onsurity







![RazorpayX](https://storage.googleapis.com/knit-website-media/2026/08/razorpay.png)[Case Study ](https://lb.getknit.dev/case-studies/razorpayx-payroll-unlocks-multi-entity-pay-runs-with-knits-unified-hrms-api/)

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

AAditya

Product Lead, RazorpayXPayroll







![Payoneer](https://storage.googleapis.com/knit-website-media/2026/08/payoneer.png)[Case Study ](https://lb.getknit.dev/case-studies/payoneer-workforce-management-launches-a-global-hris-to-netsuite-bridge-for-clients-using-knits-unified-api/)

> Knit shipped a brand-new Timesheet API in a week and handed us a ready-to-use NetSuite sandbox. That velocity is priceless when you're running payroll in 40+ countries.

RRohit Singh

GM, Payoneer Workforce Management









 

  \#1 in Ease of Integrations
---------------------------

![4.9 out of 5 stars](/wp-content/themes/knit/assets/images/g2/g2-star-rating.svg)

4.9 out of 5 stars on G2

![G2 Leader, Spring 2026](/wp-content/themes/knit/assets/images/g2/g2-leader.svg)![G2 Fastest Implementation, Spring 2026](/wp-content/themes/knit/assets/images/g2/g2-fastest-implementation.svg)![G2 High Performer, Spring 2026](/wp-content/themes/knit/assets/images/g2/g2-high-performer.svg)![G2 Best Est. ROI, Spring 2026](/wp-content/themes/knit/assets/images/g2/g2-best-roi.svg)

 

   FAQCommon questions about the Freshworks MCP Server
------------------------------------------------

  Does Knit have an MCP Server for Freshworks out of the box?Yes — the Freshworks MCP Server is live and already built, not a roadmap item. It exposes Freshworks's real actions as AI-ready tools your agent can call directly.

   Does the Freshworks MCP Server support both reading and writing data?Yes. Its actions cover both reads and writes, so your agent can pull data from Freshworks and push updates back to it, not just query it.

   How does authentication work for the Freshworks MCP Server?Knit manages Freshworks's OAuth, credential storage, and refresh for you — there's no auth to configure yourself before your agent can start calling tools.

   What happens if Freshworks changes their API?Knit absorbs it. We maintain and update the Freshworks connector on our end, so the MCP Server keeps working without you tracking Freshworks's changelog.

   Do you store Freshworks data or customer PII?No. Knit acts as a stateless passthrough — data is processed on our application server and returned directly to your agent, without being stored on Knit's servers.

   What is the pricing model, and is there a free trial?You choose the model that fits your business — pricing based on integrated accounts, or based on API call volume. Every plan includes a 30-day free trial before billing starts.

   Can I use this as an LLM tool for function calling?Yes — this MCP server exposes Freshworks's actions as tools your AI agent can call directly, the same underlying capability previously offered as a standalone LLM Tool integration. MCP is the protocol; the tool-calling access is the same.

   Does this work with Claude, GPT, and other LLMs?Yes — any MCP-compatible client or agent framework can connect to this server and call its exposed actions, regardless of which underlying LLM is driving the agent.

  

[See all FAQs](/faq)

 

    From the blog
-------------

  [![Get Open Tickets from the Freshworks API Using Python](https://storage.googleapis.com/knit-website-media/2026/08/blog-banner-green-640x400.png)](https://lb.getknit.dev/blog/get-open-tickets-from-the-freshworks-api-using-python/)### [Get Open Tickets from the Freshworks API Using Python](https://lb.getknit.dev/blog/get-open-tickets-from-the-freshworks-api-using-python/)

Learn how to fetch open support tickets using the Freshworks API. Step-by-step guide covering authentication, endpoints, common pitfalls, FAQs, and best practices for production-ready integrations.

   [![Full list of Knit’s CRM API Guides](https://storage.googleapis.com/knit-website-media/2026/08/blog-banner-red-scaled-640x400.png)](https://lb.getknit.dev/blog/full-list-of-knits-crm-api-guides/)### [Full list of Knit’s CRM API Guides](https://lb.getknit.dev/blog/full-list-of-knits-crm-api-guides/)

This directory is a live list of all CRM API integration guides we have written at Knit. Use it to quickly find the guide related to the specific CRM APP you want to learn more about.

   [![Zendesk CRM API Directory](https://storage.googleapis.com/knit-website-media/2026/08/blog-banner-yellow-scaled-640x400.png)](https://lb.getknit.dev/blog/zendesk-crm-api-directory/)### [Zendesk CRM API Directory](https://lb.getknit.dev/blog/zendesk-crm-api-directory/)

Zendesk CRM API integration guide covering key features, endpoints, use cases, FAQs, and best practices to automate customer data, sales pipelines, and support workflows at scale.‍

  

 

  Put Integrations on Autopilot. Talk to Experts.
-----------------------------------------------

Knit is loved by customers across the globe due to our seamless product and white glove support. You'll love us too!

 [Talk to a Human](/book-demo)
