Integrations
Integrations connect Claude to services like Slack, GitLab, Jira, and your local files, so it can read and act in the tools your team already runs. Every integration is an isolated worker that mounts only its own service credentials, so enabling Slack never gives that worker’s container access to your GitLab or Jira tokens. See how those credentials are stored and mounted in How credentials are handled.
No matter how many of these you turn on, Claude still sees a single MCP server, the Tool Gateway, with exactly two tools behind it: search_tools finds the right tool across every enabled integration, and execute_code runs it on the correct worker. The Tool Gateway itself holds no credentials and only routes calls.
Some integrations need no credentials at all: Office, web automation, and Context7 work without setup, and Context7 also takes an optional API key for higher rate limits. For every other service, see Connect an integration for how to turn it on for a project and confirm it’s working.
Turning on an integration for the first time builds its worker image, and that first build takes longer for heavier images: web automation pulls in Chromium, and Office pulls in LibreOffice and a Python environment. Later toggles reuse the cached image and are near-instant. If a build fails, the integration reverts to disabled.
Office is a beta integration: it stays hidden until you turn on Beta features in the Speedwave tray menu, covered in Beta features. Slack, GitHub, and Atlassian are not gated by that toggle and are visible by default.