What Does Claude Integrate With? Full Overview

Claude integrates with a wide range of tools depending on how you use it: as a chat app, as a coding assistant, as a connector inside productivity software, or as a raw API you wire into your own product. There isn't one single "integrations list" because Anthropic ships several distinct products (Claude.ai, Claude for Desktop, Claude Code, the Claude API) and each has a different integration surface.

This article gives you the map: what connects natively, what connects through the Model Context Protocol (MCP), what connects through third-party automation tools, and what you need to build yourself if you want Claude inside your own application.

The short answer

At a high level, Claude integrates with:

• Productivity suites — Google Workspace and Microsoft 365 (Word, Excel, Outlook, PowerPoint) via connectors or plugins
• Developer tools — VS Code, JetBrains IDEs (IntelliJ), Cursor, and the terminal via Claude Code
• Business apps — CRMs, accounting tools like Xero, BI tools like Power BI, spreadsheets, and databases, mostly through the API or MCP servers
• Automation platforms — Zapier, Make, and similar tools that let you trigger Claude from webhooks and events
• Note and knowledge tools — Obsidian and similar apps, usually via plugins or local API calls
• Your own software — through the official Claude API or through a wrapper like SubToAPI if you want a simpler key-based setup

The rest of this article breaks down each category so you can figure out which path fits your use case.

Native app integrations

Claude.ai (web/mobile) has built-in connectors for Google Drive, Gmail, and Calendar in supported plans, letting Claude read and reference your documents and messages during a conversation. These connectors are managed inside the app settings and don't require any code.

Claude for Desktop extends this with support for the Model Context Protocol (MCP), Anthropic's open standard for connecting AI models to external tools and data sources. Through MCP servers, Claude for Desktop can reach local files, databases, and third-party services that have an MCP server implementation.

Claude Code is the CLI-based coding agent, and it integrates directly with your terminal, git, and IDEs — VS Code, JetBrains products, and Cursor all have documented integration paths. It can run shell commands, edit files, and use MCP servers to reach outside tools during a coding session.

Model Context Protocol: the common thread

MCP is the piece that ties a lot of Claude's integrations together. Instead of every tool building a custom Claude plugin, MCP defines a standard way for a "server" (a thin adapter around a database, API, or app) to expose actions and resources that Claude can call. This is how Claude reaches things like local filesystems, Slack, Postgres, GitHub, and dozens of other systems without Anthropic building each one individually. If you see a tool advertised as having an "MCP server," that's the integration mechanism.

Productivity and office tools

For everyday office work, Claude connects to:

• Google Workspace — Docs, Sheets, Drive, Gmail, Calendar, mostly through native connectors
• Microsoft 365 — Word, Excel, Outlook, PowerPoint, usually through Azure-based setups, plugins, or the API depending on the method
• Notion, Obsidian — through plugins or local API integrations that let Claude read and write notes
• Slack — through bots built on the API, or MCP servers where available

These integrations are aimed at knowledge workers who want Claude inside the tools they already use daily, without touching code.

Developer and data tool integrations

For teams building on top of Claude, the integration surface is broader:

• IDEs — VS Code, JetBrains, Cursor, mainly through Claude Code
• Spreadsheets and BI — Excel and Power BI, typically via the API combined with a script or add-in that sends data to Claude and returns results
• Accounting and business systems — tools like Xero connect through the API, usually to summarize transactions, draft reports, or answer questions about financial data
• Automation platforms — Zapier and Make let you trigger a Claude call from a form submission, new row, or webhook, without writing a full backend

All of these ultimately rely on the same underlying mechanism: an HTTPS request to Claude's API with a message payload and an API key.

Turning Claude into an API for your own product

If you're building software rather than connecting existing apps, the integration question becomes simpler: you need a stable HTTPS endpoint, an API key, and predictable request/response formats for messages, streaming, and tool use.

This is where a lot of teams hit friction — managing raw provider credentials across a team, tracking usage per application, and rotating keys safely takes real infrastructure. SubToAPI exists for exactly this gap: it turns your existing Claude access into a clean API with sub_live_... application keys, streaming support, tool use, and usage metadata, all from one dashboard. Instead of every internal app sharing one fragile credential, each app gets its own scoped key.

A basic request looks like this:

curl https://api.subtoapi.app/v1/messages \
  -H "Authorization: Bearer $SUBTOAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "claude-sonnet",
    "max_tokens": 1024,
    "messages": [
      {"role": "user", "content": "Summarize this integration list."}
    ]
  }'

If you're integrating Claude into a product for the first time, the quickstart walks through authentication, the messages docs cover the request format, streaming covers real-time output, and tools covers function-calling style integrations. Plans start at €9/month for solo use, with team and scale tiers at /pricing, and a free trial is available at /signup.

Choosing the right integration path

• You want Claude in the apps you already use → native connectors (Google Workspace, Microsoft 365) or MCP servers
• You're coding and want Claude in your editor → Claude Code with VS Code, JetBrains, or Cursor
• You're automating a workflow without writing a backend → Zapier, Make, or similar
• You're building a product feature or internal tool → the Claude API directly, or a managed layer like SubToAPI if you want keys, streaming, and usage tracking without building that infrastructure yourself

questions

Does Claude integrate with Slack and Zapier? Yes. Slack integrations are typically built on top of the API or MCP servers, and Zapier/Make support Claude as an action step you can trigger from other apps.

What's the difference between Claude for Desktop and Claude Code integrations? Claude for Desktop is aimed at general use with MCP-based connectors for files and services; Claude Code is a coding-focused CLI agent that integrates with IDEs, git, and the terminal.

Can I integrate Claude into my own app without managing raw API credentials? Yes — services like SubToAPI sit on top of your Claude access and give each application its own API key with streaming, tool use, and usage data, so you don't manage shared provider credentials directly.