Registry / verified 2026-09-25
Integrations
Agents earn their keep inside the systems you already run. This is the map of what each cataloged agent connects to, what it does there, and what to check before you hand over a token.
- 40
- Targets
- 222
- Agent connections
- 6
- Kinds
01
Dev tools
Repositories, editors, issue trackers, and tool servers that agents read from and write to.
MCP servers
Agents that act as MCP clients can attach any Model Context Protocol server, which makes this the widest integration surface in the catalog.
Via MCP over stdio · Streamable HTTP · OAuth for remote servers


+3034 agentsGitHub
Agents read repositories, open branches and pull requests, review diffs, and respond to issues and CI results.
Via GitHub App · REST and GraphQL API · Official MCP server


+2529 agentsVS Code
Agents run inside the editor as extensions, with access to the open workspace, terminal, and diagnostics.
Via VS Code extension · Language Model and Chat APIs · MCP client support



+610 agentsJetBrains IDEs
Agents plug into IntelliJ-family IDEs as plugins and use the IDE's index, inspections, and run configurations.
Via JetBrains plugin · Agent Client Protocol · MCP client support



+37 agentsJira
Agents read and update Jira tickets, so work requested in a ticket can be planned, executed, and reported on.
Via Atlassian REST API · Atlassian Remote MCP server · OAuth 2.0 app


+15 agentsLinear
Agents pick up assigned issues, post progress back to the thread, and link the resulting pull request.
Via Linear agent API · Webhooks · Official MCP server


4 agentsCursor
Agents and tools that integrate with Cursor extend the editor's own agent with rules, MCP tools, and background work.
Via MCP client support · VS Code extension compatibility · Cursor rules


3 agentsGitLab
Agents work merge requests, read pipelines, and act on issues inside self-managed or hosted GitLab.
Via REST and GraphQL API · Project access tokens · MCP server
1 agent
Neovim
Agents run as Neovim plugins or as terminal tools next to the editor, for developers who live in the terminal.
Via Lua plugin · Agent Client Protocol · Terminal CLI
1 agent
02
Messaging & comms
Chat, mail, calendar, and phone channels where agents listen and reply.
Slack
Agents sit in channels and DMs, answer questions, take requests from a thread, and post results back where the team works.
Via Slack app with Events API · Bot and user tokens · Agents and AI Apps surface



+1620 agents
Gmail
Agents triage the inbox, draft replies, and pull context from threads for scheduling, support, and sales work.
Via Gmail API with OAuth · Google Workspace add-on · MCP server


+59 agentsGoogle Calendar
Agents read availability and create or move events, which makes them useful for scheduling and meeting prep.
Via Google Calendar API with OAuth · MCP server


+26 agentsTelegram
Agents run as Telegram bots, a common front door for personal agents that need a chat interface on any phone.
Via Telegram Bot API · Webhooks or long polling



+26 agentsTwilio / PSTN
Voice and SMS agents place and answer phone calls and texts over the public phone network, usually through Twilio.
Via Twilio Programmable Voice and Media Streams · SIP trunking · Messaging API

.png)
+26 agentsDiscord
Agents run as Discord bots that answer members, moderate, and act on commands in community servers.
Via Discord bot with Gateway API · Slash commands · Webhooks



+15 agentsWhatsApp
Agents answer customers and personal requests over WhatsApp, usually through the Business Platform.
Via WhatsApp Business Platform (Cloud API) · BSP partners such as Twilio · Unofficial bridges



+15 agentsiMessage
Personal agents on a Mac read and send iMessages so you can reach them from the Messages app.
Via macOS Messages database and AppleScript · Local bridges on an always-on Mac
1 agentSignal
Personal agents use Signal as a private chat channel, typically through a self-hosted bridge.
Via signal-cli bridge · Self-hosted REST wrappers
1 agent
03
CRM & business
CRM and business systems where agents look up and act on records.
Salesforce
Agents look up accounts, update opportunities, and log activity so sales and service work lands in the system of record.
Via Salesforce REST API · Connected App with OAuth · Agentforce actions


+48 agentsHubSpot
Agents read and write HubSpot contacts, deals, and tickets to support marketing, sales, and service workflows.
Via HubSpot API with OAuth · Private apps · Official MCP server


+15 agentsZendesk
Support agents resolve Zendesk tickets, draft replies, and route conversations they cannot close.
Via Zendesk API · Marketplace apps · Messaging and Sunshine Conversations



4 agentsGoogle Drive
Agents search, read, and create files in Google Drive to ground answers and produce documents.
Via Google Drive API with OAuth · Workspace connectors · MCP server


3 agentsIntercom
Agents answer customers in Intercom Messenger and work the inbox alongside the support team.
Via Intercom API · Inbox and Messenger apps · MCP server


3 agentsLinkedIn
Sales and recruiting agents use LinkedIn for prospect research and outreach.
Via Sales Navigator and partner APIs · Browser automation


3 agentsNotion
Agents search and edit Notion pages and databases, using the workspace as both a knowledge source and a place to write.
Via Notion API with page-level sharing · Official MCP server


3 agentsSharePoint
Enterprise agents read SharePoint and OneDrive content as a knowledge source inside Microsoft 365.
Via Microsoft Graph API · Copilot connectors · Entra ID app registration


3 agentsZapier
Agents use Zapier as a bridge to thousands of apps that have no direct integration.
Via Zapier MCP · Zapier AI Actions · Webhooks

2 agents
04
Cloud & ops
Infrastructure and operations surfaces agents observe or change.
Datadog
Ops agents read Datadog metrics, logs, and traces to investigate alerts and explain incidents.
Via Datadog API and application keys · Official MCP server · Native Bits AI



+15 agents
Okta
Agents use Okta for identity checks and user lifecycle work, and for authenticating agents themselves.
Via Okta Management API · OAuth service apps · Workflows


4 agentsPagerDuty
Incident agents respond to pages, gather context, and keep the incident record current.
Via PagerDuty REST and Events API · Webhooks · MCP server



4 agents
Auth0
Agent builders use Auth0 to log users in and to give agents scoped, delegated access to other APIs.
Via Auth0 for AI Agents · Token Vault · OAuth 2.0 and OIDC
2 agentsAWS
Ops and coding agents query and change AWS resources, from reading logs to deploying infrastructure.
Via AWS SDK and CLI with IAM roles · AWS MCP servers · Bedrock AgentCore

2 agentsCrowdStrike
SOC agents pull detections and host context from CrowdStrike Falcon to triage security alerts.
Via Falcon API with OAuth clients · Falcon Fusion workflows

2 agentsKubernetes
Ops agents inspect clusters, read pod logs and events, and propose or apply fixes.
Via Kubernetes API via kubeconfig · kubectl · MCP server

2 agentsSplunk
Security and ops agents run Splunk searches to investigate alerts across logs.
Via Splunk REST API · Splunk SOAR · MCP server

2 agents
05
Browser automation
Browser control layers agents drive when no API exists.
Chrome / Chromium
Browser agents drive Chrome or Chromium directly to use websites that have no API.
Via Chrome DevTools Protocol · Browser extension · Hosted browser sessions


+37 agents
Playwright
Agents use Playwright to control browsers reliably, both for automation and for testing web apps they build.
Via Playwright library · Playwright MCP server

3 agents
Puppeteer
Agents use Puppeteer to script headless Chrome for scraping, rendering, and automation.
Via Puppeteer library · Chrome DevTools Protocol
1 agent
06
Payments
Payment rails agents can charge or get paid through.
Coinbase x402 rail
Agents pay for API calls and content per request with stablecoins, using the HTTP 402 status code.
Via x402 protocol · Coinbase Developer Platform wallets
1 agentStripe
Agents create payments, invoices, and payment links, and read billing data to answer customer questions.
Via Stripe agent toolkit · Official MCP server · Restricted API keys
None cataloged yet0 agents
Frequently asked
What counts as an integration?
A documented, named connection between an agent and an external system: an API target, host application, messaging channel, or infrastructure layer. "Works through an API" alone doesn't count. There has to be a first-class connector or documented support.
Why do integrations matter more than feature lists?
Agents earn their keep inside existing systems. An SDR agent without Salesforce, an ops agent without PagerDuty, or a voice agent without telephony is a demo, not a deployment. The integration map is the fastest predictor of whether an agent fits your stack.
Is MCP support the same as an integration?
Not quite. An agent that speaks MCP can attach any MCP server, so it can reach many systems without a native connector. We list MCP support separately and only count a named target when the agent documents support for it directly.
Why is part of each integration's agent list gated?
The full integration matrix is the part of the dataset that took the most verification work. The public view shows the top 80% of agents per integration; the complete tail is available to signed-in accounts.