Skip to main content
Glama
Sign In
Salesforce AI Agent MCP Server

Salesforce AI Agent MCP Server

by pratapsfdc22-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Salesforce AI Agent MCP Server

No user-submitted related servers found.

    Related Servers

    • jira-mcp

      ishaqashraf
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects Claude Code and other MCP clients to Jira Cloud, enabling AI agents to search issues with JQL, read issue details and comments, create Tasks, Bugs, or Stories, and add comments in a single workflow.
      876 npm
      MIT

    • Forja MCP Server

      gilsonfiho
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes specialized agents as MCP tools so users can manage and triage Jira tasks, analyze repositories for health and conventions, generate commit/PR/DevOps patterns, assemble reports, produce slides and infographics, and run semantic search over a knowledge base. Everything is invokable directly from inside a coding session in Claude Code, Cursor, or Claude Desktop.
      1
      MIT

    • Jira JQL Tool

      amiralamox
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to interact with Jira through JQL (Jira Query Language) queries using the Model Control Protocol, allowing natural language access to Jira issue tracking and project management.
      -

    • n8n MCP Server

      andhit-r
      A
      license
      A
      quality
      C
      maintenance
      Enables management of n8n workflows, executions, credentials, tags, and variables via MCP tools. Supports stdio, Claude Code, and Claude Web with optional Authentik OAuth.
      22
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct action on a specific resource: Jira stories, Salesforce metadata/objects, and n8n workflows. There is no overlap between tools like get_deployment_status and get_execution_status because they operate on different systems.

    Naming Consistency5/5

    All tool names follow a consistent pattern of domain_verb_noun (e.g., jira_get_story, salesforce_create_custom_field, n8n_trigger_workflow). Even salesforce_query fits, as 'query' functions as both verb and noun without breaking the convention.

    Tool Count5/5

    The 12 tools are well-scoped for a cross-platform integration server covering Jira, Salesforce, and n8n. Each tool serves a clear purpose with no redundancy, so the count feels appropriate for the domain.

    Completeness4/5

    The tool surface covers the core workflow: fetching Jira stories, searching, commenting, modifying Salesforce metadata, deploying, and triggering/polling n8n workflows. Minor gaps exist, such as no update/delete for validation rules or custom fields, but the main lifecycle is adequately covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources