Integrations overview
The ways Otis connects to the tools your team uses, including your coding agent, your repositories and Slack.
Integrations connect Otis to tools that your team already uses. This section has a page for each of the developer tools that connect Otis to your coding agent and to your repositories.
Otis connects to other tools as well. Each of those is documented with the feature it belongs to, and this page links to them.
Developer tools
Coding agents
Install the Otis skills in Claude Code, Codex, Cursor or another agent, so that it can instrument your app and ask Otis about your product.
MCP server
Connect an agent to Otis directly, and see the tools, workflows and reference docs that the server provides.
GitHub App
Connect your repositories to give Otis context about your codebase, pull requests and deployments.
The Otis skills and the MCP server both connect a coding agent to Otis. A connected agent can ask Otis how your product is used, add the Otis SDK to your app, and check that the instrumentation works.
Start with the skills if your agent supports them. Each skill tells your agent when to consult Otis and which steps to follow. The skills work through the MCP server, and the Claude Code and Codex plugins install both together. MCP (Model Context Protocol) is the standard way coding agents connect to outside tools.
Connect the MCP server alone if your agent doesn't support skills. The server provides the same workflows, and you ask your agent to follow one.
The GitHub App is separate from both. It connects your repositories to Otis, which gives Otis context about your code and how it changes.
Slack
With Slack connected, Otis can post each new insight to a channel, and you can reply in the thread to ask Otis about it. Otis can also post the daily briefing to Slack.
A team admin connects your Slack workspace in the team's settings. On the Integrations tab of the project's settings, you then choose whether Otis posts insights, whether it posts the team briefing, and which channels it uses.
Briefings covers the briefing settings, and Customization lists the delivery controls.
SDK integrations
The Otis SDK works with tools that your app may already use. The SDK section documents each one.
| Tool | What the SDK does | Page |
|---|---|---|
| AI frameworks | Traces calls made through the Vercel AI SDK, the OpenAI client, the Anthropic client and the Claude Agent SDK | Agent traces |
| OpenTelemetry | Adds Otis to an existing OpenTelemetry setup, or receives OpenTelemetry spans directly | OpenTelemetry |
| Feature flag platforms | Records flag assignments from a platform that has an OpenFeature provider, such as LaunchDarkly, Statsig, PostHog or GrowthBook | Feature flags |
| Auth providers | Takes user and session IDs from providers such as Clerk, Supabase, WorkOS AuthKit, Stytch and Auth.js | Sessions |
| Consent management platforms | Follows the consent a user gives in Usercentrics, Cookiebot or OneTrust before it sets cookies | Browser and consent |