> ## Documentation Index > Fetch the complete documentation index at: https://modem.dev/docs/llms.txt > Use this file to discover all available pages before exploring further. # Overview > Connect your tools to capture feedback and take action Modem connects to the tools where your users and team already work. Integrations serve three purposes: **capturing data** (messages, issues, emails) so Modem can analyze it, **giving the agent tools** to take action on what it finds, and **letting external MCP clients** invoke the Modem Agent. ## Data Sources These integrations continuously capture messages and events, feeding them into Modem's analysis pipeline. Messages are grouped into [topics](/guides/topics), classified by type (bug, feature request, praise, complaint), and linked to [people](/guides/people) and [companies](/guides/people#companies). Capture messages from selected channels. Also lets you talk to the Modem Agent directly from Slack. Capture messages from Discord servers. Currently capture-only (no agent interaction). Sync issue and PR metadata: titles, descriptions, comments, labels, and review discussions. Does not read source code. Capture conversations in real time. The agent can also search, reply, and manage tags. Capture Zendesk tickets in real time, including replies, internal notes, and ticket metadata. Capture issues and comments in real time. The agent can also search, create, and update issues. Capture customer support requests from Jira Service Management, including public replies and internal notes. Route email feedback to Modem through a dedicated inbound address. | Source | What's captured | Historical backfill | Real-time | | ----------------- | ------------------------------------------------- | -------------------------- | -------------- | | Slack | Messages, reactions, threads | \~30 days (varies by plan) | Yes | | Discord | Messages, reactions, threads, forum posts | 30 days | Yes | | GitHub | Issue/PR titles, descriptions, comments, labels | 30 days | Yes (webhooks) | | Intercom | Conversations, replies, notes, CSAT, contacts | Admin-initiated | Yes (webhooks) | | Zendesk | Tickets, replies, internal notes, ticket metadata | None | Yes (webhooks) | | Jira | Issues, comments, issue metadata | None | Yes (webhooks) | | Jira Service Desk | Requests, public replies, internal notes | None | Yes (webhooks) | | Email | Email body and threads | None | Yes | All data sources let you choose what to monitor: specific Slack channels, Discord channels, GitHub repositories, or a dedicated email address. Start narrow and expand as needed. ## Agent Tools These integrations give the Modem Agent the ability to take action beyond reading your data. They don't capture data into Modem's pipeline. Instead, the agent queries or writes to them on demand when you ask. Search, create, and update issues. Link topics to existing tickets. Search, create, and update issues. Link topics to existing issues. Search, read, and create pages and database entries in your Notion workspace. Query product analytics, feature flags, experiments, and error tracking data. Delegate implementation tasks to Claude Code, Cursor, or Devin, enriched with Modem context. Connect any MCP-compatible tool server to extend the agent's capabilities. Slack, Intercom, and Jira are both data sources and agent tools. Slack lets your team talk to the agent via DM or @mention. Intercom lets the agent search, reply to, and manage conversations (when write access is enabled). Jira captures issue activity and lets the agent search, create, and update issues. ## External Agent Access These integrations make Modem available to other AI tools. They don't add new data sources or outbound tools for the Modem Agent. Instead, they let external clients call the agent with access to your Modem context. Use the Modem Agent from external MCP clients like Claude Code, Cursor, VS Code, Windsurf, and Cline. ## Setup Most integrations are configured from **Settings** > **Integrations** in the Modem dashboard. Data source integrations use OAuth (Slack, Discord, GitHub, Intercom, Zendesk) or a generated address (Email). Agent tools use OAuth (Linear, Notion) or API keys (PostHog, Coding Agents, MCP Servers). The Modem MCP Server is configured from your external MCP client. Each integration page has step-by-step setup instructions. ## Cross-Platform Identity When you connect multiple data sources, Modem links people across platforms using shared identifiers like email addresses. A user who messages you on Slack, files a GitHub issue, and emails support gets a single unified profile with their full history. This also works at the company level. Email domains and other signals help associate people with companies, giving you an account-level view of feedback across all sources. See [Companies & People](/guides/people) for details. ## Next Steps Connect your first integration in 5 minutes. See what the agent can do with your connected tools.