---
title: "Integrations"
description: "GitHub, Slack, Linear, Sentry, phone, and MCP servers"
canonical_url: "https://hoplite.sh/docs/integrations"
markdown_url: "https://hoplite.sh/docs/integrations.md"
---

# Integrations
URL: /docs/integrations
LLM index: /llms.txt
Description: GitHub, Slack, Linear, Sentry, phone, and MCP servers
Related: /docs/integrations/slack, /docs/integrations/linear, /docs/agent/mcp, /docs/github

# Integrations

Integration settings live together under **Settings → Integrations**, grouped into personal, selected-project, and workspace sections. Connect the provider at the scope it needs, then use a project binding when the provider must route events into one particular project. Slack's workspace installation authorizes the bot across every project in the Hoplite workspace, while Linear bindings route its events into a project.

## Available integrations

| Integration | What it unlocks |
| --- | --- |
| **[GitHub](/docs/github)** | The foundation: the GitHub App is installed at the workspace level and repos bind to projects |
| **[Slack](/docs/integrations/slack)** | Connect your Slack workspace and optionally route channels to projects, so threads start and stream where your team talks |
| **[Linear](/docs/integrations/linear)** | Route Linear mentions and delegated issues into a project, with progress flowing back to the issue |
| **Sentry** | Bind one or more Sentry projects so agents can inspect redacted issues, events, releases, alerts, teams, and members; issue comments and resolution are separately capability-gated |
| **Phone / iMessage** | Connect your personal Messages account to check agents, relay instructions, and start threads by text |
| **[MCP servers](/docs/agent/mcp)** | Extend the agent's tool catalog with Model Context Protocol servers |

## Phone and iMessage

Under **Settings → Integrations → Personal**, connect your phone and send the prefilled greeting in Messages. If the pairing does not complete because a relay, keyboard, or OS stripped the invisible pairing token, choose **Or add manually**, enter your number with its country code, and send the new prefilled message. Loosely formatted international numbers are accepted; a number already linked to an active account cannot be claimed. Unlink the current connection before moving the number between active accounts.

To drive Hoplite *from* your tools instead — Claude Code, Cursor, or another MCP client — see [Hoplite's MCP server](/docs/cli/mcp-server).

## GitCafe

When this rollout-gated connection is enabled for your workspace, an administrator can connect GitCafe with a username and personal access token, sync its discovered repositories, and bind one to a project. The connected repository then uses the same provider-neutral agent tools for branches, pull requests, reviews, and source-control operations.

## Platform web research

Staff can enable the first-party **Exa web search** capability from the admin Settings screen after provisioning `EXA_API_KEY` to every worker service. It adds a bounded `web_search` tool to agent runs across the platform. This is intentionally not an MCP connection: the Exa credential stays in Hoplite's worker environment and never reaches projects or sandboxes. The setting is off by default and takes effect for newly built agent contexts. See [Tools and permissions](/docs/agent/tools) for how the agent treats search results.

## Sitemap

See the full [sitemap](/docs/sitemap.md) for all pages.
Well-known sitemap: [/docs/.well-known/sitemap.md](/docs/.well-known/sitemap.md).