Gmail
Search, read, send and organise Gmail and manage Google Tasks from your AI agent.

618 MCP servers with 12,363+ tools, ready to connect to Claude, ChatGPT, Cursor and Agentman agents over the Model Context Protocol.
17 of 618 connectors in CommunicationShow all
Search, read, send and organise Gmail and manage Google Tasks from your AI agent.
Give an AI agent its own email inbox: create inboxes, read threads and send mail to anyone.
Search meeting notes, transcripts, action items, calendar and connected email.
Pull meeting transcripts, summaries, action items and participants from Fellow.
Search Fireflies transcripts and summaries.
Search a Front inbox, draft replies and comment on conversations from an AI agent.
Google's own Gmail server: search threads, read messages, manage labels, trash or unspam mail.
Give an AI agent its own email address, phone number and iMessage line.
Search Intercom conversations, contacts, companies and Help Center articles.
Draft, schedule and send email campaigns to your subscriber list from chat, plus manage subscribers, groups and…
Search news and social posts, pull sentiment and share-of-voice stats, manage saved searches.
Send push, email and SMS and manage subscribers from an AI chat.
Search and update Pylon support issues, accounts and contacts.
Read texts and call transcripts from a Quo business phone number and send SMS.
Send transactional email, run broadcasts to a contact list, manage domains and templates, and read inbound mail.
Read RingCentral Team Chat and post, edit or delete messages.
Searches Twilio's documentation and API specifications.
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.