Vertiso Memory
One durable memory store for every AI tool: facts, decisions, preferences and handoffs across Claude, Codex and Cursor.

618 MCP servers with 12,363+ tools, ready to connect to Claude, ChatGPT, Cursor and Agentman agents over the Model Context Protocol.
234 of 618 connectors in ProductivityShow all
One durable memory store for every AI tool: facts, decisions, preferences and handoffs across Claude, Codex and Cursor.
Search Viator tours and activities, then pull the details.
Read meeting transcripts, summaries and memos from a Vibe workspace.
Schedule, update and delete Webex meetings and read recordings and transcripts.
Generate a complete B12 website from a prompt in your AI assistant.
Query performance review cycles, feedback, 1:1s and pulse surveys.
Search meeting transcripts, scratchpad notes, tasks and calendar events.
Query your organization's process index, observations and source documents.
Search Wix developer docs and act on live Wix sites.
Draft posts, edit pages, manage comments, install plugins and change user roles.
Run an applicant tracking system from your AI assistant.
Manage a WorkOS workspace.
Search projects, read your inbox, create tasks and bulk-update up to 20 work items.
Search Wyndham hotels by city and dates and pull room types, policies and rates into an AI agent.
Read and build visual pages, tiles, projects and tasks in an xTiles workspace.
Reach 9,000+ apps via Zapier.
Search live ZipRecruiter job listings.
Search Zoom meetings, read recording transcripts and summaries, create Zoom Docs.
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.