A
licenseB
qualityD
maintenanceConnects AI assistants like Claude to productivity tools such as Notion, Monday, Jira, and Slack via a remote MCP integration hub.
71
46
MIT
Salesforce AI Agent MCP Server
Related Servers
Alternatives to Salesforce AI Agent MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables 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.-
- AlicenseAqualityCmaintenanceEnables management of n8n workflows, executions, credentials, tags, and variables via MCP tools. Supports stdio, Claude Code, and Claude Web with optional Authentik OAuth.22MIT
- AlicenseAqualityCmaintenanceEnables Claude AI and other MCP clients to interact with Jira Server/Data Center through tools like listing issues, logging work, and updating issues, requiring user confirmation for write operations.8601MIT
- AlicenseAqualityBmaintenanceEnables Claude Code and Claude Desktop to manage ClickUp tasks, sprints, reports, workspace navigation, and docs through 25+ MCP tools.28MIT
- AlicenseNot gradedqualityCmaintenanceAggregates GitHub, GitLab, and Figma development tools via MCP, enabling file access, code search, and design inspection. Also supports executing standalone tasks with Claude Code or Codex CLI.7MIT
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 issues