A complete reference for architects and procurement teams. Every major enterprise platform mapped against Claude's four integration paths: native connector, MCP server, Cowork plugin, and direct API.
Salesforce, HubSpot, and modern CRM platforms connect to Claude for lead scoring, deal analysis, email generation, and pipeline intelligence. The depth of integration depends on your chosen path.
| Tool | Native | MCP | Cowork Plugin | Direct API | 3rd Party | Notes |
|---|---|---|---|---|---|---|
Salesforce CRM / Sales Cloud | — | ✓ MCP | ✓ Plugin | ✓ API | ✓ Make/Zapier | MCP server reads/writes records. Cowork plugin pulls opportunity context. See our Salesforce integration guide. |
HubSpot CRM / Marketing Hub | — | ✓ MCP | ✓ Plugin | ✓ API | ✓ Zapier | Read/write contacts, deals, emails. Strong for marketing automation pipelines. |
Pipedrive CRM / Pipeline | — | ✓ Community MCP | — | ✓ API | ✓ Zapier | Community MCP server available. Best via direct API for complex workflows. |
Microsoft Dynamics 365 CRM / ERP | — | ✓ Community MCP | — | ✓ API | ✓ Power Automate | Power Automate provides deep native-feeling integration for M365 shops. |
Outreach / Salesloft Sales Engagement | — | — | — | ✓ API | ✓ Zapier | Typically integrate via webhook triggers to Claude API for email personalisation. |
Slack, Teams, Notion, and Google Workspace are the most requested integrations. Claude Cowork has native connectors for most; MCP servers handle the rest.
| Tool | Native | MCP | Cowork Plugin | Direct API | 3rd Party | Notes |
|---|---|---|---|---|---|---|
Slack Team Messaging | ✓ Claude for Slack | ✓ MCP | ✓ Connector | ✓ API | ✓ Zapier | Deep native integration via Claude for Slack. See Slack guide. |
Microsoft Teams Team Collaboration | — | ✓ MCP | ✓ Connector | ✓ API | ✓ Power Automate | Bot framework + API most common. See our Teams guide. |
Google Workspace Docs, Gmail, Drive, Sheets | — | ✓ MCP | ✓ Connector | ✓ API | ✓ Zapier/Make | Cowork connector reads Drive files. Gmail drafting common via API. See Workspace guide. |
Notion Knowledge Base / Docs | — | ✓ Official MCP | ✓ Connector | ✓ API | ✓ Zapier | Anthropic-published official Notion MCP. Read/write pages, databases. See Notion guide. |
Confluence Knowledge Management | — | ✓ Community MCP | ✓ Connector | ✓ API | ✓ Make | Read pages for RAG context, write summaries back. |
SharePoint / OneDrive Document Management | — | ✓ Community MCP | ✓ Connector | ✓ API | ✓ Power Automate | Key for M365-heavy enterprises. SharePoint MCP enables document-aware agents. |
Claude Code has native GitHub integration. Other dev tools connect via MCP or direct API — critical for code review pipelines, incident response, and automated documentation.
| Tool | Native | MCP | Cowork Plugin | Direct API | 3rd Party | Notes |
|---|---|---|---|---|---|---|
GitHub Code / DevOps | ✓ Claude Code Native | ✓ Official MCP | — | ✓ API | ✓ Actions | Deepest integration of any dev tool. PR reviews, Actions pipelines, MCP for code context. See GitHub guide. |
GitLab Code / CI/CD | — | ✓ Community MCP | — | ✓ API | ✓ CI Webhooks | CI/CD webhook to Claude API for automated review comments. MCP for repo search. |
Jira Project Management | — | ✓ Official MCP | ✓ Connector | ✓ API | ✓ Zapier | Anthropic-published official Jira MCP. Create, read, update issues. See Jira guide. |
PagerDuty Incident Management | — | ✓ Community MCP | — | ✓ API | ✓ Webhooks | Incident triage automation: PagerDuty alert → Claude analysis → runbook suggestion. |
Datadog / Splunk Observability | — | ✓ Community MCP | — | ✓ API | ✓ Webhooks | Log analysis, anomaly explanation, alert summarisation via API or MCP. |
Linear Project / Eng. Management | — | ✓ Official MCP | — | ✓ API | — | Official MCP for project management. Read/create issues, comments, projects. |
SAP, ServiceNow, Workday, and other core enterprise platforms. Integration complexity is higher here — custom MCP servers or API middleware are typically required.
| Tool | Native | MCP | Cowork Plugin | Direct API | 3rd Party | Notes |
|---|---|---|---|---|---|---|
ServiceNow ITSM / Enterprise Workflow | — | ✓ Community MCP | — | ✓ API | ✓ IntegrationHub | Ticket triage, knowledge base augmentation, change advisory. See ServiceNow guide. |
SAP (S/4HANA, BTP) ERP | — | ✓ Custom MCP | — | ✓ API | ✓ BTP | Custom MCP recommended for SAP API access. BTP Integration Suite bridges the gap. See SAP guide. |
Workday HR / Finance | — | ✓ Custom MCP | — | ✓ API | ✓ Boomi/Mulesoft | HR data for onboarding agents, payroll queries. Custom MCP or middleware required. |
Oracle ERP / Fusion ERP / Finance | — | ✓ Custom MCP | — | ✓ API | ✓ OIC | Oracle Integration Cloud (OIC) recommended. Custom MCP for read access to financials. |
Zendesk Customer Support | — | ✓ Community MCP | — | ✓ API | ✓ Zapier | Ticket classification, response drafting, CSAT analysis via API very common. |
DocuSign E-Signature / Contracts | — | — | ✓ Cowork Connector | ✓ API | ✓ Zapier | Cowork connector enables document-aware workflows. API for contract analysis pipelines. |
SQL databases, warehouses, and BI tools. MCP's database protocol makes Claude a powerful query interface for analysts and operations teams.
| Tool | Native | MCP | Cowork Plugin | Direct API | Notes |
|---|---|---|---|---|---|
PostgreSQL / MySQL Relational Database | — | ✓ Official MCP | — | ✓ API | Anthropic publishes official database MCP. Natural language to SQL. See database MCP tutorial. |
Snowflake Cloud Data Warehouse | — | ✓ Community MCP | — | ✓ API | Query Snowflake via NL, generate data summaries, auto-build reports. |
BigQuery Cloud Data Warehouse | — | ✓ Community MCP | — | ✓ API | Natural language queries, query generation, cost analysis for GCP environments. |
Tableau / Power BI Business Intelligence | — | — | — | ✓ API | Typically integrated by sending exported data or API results to Claude for narrative generation. |
Pinecone / Weaviate Vector Database | — | ✓ Community MCP | — | ✓ API | Core of RAG architectures. See our Pinecone RAG tutorial. |
Each integration type has different strengths, effort levels, and appropriate use cases. Here's when to use each.
Anthropic-developed integrations that ship with Claude products. Zero configuration, maintained by Anthropic.
The standard protocol for giving Claude tools and data access. The right choice for developer-built integrations where control and customisation matter.
No-code connectors available in Claude Cowork's plugin marketplace. Ideal for knowledge workers who need connected workflows without engineering support.
Build your own integration from scratch using the Claude API. Total flexibility — any tool, any data format, any workflow logic.
n8n, Zapier, Make, and similar automation platforms have Claude nodes. Fast to prototype, limited in sophistication.
Most organisations underestimate how much their integration path determines long-term AI capability. Teams that start with a Zapier automation get quick results but hit a ceiling: rate limits, limited context, no bidirectional data flow, no security controls. Teams that invest in custom MCP server development get a foundation they can build on for years.
The decision framework is simpler than it looks: if you're giving access to a knowledge worker who doesn't write code, start with Cowork connectors. If you're a developer building a product or pipeline, use the Claude API directly or build an MCP server. If you need Claude to actively read and write back to enterprise systems, MCP is the right architecture.
As of March 2026, Anthropic has published official MCP servers for GitHub, Jira, Notion, Linear, PostgreSQL, and several other platforms. The community has published hundreds more. Before building a custom MCP server, check the MCP registry — your integration may already exist.
Where official MCP servers exist, use them. They're maintained by Anthropic or the tool vendor, they follow the MCP specification precisely, and they handle edge cases that custom servers often miss. Reserve custom MCP development for proprietary systems and tools without official support.
Enterprise Procurement Note: When evaluating Claude for enterprise deployment, integration breadth is a key evaluation criterion. Claude's MCP ecosystem gives it a structural integration advantage over closed AI platforms — any API-accessible system can become a Claude integration. If a vendor claims their AI "integrates with everything," ask how: native, MCP, middleware, or custom build? The answer determines your long-term total cost of ownership.
We've integrated Claude with over 40 enterprise platforms. Our API integration and MCP development teams will assess your stack and design the right integration architecture — before you commit to a build.