# Introducing Agent Connectors in Amplitude Connect Notion, Atlassian, Slack, Linear, and more to Amplitude's Global Agent. Get richer analysis and take action across tools without leaving Amplitude. Source: https://amplitude.com/en-us/blog/agent-connectors --- [Michele Morales](/blog/author/michele-morales) [Senior Product Marketing Manager, Amplitude](/blog/author/michele-morales) [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Famplitude.com%2Fblog%2F%2Fblog%2Fagent-connectors)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Famplitude.com%2Fblog%2F%2Fblog%2Fagent-connectors)[](https://twitter.com/intent/tweet?url=https%3A%2F%2Famplitude.com%2Fblog%2F%2Fblog%2Fagent-connectors\&text=Introducing%20Agent%20Connectors%20in%20Amplitude)[](mailto:?subject=Checkout%20this%20Amplitude%20Article\&body=Check%20this%20out%3A%20https%3A%2F%2Famplitude.com%2Fblog%2F%2Fblog%2Fagent-connectors) Every product team has lived this moment: a metric moves, a funnel breaks, or retention dips, and you turn to Amplitude to answer, “What happened?” The chart gives you the signal. But the explanation may live somewhere else. Maybe it’s a Jira incident from the last sprint. A GitHub PR that changed the flow. Or a Notion spec, a Slack thread, or a Confluence page that explains the decision behind the behavior. The work of answering “Why did this happen?” becomes a manual scavenger hunt through every system you use. Scavenger hunts are for birthday parties. That’s why today, we’re adding [Agent Connectors](https://amplitude.com/ai-agents) to Amplitude. ## Hooking you up Agent Connectors use the Model Context Protocol (MCP) to connect Amplitude Global Agent to the rest of your tool stack, giving your user behavior queries access to all the operational context around your product. - Bring tools and context from Jira, Confluence, Linear, Notion, Slack, GitHub, and more into the Global Agent to get the fully informed product answers you’ve been looking for. - Then, because the connector is two-way, tell Amplitude to take action on your insights in the rest of your tool stack, right from the same conversation. This creates a more complete path from “What changed?” to “Why did it change?” to “What should we do next?” ## What’s available Connect the tools your team relies on every day, plus any custom MCP servers: | **Tool** | **Use Case** | | -------- | ------------------------------------------------------------------------------------------- | | | Cross-reference product data with Jira tickets, Confluence docs, and in-flight project work | | | Connect your codebase or recent pull requests to user metrics and behavioral baselines | | | Surface meeting notes and decisions alongside your product data | | | Cross-reference analytics with issues, sprints, and engineering work in flight | | | Pull in historical context, decisions, and team documentation | | | Connect error and crash data to the user flows and features they affect | | | Surface team discussions and past decisions without digging through old channels | | | Build your own connector for whatever you need |   ### Contextualize your analysis Try asking these questions for a deeper understanding of product behavior. ##### “Why did retention drop after last week’s release?” With** Atlassian or Linear**, Global Agent can trace a drop to its root cause by cross-referencing open tickets alongside your Amplitude data. ##### “Why did we decide to sunset that feature?” Global Agent can use **Slack and Notion** to pull in the original discussion and docs without you having to go find them. ##### “Which user flows does this PR touch? What are the baselines?” Connecting to **GitHub** surfaces the context so you can preview impact before you merge and know exactly what to watch post-merge. ### Take action inside your workflows Turn the beat around and put Global Agent to work in your other tools from the same chat. Try these prompts. ##### “Find the top drop-off points in our sign-up funnel and create a Linear ticket for each with the metric impact.” The diagnosis and the to-do list happen in the same Global Agent prompt, turning drop-off into a backlog. ##### “Did the latest GitHub release cause any regressions? If crash-free sessions dropped by more than 10%, file a P1 in Jira.” Global Agent closes the loop after a release. Engineering gets an automatic signal before it becomes a customer escalation. ##### “Post a weekly summary of product feedback from Slack, behavioral trends, and sprint progress to #product-team every Monday.” Your team can now get a data-backed pulse check from Global Agent without the manual work. Stay on top of it every week. ## Get connected Agent Connectors are available now. Head to Global Agent in Amplitude and open the Connectors settings to get started. The more tools you connect, the more Amplitude can do. All you have to do is ask. CONNECT NOW Use Agent Connectors to enrich your analytics with all the product context in the rest of your stack. [Connect your first tool today](https://app.amplitude.com/signup)! About the author Michele Morales Senior Product Marketing Manager, Amplitude [More from ](/blog/author/michele-morales) [Michele](/blog/author/michele-morales) Michele Morales is a product marketing manager at Amplitude, focusing on go-to-market solutions for enterprise customers. Topics [Agents](/blog/tag/agents) [Amplitude AI](/blog/tag/amplitude-ai) [Integration](/blog/tag/integration) [MCP](/blog/tag/mcp) #### Recommended Reading [Read ](/blog/understand-how-AI-thinks) [Insights](/blog/understand-how-AI-thinks) ###### [Understand How AI Thinks, Get Better Results](/blog/understand-how-AI-thinks) [Jun 2, 2026](/blog/understand-how-AI-thinks) [6 min read](/blog/understand-how-AI-thinks) [Read ](/blog/docs-redesign) [Company](/blog/docs-redesign) ###### [How We Redesigned Amplitude Docs for Agents and Made Everyone an Author](/blog/docs-redesign) [Jun 2, 2026](/blog/docs-redesign) [13 min read](/blog/docs-redesign) [Read ](/blog/ai-broke-experimentation) [Insights](/blog/ai-broke-experimentation) ###### [AI Broke Your Experimentation Program. Here’s How to Fix It.](/blog/ai-broke-experimentation) [Jun 1, 2026](/blog/ai-broke-experimentation) [7 min read](/blog/ai-broke-experimentation) [Read ](/blog/ai-assistant-ticket-deflection) [Product](/blog/ai-assistant-ticket-deflection) ###### [Every Stuck User Is a Support Ticket Waiting to Happen](/blog/ai-assistant-ticket-deflection) [Jun 1, 2026](/blog/ai-assistant-ticket-deflection) [3 min read](/blog/ai-assistant-ticket-deflection)