Tools

Extensions and
integrations

The broader ecosystem that puts Claude inside your existing tools. IDE extensions for developers, desktop extensions for power users, plugins for Claude Code, and MCP as the protocol underneath it all.

Everything else in the Tools section lives inside Claude itself. Extensions are the opposite: they bring Claude into the places you already work. Your code editor. Your desktop environment. Your automation pipelines. The Model Context Protocol (MCP) is the standard that makes all of it possible.


MCP: the protocol underneath

Model Context Protocol is an open standard created by Anthropic that lets Claude talk to external tools and data sources in a consistent way. Think of it as USB-C for AI: one protocol, many things you can plug in. Connectors, IDE extensions, desktop extensions, plugins, and custom integrations all use MCP under the hood.

Claude via MCP IDE extensions Desktop extensions Plugins Custom MCP servers Remote connectors Third-party tools

One protocol, many surfaces. MCP is the shape Claude uses to talk to everything.

You do not need to understand MCP to use extensions. But knowing it exists helps explain why so many different tools can plug into Claude so easily: they all speak the same protocol.


Four types of extension

The extension ecosystem

IDE extensions. Native integrations in your code editor. Claude sits inside the tool you already use, with full access to your codebase.

  • VS Code (and forks like Cursor, Windsurf): native graphical interface for Claude Code. Review and edit plans, auto-accept edits, @-mention files with line ranges, conversation history, multiple tabs.
  • JetBrains (IntelliJ, PyCharm, WebStorm, GoLand, PhpStorm, Android Studio): dedicated plugin in the JetBrains marketplace. Quick launch (Cmd+Esc / Ctrl+Esc), interactive diff viewing, automatic selection context, file references (@File#L1-99).

Desktop extensions. One-click installable MCP servers packaged as .mcpb files. No terminal, no JSON configuration, no developer tools needed.

  • Download the .mcpb file, double-click, click Install in Claude Desktop.
  • Sensitive data (API keys, credentials) stored securely in the OS keychain.
  • Auto-updates when new versions are published.
  • Growing curated directory built into Claude Desktop.

Plugins. Lightweight capability bundles for Claude Code. Found via the /plugin command or the Discover tab in the marketplace at claude.com/plugins.

  • Code and development: frontend design, code review, code simplification, Playwright browser automation.
  • Workflow: feature development agents, brainstorming, live documentation lookup (Context7).
  • Integrations: Zapier (8,000+ apps), Intercom, Netlify, Terraform.

Custom MCP servers. For organisations that want to connect Claude to their own internal systems. Build using the Anthropic SDK (TypeScript or Python), host locally or remotely, authenticate via OAuth.

  • Expose internal databases, APIs, or file systems to Claude.
  • Full control over what Claude can read and write.
  • Enterprise orgs can build private marketplaces for internal distribution.
  • Pre-built reference servers available on GitHub for common integrations (Postgres, Git, Puppeteer).

IDE extensions in more detail

If you write code, the IDE extension is probably the single most relevant tool in this section. Claude lives inside your editor, reads your codebase, and helps without context switching.

FeatureVS CodeJetBrains
Launch shortcutCmd+Shift+P, then "Claude"Cmd+Esc / Ctrl+Esc
File references@-mention files with line ranges@File#L1-99 syntax
Diff viewingInline diff reviewInteractive diff with IDE tools
Auto-accept editsYesYes (caution: may auto-execute IDE configs)
Multiple sessionsMultiple tabs side by sideSingle session
Selection contextHighlight code, then askAutomatic selection sharing
Remote development (WSL)Plugin on remote host neededPlugin on remote host needed

For VS Code users: this is the recommended way to use Claude Code. The graphical interface is richer than the terminal, and you can review and accept changes visually before they are applied.


Zapier: the everything connector

Worth calling out specifically because it is the broadest integration available. The Zapier connector lets Claude access 8,000+ apps and execute real actions: send emails, update CRMs, schedule meetings, pull sales data, add records to databases. It is not read-only. Claude can do things through Zapier, not just read things.

Available on Pro, Max, Team, and Enterprise plans. Set it up via the connectors directory. Once connected, you can say things like "pull this week's closed deals from HubSpot and draft a summary for the Monday standup" and Claude will actually query HubSpot, not ask you to paste the data.


Getting started

Pick one based on where you work:

1.

If you write code: install the VS Code or JetBrains extension. It is the highest-leverage tool for developers in the entire handbook.

2.

If you use Claude Desktop: browse the desktop extensions directory inside the app. One-click install. Start with whichever matches a tool you already use.

3.

If you want Claude to talk to your business tools: set up the Zapier connector. It covers more tools than any other single integration.

4.

If you are building something custom: read the MCP documentation on platform.claude.com. The TypeScript and Python SDKs make it straightforward to build a custom server that exposes your internal systems to Claude.


Security note for extensions


Extensions are where Claude stops living in its own window and starts living inside the tools you already use. For developers, the IDE extension is transformative. For everyone else, start with Zapier or a desktop extension and expand from there.

Go back to the Tools hub to see all eight tools, or to the handbook homepage to start somewhere else entirely.