Adobe Customer Journey Analytics
Run cross-channel reports and build segments in Adobe Customer Journey Analytics.

618 MCP servers with 12,363+ tools, ready to connect to Claude, ChatGPT, Cursor and Agentman agents over the Model Context Protocol.
64 of 618 connectors in Data & ResearchShow all
Run cross-channel reports and build segments in Adobe Customer Journey Analytics.
Look up airfields, landing fees, fuel prices, pilot reports and METAR/TAF from an AI agent.
Read, write and restructure Airtable bases from your AI assistant.
Search, read and analyse arXiv papers from an AI agent.
Query Aura Intelligence workforce data — headcount, hiring, attrition, subsidiaries — from an AI agent.
Search Benevity's verified nonprofit database from an AI agent.
Shorten links, build QR Codes and read click analytics.
Read donor records, gift history and fundraising events from Raiser's Edge NXT.
Search Box content, ask Box AI about your documents, create files and folders.
Create Boost activities, lesson plans, quizzes and standards-aligned materials in Brisk.
Search Candid's 1.9 million US nonprofits and foundations, look up grantmakers by mission and location, read the…
Run SQL against 318 enterprise data sources.
Search global trademark registers, run knockout screens and pull full records.
Upload, search, organise, transform and delete media.
Search 220M+ peer-reviewed papers from your AI assistant.
Ask in plain English how visitors behave on your site: funnels, journeys, page metrics, errors.
Generate classroom-ready K-12 math diagrams.
Search DataCamp’s course catalogue, then authenticate for team admin and learning reports.
Search your data catalogue, trace column-level lineage, draft SQL and edit governance metadata.
Generate differentiated K-12 reading materials.
Search Eedi's library of maths Diagnostic Questions from an AI agent.
Read your own Elfcare results — blood biomarkers, MRI and CT findings, body composition and doctor summaries.
Query your unified customer feedback graph from your AI agent.
Build maps, run spatial SQL and style geographic layers.
Product names and logos belong to their owners. Each connector is built by its own developer, and Agentman is not affiliated with them. The ones Agentman builds and runs are marked “Built and run by Agentman”.
A server that exposes a tool’s capabilities over the Model Context Protocol, so an AI agent can call them directly. It is the standard way to let an assistant act in a system rather than just describe it.
Each server page carries its connection URL, which works in any MCP-compatible client. In Agentman Studio connecting is one click and there is no config file to edit.
Most are not. Each is built by its own developer, and each page names them and links to their documentation. The few Agentman builds and runs are marked “Built and run by Agentman”. Every page lists what the server exposes and cites the sources its factual claims come from.
Each page lists the tools the server exposes. Where we could read the server directly, every tool carries the safety label its vendor gave it: read-only, acts, or destructive. Each page also has a Limits section; read both before connecting anything to a production system.
Connect any of these once and your agents call their tools on their own: on a schedule, in a workflow, with nobody at the keyboard.