Knit MCP
Visit ProjectConnect with 10 000+ business tools (HRIS, ATS, CRM, accounting, calendar, ticketing, and more).
Visit ProjectCategory
Tags
What is Knit MCP?
Knit MCP is a powerful platform that enables AI models to connect with 10,000+ business tools across various categories like HRIS, ATS, CRM, accounting, calendar, ticketing, and more through a standardized protocol.
How to use Knit MCP?
To use Knit MCP, follow these steps:
-
Find Tools: Discover and select tools from Knit's catalog by application, use case, entities, or operation type.
-
Create a Tools Package: Bundle selected tools together to form a package.
-
Create a Knit MCP Server: Configure your server with your tools package and necessary integrations.
-
Use Your Server: Connect your server to AI models using the appropriate authentication.
Here's a quick overview:
-
Search for relevant tools using the Knit tool finder API. Command:
curl <KNIT_ENDPOINT> --header 'Content-Type: application/json' --header 'Authorization: Bearer {YOUR_API_KEY}' --data '{ "filters": { "app_id": "hubspot", "usecase": "get leads" } }'
-
Create a tools package. Command:
curl <KNIT_ENDPOINT> --header 'Content-Type: application/json' --header 'Authorization: Bearer {YOUR_API_KEY}' --data '{ "name": "Sales test tools", "description": "Sales test tools", "tools": [ "hubspot__get_lead_details_by_id", "hubspot__get_read_a_page_of_leads", ] }'
-
Create an MCP server. Command:
curl <KNIT_ENDPOINT> --header 'Content-Type: application/json' --header 'Authorization: Bearer {YOUR_API_KEY}' --data '{ "pkgID": "<PACKAGE_ID>", "integrationIDs": [ { "appOrCategoryID": "hubspot", "integrationID": "<INTEGRATION_ID>" } ] }'
-
Use your MCP server:
- With Claude Desktop: Use the MCP Remote npm package by Cloudflare. Example Config:
{ "mcpServers": { "knit-mcp": { "command": "C:\\nvm4w\\nodejs\\node.exe", "args": [ "C:\\nvm4w\\nodejs\\node_modules\\npm\\bin\\npx-cli.js", "-y", "-p", "mcp-remote@0.0.22", "mcp-remote", "https://mcp.getknit.dev/sse", "--header", "Authorization:Bearer {YOUR_API_KEY}.{KNIT_MCP_SERVER_ID}" ] } } }
- With Claude Web: Use the secure server token generated during server creation.
Here's a video guide: https://www.loom.com/share/a5756093c9b846a2866f4354a6eba576?sid=60db267d-b2d2-481b-85d9-585ade6f683c
Key Features of Knit MCP
-
Cloud-hosted infrastructure
- Limitless scaling capabilities
- Robust authorization support via Bearer tokens
-
Consolidated API packaging
- Package APIs from different applications into a single server
- Create specialized AI agents (e.g., recruitment agent with ATS, Assessment, and Calendar APIs)
-
White-labeled embedded solution
- API-first approach for tools packaging and distribution
- Streamlined deployment for B2B workloads
-
Extensive tool ecosystem
- Access to 10,000+ business tools across multiple categories
Use Cases of Knit MCP
-
AI Agent Development: Build specialized AI agents by combining tools from different categories (e.g., recruitment, sales, project management).
-
Business Process Automation: Automate complex workflows by integrating tools from HRIS, CRM, accounting, and other systems.
-
Data Synchronization: Keep data consistent across multiple business applications.
-
Real-time Events: Implement event-driven integrations for various platforms.
-
Custom Solutions: Create tailored solutions by packaging specific tools for your business needs.
-
Cross-platform Integration: Connect tools from different ecosystems (e.g., HubSpot CRM with Google Calendar).
FAQ from Knit MCP
-
What is Model Context Protocol (MCP)?
MCP is a standardized protocol that enables AI models to access external tools and data through consistent interfaces.
-
What's the difference between STDIO and SSE MCP Servers?
STDIO servers run locally and have limited capabilities for production environments, while SSE servers are cloud-hosted solutions offering better security and scalability.
-
How do I authenticate requests to Knit MCP Server?
Authentication can be done through either separate headers (Authorization + X-KNIT-MCP-SERVER-ID) or a combined header (Authorization: Bearer {YOUR_API_KEY}.{KNIT_MCP_SERVER_ID}).
-
Can I use Knit MCP with other AI platforms?
While the documentation specifically mentions Claude, Knit MCP can potentially be used with other AI platforms that support MCP.
-
What kind of tools are available?
The platform offers access to over 10,000 tools across HRIS, ATS, CRM, accounting, calendar, meeting, ticketing, and many other business categories.
Knit MCP Server - Getting Started
===============
HomeGuidesAPI ReferenceChangelogDiscussions
v 1.0
Guides
v1.0HomeGuidesAPI ReferenceChangelogDiscussionsKnit MCP Server - Getting Started
Search
CTRL-K
All
Guides
Reference
Changelog
Discussions
Pages
Start typing to search…
Knit Basics
Getting started with Knit
Getting started with Syncs
Settings
App API Integration Guide
Getting started with Knit Communication APIs
- Setting up Slack Bot
- Settings up MS Teams Bot
- Slack event subscription
- Knit Markdown syntax for message formatting
- Sending plain text messages via Knit Communication APIs
- Build commands for your Bot powered by Knit
- Sending interactive message via Knit Communication APIs
App Implementation GUIDES
Real Time Events Guides
Knit MCP Server
AI Agents SDK
Knit MCP Server - Getting Started
A quick introduction to Knit's MCP Servers and how to get started with them.
Introduction to Model Context Protocol (MCP) Servers
Model Context Protocol (MCP) Servers enable AI models to access external tools and data through standardized interfaces. They serve as a bridge between language models and various APIs, allowing AI systems to perform tasks beyond their built-in capabilities. For more details on the Model Context Protocol, visit the official MCP documentation.
STDIO vs SSE MCP Servers: Understanding the Difference
STDIO MCP Servers
- Run locally on your machine
- Challenging to secure, deploy, and scale
- Currently the majority of servers being built use STDIO transport
- Limited for production business environments
SSE (Server-Sent Events) MCP Servers
- Cloud-hosted solution
- Offer superior security, scalability, and ease of deployment
- Better suited for production-grade business applications
Knit's MCP Server Solutions
Knit offers production-ready SSE transport-based servers with the following advantages:
Key Features
-
Cloud-hosted infrastructure
- Limitless scaling capabilities
- Robust authorization support (via Bearer tokens)
-
Consolidated API packaging
- Package APIs from different applications into a single server. No need to run multiple servers for different apps.
- Example: Build a recruitment agent by combining ATS, Assessment, and Calendar APIs
-
White-labeled embedded solution
- API-first approach for tools packaging and distribution
- Streamlined deployment for B2B workloads
-
Extensive tool ecosystem
- Access to 10,000+ tools across popular applications
- Categories include HRIS, ATS, CRM, Accounting, Calendar, Meeting, Ticketing, and more
Getting Started with Knit MCP Server
Setting up your Knit MCP Server involves a simple 4-step process:
- Find tools you want to include from Knit's extensive catalog
- Create a tools package that bundles your selected tools together
- Create a Knit MCP Server configured with your package and necessary integrations
- Use your server by connecting it to AI models using the proper authentication
Here's a quick about how you can quickly build your Knit MCP Server and use it with any popular MCP Client.
Let's explore these steps in detail:
1. Find Tools for Your Package
You can discover tools by application, use case, entities, or operation type. For more details on finding tools for your workloads, visit our find tools guide.
Click here to see this API's reference.
Example 1: Find tools by app and usecase
Bash
curl --location --request GET 'https://api.getknit.dev/v1.0/tools.find' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer {YOUR_API_KEY}' \
--data '{
"filters": {
"app_id": "hubspot",
"usecase": "get leads"
}
}'
JSON
{
"success": true,
"data": [
{
"tool_id": "hubspot__get_lead_details_by_id",
"entities": [
"lead",
"association",
"property"
],
"operation": "read",
"title": "Get Lead Details by ID",
"description": "This API endpoint retrieves details of a lead identified by the {leadsId}. The {leadsId} can be the internal object ID or any unique property value specified by the idProperty query parameter. The API allows filtering of returned properties using the properties query parameter and can include property history with propertiesWithHistory. It also supports retrieving associated object IDs with the associations parameter and can filter archived results using the archived parameter. The response includes lead details such as associations, creation and update timestamps, properties, and archived status.",
"is_unified_tool": false
},
{
"tool_id": "hubspot__post_create_a_lead",
"entities": [
"lead",
"association",
"property"
],
"operation": "write",
"title": "Create a Lead",
"description": "This API endpoint allows you to create a lead with specified properties and associations in HubSpot. The request requires an authorization header with a Bearer token and a content-type header set to application/json. The body of the request includes an array of associations and a properties object, which now includes 'hs_lead_name', 'hs_lead_type', and 'hs_lead_label'. The response returns a copy of the created lead object, including its ID, creation and update timestamps, and properties with history. If there is an error, a detailed error message is provided.",
"is_unified_tool": false
},
// Additional tools omitted for brevity
]
}
Example 2: Find unified API tools by category
Bash
curl --location --request GET 'https://api.getknit.dev/v1.0/tools.find' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer {YOUR_API_KEY}' \
--data '{
"filters": {
"category_id": "CALENDAR",
"include_unified_tools": true
}
}'
Sample Response:
JSON
{
"success": true,
"data": [
{
"tool_id": "unifiedcalendar__update-event",
"entities": null,
"operation": "write",
"title": "Update Calendar Event",
"description": "The Update Calendar Event API allows users to update an existing calendar event by providing the calendarId and eventId. Users can update details such as the event title, description, start and end times, attendees, and conferencing details. The API supports both all-day and recurring events. The response indicates whether the update was successful or provides an error message if it failed.",
"is_unified_tool": true
},
{
"tool_id": "unifiedcalendar__get-availability",
"entities": null,
"operation": "read",
"title": "Retrieve Available Common Time Slots for Multiple Attendees",
"description": "This API is used to retrieve available common time slots for multiple attendees within a specified time range. The request requires the start and end times in ISO 8601 UTC format, a list of attendee email addresses, and optionally the slot duration in minutes. The response includes a list of free time slots available for all attendees. Supported applications include Outlook Calendar and Google Calendar, with a restriction that the gap between start and end should be less than 62 days.",
"is_unified_tool": true
},
{
"tool_id": "unifiedcalendar__list-calendars",
"entities": null,
"operation": "read",
"title": "List Calendars API",
"description": "The List Calendars API retrieves all calendars associated with a user, including those they own and those shared with them. It supports apps like Outlook Calendar and Google Calendar. The API requires a 'pageSize' query parameter to control the size of results and an optional 'pageToken' to fetch additional records. The response includes details of each calendar such as id, name, description, timezone, owner information, colors, visibility, reminders, and more.",
"is_unified_tool": true
},
// Additional tools omitted for brevity
]
}
Save the relevant
tool_id
for creating a tools package in the next step.
2. Create a Tools Package
Now that you have searched for the tools you'd want to package, use the below curl to create a tool package to be used by your MCP Server.
In the below curl, name and description can be any arbitrary text you'd want to set. However, include the relevant tool_ids from the find tool result of the previous step in the tools array in request body as shown below.
Click here to see this API's reference.
Bash
curl --location --request POST 'https://api.getknit.dev/v1.0/tools.pkg.create' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer {YOUR_API_KEY}' \
--data '{
"name": "Sales test tools",
"description": "Sales test tools",
"tools": [
"hubspot__get_lead_details_by_id",
"hubspot__get_read_a_page_of_leads",
"hubspot__get_read_a_page_of_tasks",
"hubspot__post_read_batch_tasks",
"hubspot__get_task_details_by_task_id",
"hubspot__post_search_crm_tasks",
"unifiedcalendar__list-events",
"unifiedcalendar__delete-event",
"unifiedcalendar__get-event",
"unifiedcalendar__move-event",
"unifiedcalendar__update-event",
"unifiedcalendar__create-event",
"unifiedcalendar__respond-event"
]
}'
Sample Response:
JSON
{
"success": true,
"data": {
"orgID": "o_bdVS8xxx3TzqG9xxxXyN9",
"pkgID": "tp_l9oUkEqEBz7wcEswIJXGh2",
"tools": [
"unifiedcalendar__get-event",
"unifiedcalendar__update-event",
"hubspot__get_lead_details_by_id",
"unifiedcalendar__create-event",
"hubspot__get_task_details_by_task_id",
"hubspot__get_read_a_page_of_tasks",
"unifiedcalendar__move-event",
"unifiedcalendar__delete-event",
"hubspot__get_read_a_page_of_leads",
"hubspot__post_search_crm_tasks",
"unifiedcalendar__respond-event",
"hubspot__post_read_batch_tasks",
"unifiedcalendar__list-events"
],
"name": "Sales test tools",
"description": "Sales test tools",
"apps": [
"calendar",
"hubspot"
],
"updateAt": 1745660614190
}
}
Store the value of
pkgID
. You need it in the next step to create your MCP Server.
3. Create Knit's MCP Server for your tools package
Use the pkgID, generated in the previous step, and your user's integration IDs to create an MCP Server for your user.
❗️
You'd need to pass an active integration id for each unique tool set present in the tools package.
For example, in the above package, tools from Knit's unified CALENDAR category and Hubspot CRM app are being used. So, one active integration ID for calendar app and one for Hubspot need to be passed as shown in the curl command below.
See our getting started guide to understand what an Integration ID is and why it is important to have an Integration Id to make API calls on Knit.
Click here to see this API's reference.
Bash
curl --location --request POST 'https://api.getknit.dev/v1.0/mcp.server.create' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer {YOUR_API_KEY}' \
--data '{
"pkgID": "tp_MixTYxbEsnll...",
"integrationIDs": [
{
"appOrCategoryID": "hubspot",
"integrationID": "mg_MneXkY6pGG..."
},
{
"appOrCategoryID": "CALENDAR",
"integrationID": "mg_clntx8ZENs..."
}
]
}'
Sample Response:
JSON
{
"success": true,
"data": {
"mcpServerID": "dtp_4dapuVACbWQoUVBWKCmHYM",
"serverURL": "https://mcp.getknit.dev/sse",
"secureServerToken": "8dXXn5ZNIJWvIHW_i6TbFbg"
}
}
Store the value of
mcpServerID
. You need to pass this as a header value in the next step.
4. Using Your MCP Server
4.1 Knit MCP Server URL
Knit MCP Server is hosted on
https://mcp.getknit.dev/sse
. This is the endpoint you'll use when configuring any client to connect to Knit's MCP Server.
4.2 Authentication Headers
Knit's MCP Server authentication headers help with security, multi-tenancy, and logical separation of data and operations, which is essential for embedded integrations. You can choose either one of the following options to pass the headers to Knit's MCP server:
Option 1: Separate Headers
Authorization: Bearer {YOUR_API_KEY}
X-KNIT-MCP-SERVER-ID: {KNIT_MCP_SERVER_ID}
This approach separates your API key from the server identifier, providing clearer separation of authentication components.
Option 2: Combined Header
Authorization: Bearer {YOUR_API_KEY}.{KNIT_MCP_SERVER_ID}
This method combines both identifiers into a single header for simplified implementation.
📘
Replace
mcpServerID
(begins with "dtp"), generated in the previous step, with
{KNIT_MCP_SERVER_ID}
for creating your Knit MCP Server.
4.3 Using with Claude Desktop
Claude Desktop only supports STDIO servers by default. To use Knit's SSE-based MCP server with Claude Desktop, you'll need to use the MCP Remote npm package by Cloudflare. Your Claude MCP config JSON file should look like this:
Claude Desktop - Windows Configuration Example:
JSON
{
"mcpServers": {
"knit-mcp": {
"command": "C:\\nvm4w\\nodejs\\node.exe",
"args": [
"C:\\nvm4w\\nodejs\\node_modules\\npm\\bin\\npx-cli.js",
"-y",
"-p",
"mcp-remote@0.0.22",
"mcp-remote",
"https://mcp.getknit.dev/sse",
"--header",
"Authorization:Bearer {YOUR_API_KEY}.{KNIT_MCP_SERVER_ID}"
]
}
}
}
Important: On Windows, make sure to provide absolute paths for node.exe and npx-cli.js as shown in the example above.
_Note: Replace
{YOUR\_API\_KEY}
with your actual Knit API Key and
{KNIT\_MCP\_SERVER\_ID}
with your Knit MCP Server ID (generated in step 3)._
📘
How to get Knit API Key?
Sign up on Knit and complete the Getting Started journey for AI Agents Toolkit to get Knit's API Key.
4.3 Using with Claude Web
Claude web recently started supporting remote MCP servers. You can use the secure server token generated in Step 3 to connect to Knit remote MCP server on Claude web. Here's a video showing how that works.
Updated 5 days ago
Zoho Recruit Real Time EventsFinding Tools API Guide
Did this page help you?
Yes
No
- Table of Contents
-
* [Introduction to Model Context Protocol (MCP) Servers](https://developers.getknit.dev/docs/knit-mcp-server-getting-started#introduction-to-model-context-protocol-mcp-servers)
-
* [STDIO MCP Servers](https://developers.getknit.dev/docs/knit-mcp-server-getting-started#stdio-mcp-servers)
-
* [Key Features](https://developers.getknit.dev/docs/knit-mcp-server-getting-started#key-features)
-
* [1. Find Tools for Your Package](https://developers.getknit.dev/docs/knit-mcp-server-getting-started#1-find-tools-for-your-package)