MCP server intelligence profile

Salesforce AI Agent MCP Server

Enables Claude to interact with Jira, Salesforce, and n8n through MCP tools, allowing automated reading of Jira stories, deploying Salesforce metadata, and triggering n8n workflows

Local Onlypratapsfdc22-dev
Awaiting current scanNpm · 1.0.0

The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.

1Distribution channel
12Independently observed tools
0Linked remote endpoints
AvailableVersion intelligence

Detailed security scan evidence is not public for this MCP yet. Public identity, registry metadata, and independently observed protocol inventory remain available.

Install and connect

Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.

Install salesforce-ai-agent-mcp from npm

Version 1.0.0 declares 1 executable entrypoint.

npm install --save-exact salesforce-ai-agent-mcp@1.0.0
npx -y -p salesforce-ai-agent-mcp@1.0.0 salesforce-ai-agent-mcp
MCP client configuration example
{
  "mcpServers": {
    "salesforce-ai-agent-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "salesforce-ai-agent-mcp@1.0.0",
        "salesforce-ai-agent-mcp"
      ]
    }
  }
}

Identity

Canonical slugsalesforce-ai-agent-mcp-server-6141ad07DeploymentLocal Only
Canonical packagenpm:salesforce-ai-agent-mcpRepositorypratapsfdc22-dev/salesforce-ai-agent-mcp
First published—Latest release—
Last security verification—Classification confidence90%
PublicationDraftOfficial distributionNot verified

Distributions

ChannelIdentifierCurrent versionVersionsSource
npmsalesforce-ai-agent-mcp1.0.01Repository

Current release

PackageVersionPublished / observedInventorySecurity scan
npmsalesforce-ai-agent-mcp1.0.0CurrentSep 5, 202612 toolsSucceeded · 0 resources · 0 promptsEvidence restricted
Enterprise protection

Continuously monitor this MCP for security risk

Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.

  • Independent exact-version security scans
  • Continuous release and vulnerability monitoring
  • Risk-change alerts with capability context
  • Historical evidence and API exports
Custom pricingContact salesTailored to your organization, integrations, data needs, and support requirements.

Current version evidence

No public current-version evidence is available yet.

Current protocol inventory

2025-06-18Negotiated protocol
salesforce-ai-agent-mcpServer-reported name
1Capability groups
Aug 22, 2026Observed

Tools 12

ToolCategoryAnnotationsRisk
jira_get_storyFetch a Jira story by issue key. Returns summary, description, acceptance criteria, status, labels, assignee, and all custom fields.
Input schema
{
  "type": "object",
  "properties": {
    "issueKey": {
      "type": "string",
      "minLength": 1,
      "description": "Jira issue key in the format PROJECT-NNN (e.g. SFDC-123)"
    }
  },
  "required": [
    "issueKey"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
jira_post_commentPost a comment to a Jira story. Used by the AI agent to document deployment results, ask for clarification, or provide status updates. Supports plain text with paragraphs separated by blank lines.
Input schema
{
  "type": "object",
  "properties": {
    "issueKey": {
      "type": "string",
      "minLength": 1,
      "description": "Jira issue key (e.g. SFDC-123)"
    },
    "body": {
      "type": "string",
      "minLength": 1,
      "description": "Comment text. Use double newlines to separate paragraphs. Supports plain text — rich formatting will be preserved as ADF."
    }
  },
  "required": [
    "issueKey",
    "body"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
jira_search_storiesSearch Jira stories using JQL (Jira Query Language). Returns matching issues with full details. Example JQL: 'label = "sf-config" AND status = "To Do" AND project = SFDC ORDER BY created DESC'
Input schema
{
  "type": "object",
  "properties": {
    "jql": {
      "type": "string",
      "minLength": 1,
      "description": "JQL query string. Examples: 'project = SFDC AND status = \"To Do\"', 'label = \"sf-config\" AND assignee = currentUser()', 'issuetype = Story AND sprint in openSprints()'"
    },
    "maxResults": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "default": 50,
      "description": "Maximum number of results to return (1–100, default 50)"
    },
    "startAt": {
      "type": "integer",
      "minimum": 0,
      "default": 0,
      "description": "Zero-based offset for pagination (default 0)"
    }
  },
  "required": [
    "jql"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
jira_update_story_statusTransition a Jira story to a new status. The available transitions depend on the current workflow configuration. Common statuses: 'To Do', 'In Progress', 'In Review', 'Done', 'Blocked'.
Input schema
{
  "type": "object",
  "properties": {
    "issueKey": {
      "type": "string",
      "minLength": 1,
      "description": "Jira issue key (e.g. SFDC-123)"
    },
    "targetStatus": {
      "type": "string",
      "minLength": 1,
      "description": "The target workflow status name (e.g. 'In Progress', 'Done', 'Blocked'). Must match an available transition exactly."
    }
  },
  "required": [
    "issueKey",
    "targetStatus"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
n8n_get_execution_statusRetrieve the current status and output data of an n8n workflow execution by its execution ID. Use this to poll whether a triggered workflow has completed successfully.
Input schema
{
  "type": "object",
  "properties": {
    "executionId": {
      "type": "string",
      "minLength": 1,
      "description": "The n8n execution ID returned by n8n_trigger_workflow or found in the n8n Executions panel"
    }
  },
  "required": [
    "executionId"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
n8n_trigger_workflowTrigger a specific n8n workflow by its webhook URL, passing a JSON payload. This enables Claude to kick off the full Salesforce automation pipeline — for example, by sending a Jira issue key to start the analysis and deployment workflow.
Input schema
{
  "type": "object",
  "properties": {
    "webhookUrl": {
      "type": "string",
      "format": "uri",
      "description": "The full n8n webhook URL for the workflow (e.g. https://your-n8n.com/webhook/abc123). Obtain this from the Webhook trigger node in your n8n workflow."
    },
    "payload": {
      "type": "object",
      "additionalProperties": {},
      "description": "JSON payload to send to the webhook. Structure depends on what the n8n workflow expects. For the Salesforce AI Agent pipeline, include fields like: { issueKey, projectKey, environment, triggeredBy }"
    },
    "waitForResponse": {
      "type": "boolean",
      "default": false,
      "description": "If true, the tool waits for a synchronous response from the webhook. If false (default), it fires-and-forgets and returns immediately. Set to true only for workflows configured with 'Respond to Webhook' node."
    }
  },
  "required": [
    "webhookUrl",
    "payload"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
salesforce_create_custom_fieldCreate a custom field on a Salesforce object using the Tooling API. Supports all standard field types including Text, Number, Picklist, Checkbox, Date, Lookup, and more.
Input schema
{
  "type": "object",
  "properties": {
    "objectName": {
      "type": "string",
      "minLength": 1,
      "description": "Salesforce object API name (e.g. 'Account', 'My_Object__c')"
    },
    "fieldLabel": {
      "type": "string",
      "minLength": 1,
      "description": "Human-readable field label (e.g. 'Customer Tier')"
    },
    "fieldApiName": {
      "type": "string",
      "minLength": 1,
      "description": "Field API name without the __c suffix (e.g. 'Customer_Tier'). The __c suffix will be added automatically."
    },
    "fieldType": {
      "type": "string",
      "enum": [
        "Text",
        "Number",
        "Currency",
        "Picklist",
        "MultiSelectPicklist",
        "Checkbox",
        "Date",
        "DateTime",
        "Email",
        "Phone",
        "URL",
        "TextArea",
        "LongTextArea",
        "RichTextArea",
        "Lookup",
        "MasterDetail",
        "Percent",
        "AutoNumber",
        "Formula"
      ],
      "description": "Salesforce field type. One of: Text, Number, Currency, Picklist, MultiSelectPicklist, Checkbox, Date, DateTime, Email, Phone, URL, TextArea, LongTextArea, RichTextArea, Lookup, MasterDetail, Percent, AutoNumber, Formula"
    },
    "length": {
      "type": "integer",
      "minimum": 1,
      "maximum": 131072,
      "description": "Field length. For Text: 1–255 (default 255). For LongTextArea/RichTextArea: up to 131072 (default 32768). Not used for Date, Checkbox, etc."
    },
    "precision": {
      "type": "integer",
      "minimum": 1,
      "maximum": 18,
      "description": "Total number of digits for Number/Currency/Percent fields (default 18)"
    },
    "scale": {
      "type": "integer",
      "minimum": 0,
      "maximum": 17,
      "description": "Number of decimal places for Number/Currency/Percent fields (default 0)"
    },
    "required": {
      "type": "boolean",
      "description": "Whether the field is required (default false)"
    },
    "unique": {
      "type": "boolean",
      "description": "Whether the field value must be unique (default false)"
    },
    "description": {
      "type": "string",
      "description": "Internal description of the field's purpose"
    },
    "inlineHelpText": {
      "type": "string",
      "description": "Help text shown to users in the UI"
    },
    "defaultValue": {
      "type": "string",
      "description": "Default value for the field. For AutoNumber fields, this sets the display format (e.g. 'CASE-{000000}')"
    },
    "referenceTo": {
      "type": "string",
      "description": "Target object API name for Lookup or MasterDetail fields (e.g. 'Account', 'My_Object__c'). Required for Lookup/MasterDetail types."
    },
    "relationshipName": {
      "type": "string",
      "description": "Relationship name for Lookup/MasterDetail fields. Auto-generated if not provided."
    },
    "picklistValues": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "List of picklist values for Picklist or MultiSelectPicklist fields (e.g. ['High', 'Medium', 'Low'])"
    },
    "formula": {
      "type": "string",
      "description": "Formula expression for Formula fields"
    },
    "visibleLines": {
      "type": "integer",
      "minimum": 2,
      "maximum": 50,
      "description": "Number of visible lines for LongTextArea/RichTextArea fields (default 5)"
    }
  },
  "required": [
    "objectName",
    "fieldLabel",
    "fieldApiName",
    "fieldType"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
salesforce_create_validation_ruleCreate a validation rule on a Salesforce object using the Tooling API. The rule evaluates an error condition formula and displays an error message when the formula returns true.
Input schema
{
  "type": "object",
  "properties": {
    "objectName": {
      "type": "string",
      "minLength": 1,
      "description": "Salesforce object API name (e.g. 'Account', 'My_Object__c')"
    },
    "ruleName": {
      "type": "string",
      "minLength": 1,
      "pattern": "^[A-Za-z][A-Za-z0-9_]*$",
      "description": "API name for the validation rule (no spaces, e.g. 'Require_Phone_For_Hot_Leads')"
    },
    "errorConditionFormula": {
      "type": "string",
      "minLength": 1,
      "description": "Salesforce formula that evaluates to TRUE when the record should be invalid. Example: 'AND(Rating = \"Hot\", ISBLANK(Phone))'"
    },
    "errorMessage": {
      "type": "string",
      "minLength": 1,
      "description": "Error message shown to users when validation fails (e.g. 'Phone is required for Hot leads')"
    },
    "description": {
      "type": "string",
      "description": "Internal description of the rule's purpose"
    },
    "errorDisplayField": {
      "type": "string",
      "description": "API name of the field where the error should appear. If omitted, the error appears at the top of the page."
    },
    "active": {
      "type": "boolean",
      "default": true,
      "description": "Whether the rule should be active after creation (default true)"
    }
  },
  "required": [
    "objectName",
    "ruleName",
    "errorConditionFormula",
    "errorMessage"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
salesforce_deploy_metadataTrigger a Salesforce metadata deployment using the Metadata API. The metadata must be provided as a base64-encoded ZIP file containing a standard Salesforce metadata package.
Input schema
{
  "type": "object",
  "properties": {
    "zipFile": {
      "type": "string",
      "minLength": 1,
      "description": "Base64-encoded ZIP file containing the Salesforce metadata package. Must include package.xml and the appropriate metadata folders."
    },
    "checkOnly": {
      "type": "boolean",
      "default": false,
      "description": "If true, validates the deployment without making changes (dry run). Default false."
    },
    "testLevel": {
      "type": "string",
      "enum": [
        "NoTestRun",
        "RunSpecifiedTests",
        "RunLocalTests",
        "RunAllTestsInOrg"
      ],
      "default": "NoTestRun",
      "description": "Test execution level. Use 'RunLocalTests' or 'RunAllTestsInOrg' for production deployments."
    },
    "runTests": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Specific test class names to run when testLevel is 'RunSpecifiedTests'"
    },
    "rollbackOnError": {
      "type": "boolean",
      "default": true,
      "description": "Roll back all changes if any component fails (default true)"
    },
    "ignoreWarnings": {
      "type": "boolean",
      "default": false,
      "description": "Allow deployment to succeed with warnings (default false)"
    }
  },
  "required": [
    "zipFile"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
salesforce_get_deployment_statusPoll the status of a Salesforce metadata deployment by its deployment ID. Returns component counts, errors, and test results.
Input schema
{
  "type": "object",
  "properties": {
    "deploymentId": {
      "type": "string",
      "minLength": 1,
      "description": "The deployment ID returned by salesforce_deploy_metadata (18-character Salesforce ID)"
    }
  },
  "required": [
    "deploymentId"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
salesforce_get_object_fieldsQuery all existing fields on a Salesforce object using the REST API describe endpoint. Returns field names, labels, types, lengths, and picklist values.
Input schema
{
  "type": "object",
  "properties": {
    "objectName": {
      "type": "string",
      "minLength": 1,
      "description": "Salesforce object API name (e.g. 'Account', 'Contact', 'Opportunity', 'My_Custom_Object__c')"
    }
  },
  "required": [
    "objectName"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
salesforce_queryExecute a SOQL query against Salesforce and return the results. Use this to verify field values after deployment, check existing records, or validate configuration.
Input schema
{
  "type": "object",
  "properties": {
    "soql": {
      "type": "string",
      "minLength": 1,
      "description": "SOQL query string. Example: 'SELECT Id, Name, Rating, Phone FROM Account WHERE Rating = \\'Hot\\' LIMIT 10'"
    },
    "maxRecords": {
      "type": "integer",
      "minimum": 1,
      "maximum": 2000,
      "description": "Maximum records to return (1–2000). Use LIMIT in your SOQL for precise control. Default: returns whatever SOQL specifies."
    }
  },
  "required": [
    "soql"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——

Resources 0

  • None observed.

Resource templates 0

  • None observed.

Prompts 0

  • None observed.

Remote endpoints

EndpointTransportAuthenticationHealthObserved
No verified remote endpoint is linked.

Salesforce AI Agent MCP Server questions

How do I install Salesforce AI Agent MCP Server?

Install the selected package version with: npm install --save-exact salesforce-ai-agent-mcp@1.0.0

What tools does Salesforce AI Agent MCP Server provide?

Salesforce AI Agent MCP Server exposed 12 tools during independent protocol observation, including jira_get_story, jira_post_comment, jira_search_stories, jira_update_story_status, n8n_get_execution_status, n8n_trigger_workflow, salesforce_create_custom_field, salesforce_create_validation_rule, and others.

Is Salesforce AI Agent MCP Server secure?

The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.

Company and product intelligence

These internal links are derived from strong identity fields such as the implementation name, package, repository, vendor, and listing name—not generic description prose.

Associated company landscape

Salesforce intelligence →

Association is based on retained identity fields; it does not by itself prove first-party publication.

Salesforce 107 matches

Explore related MCP server guides

Curated product and capability guides containing this catalog record.

Official vs Community MCP Servers

Let’s talk about MCP security.

Share your details and our security team will contact you.