--- title: "Knit - MCP Servers Salesforce" description: "Knit's Salesforce MCP Server gives your AI agents instant, code-free access to every Salesforce API endpoint-read, write, and automate without OAuth headaches or custom endpoints." source_url: "https://www.getknit.dev/mcp-servers/salesforce-mcp-server" page_type: "mcp-server" --- _This page is part of Knit's MCP server directory. It describes the Salesforce MCP Server, which gives AI agents direct, code-free access to the Salesforce API through Knit._ # Knit - MCP Servers Salesforce ## **Salesforce** MCP Server - Integrate your Agent with **Salesforce** in Minutes Knit's Salesforce MCP Server gives your AI agents instant, code-free access to every Salesforce API endpoint-read, write, and automate without OAuth headaches or custom endpoints. ### Installing Salesforce MCP Server Watch an agent automate workflows-all with knit's plug-and-play MCP Servers. ## 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 Salesforce MCP Server * Unified Action #### 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. * Unified Action #### 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. * Unified Action #### 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. * Unified Action #### 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. * Unified Action #### 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. * Unified Action #### 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. ## Related pages - [CRM MCP servers category](https://md.getknit.dev/mcp-servers-categories/crm-mcp-servers) - [Salesforce LLM Tools](https://md.getknit.dev/llm-tool/salesforce) - [Unified CRM API](https://md.getknit.dev/integration-categories/crm-api) - [How Knit works](https://md.getknit.dev/how-knit-works)