On this page

MCP Connectors for Global Agent

MCP connectors let Global Agent reach into the tools where your team plans, ships, and talks, so it can ground answers in product specs, tickets, and conversations alongside your Amplitude data and page context. Use connectors to ask cross-source questions like "Which retention drop correlates with the Jira incidents last sprint?" and to take action in those tools without leaving Amplitude. This is useful for product managers connecting analytics to ongoing work, and for technical teams who want the agent to read and update tickets, docs, and repositories.

Supported connectors

Global Agent supports the following MCP connectors:

ConnectorWhat Global Agent can do
Atlassian (Jira, Confluence)Read Jira tickets and Confluence pages, create and update issues, and comment.
GitHubRead pull requests, issues, and code, open issues, and comment on pull requests.
GranolaRead meeting notes and transcripts to bring discussion context into the conversation.
LinearRead issues and projects, and create and update issues.
NotionRead pages and databases, and create and update pages.
SentryRead error and issue details to connect production problems with analytics.
SlackSearch and read channels and threads, and post messages.

Need another tool?

To connect a tool that isn't on this list, add a custom connector.

Organization Admins control which of these connectors org members can authorize from the Connectors tab in AI Settings and Controls. For more detail, refer to Manage available connectors.

How MCP connectors work

Global Agent uses the Model Context Protocol (MCP) to connect with external services. Each connector exposes a set of tools that Global Agent can call during a conversation. Tools fall into two categories:

  • Read tools pull information into the conversation, like fetching a Jira ticket, reading a Notion page, or searching a Slack channel.
  • Write tools take action in the connected service, like creating a ticket, updating a doc, or posting a message.

You authorize each connector through OAuth, so Global Agent acts on your behalf and respects the same permissions you have in the connected tool. Once connected, that service's tools stay available to Global Agent in every conversation until you disconnect the connector.

Use cases

  • Correlate analytics with product work: Ask Global Agent to compare a retention drop against Jira incidents or Linear bugs from the same sprint.
  • Ground analysis in product specs: Pull a Notion or Confluence spec into the conversation, then ask Global Agent to find the matching funnel or cohort.
  • Close the loop on insights: Turn an analysis into a Jira ticket, Linear issue, or Slack post without leaving Global Agent.
  • Summarize cross-tool context: Ask Global Agent to combine a GitHub PR description, the related Linear ticket, and an Amplitude chart into a single summary.

Take action with write tools

Connectors support both read and write tools, so Global Agent can do more than retrieve context. You can ask Global Agent to:

  • Create a Jira or Linear ticket from an insight.
  • Update a Confluence or Notion page with findings from an analysis.
  • Post a summary to a Slack channel.
  • Open a GitHub issue or comment on a pull request.

Global Agent confirms write actions before it runs them, so you stay in control of what changes in the connected tool.

Prerequisites

  • Global Agent enabled for your organization. Organization Admins manage availability from AI Settings and Controls.
  • An account in the external service you want to connect, with permission to authorize third-party apps.

Set up a connector

  1. Open Global Agent.
  2. Click the Select Mode icon and then select Connectors > Add Connectors.
  3. Select the connector you want to enable, then click Connect.
  4. Complete the OAuth flow in the popup window to authorize Global Agent.
  5. Return to Global Agent. The connector now appears as available in the Connectors panel.

Repeat for each connector you want to use. Connectors only need authorization one time for each account.

Manage available connectors

By default, every supported MCP connector is available to org members. Organization Admins manage which connectors are available, and whether members can add custom MCP servers, from AI Settings and Controls.

  1. Go to Settings > AI Controls.
  2. Open the Connectors tab to view the connectors available to your org members.
  3. Use the Enabled toggle on a connector's row to allow or block it for org members.
  4. Select the pencil icon (Edit) on a connector's row to change its configuration, or the trash icon (Delete) to remove it.
  5. Toggle Allow custom MCP servers off to prevent org members from importing or using custom MCP servers.
  6. To add a connector beyond the built-in list, select Add custom MCP server.

Custom connectors

If the tool you need isn't a supported connector, you can bring your own. Any service that exposes a remote MCP server can become a custom connector, so Global Agent reads from and writes to tools beyond the built-in set.

  1. In a Global Agent chat, click the plus sign (+).
  2. Select Connectors > Manage Connectors.
  3. Click Add custom MCP server.

Custom connectors appear alongside built-in connectors, and Organization Admins manage them from the Connectors tab in AI Settings and Controls.

Frequently asked questions

Was this helpful?