Service integrations

Speedwave connects to enterprise collaboration platforms, code hosting systems, project trackers, and local utilities through isolated worker containers. Each integration worker executes in an independent container, mounting scoped service credentials in read-only mode without exposing secrets to other services or to Claude Code itself. Consult Credentials management for credential storage specifications.

Slack Team messaging, channels, and thread discussions.

SharePoint Corporate document management and enterprise intranets.

GitLab Repository management, merge requests, and CI/CD pipelines.

GitHub Repository management, pull requests, and GitHub Actions.

Atlassian Jira agile planning and Confluence technical documentation.

Redmine Self-hosted issue tracking, time logging, and project hierarchies.

Office documents Native manipulation of Word, Excel, PowerPoint, and PDF files.

Web automation Headless Chromium browser automation via Playwright MCP.

OS integrations macOS Calendar, Reminders, Mail, and Notes automation.

Context7 Up-to-date framework and library API documentation lookup.

Gateway routing and tool aggregation

Regardless of the number of active integrations, Claude interacts with a unified endpoint: the Tool Gateway. The gateway exposes two fundamental tools: search_tools dynamically discovers available capabilities across active services, and execute_code executes selected tools on their target worker containers. The gateway manages routing without storing persistent credentials.

Certain workers operate out of the box without authentication (such as Office documents, Web automation, and Context7). External services require credential configuration before requests succeed (see Connect an integration).

Enabling an integration for the first time compiles its worker image locally within the virtual machine sandbox. Subsequent activations reuse local image layers and start immediately.