Circleback MCP server
Circleback in any MCP client, through Memtro: Circleback does not publish this server. Memtro's Circleback connector reads Circleback through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Circleback meeting notes: meetings with attendees, notes and action items, full-text search, one meeting in full, action items by assignee, tags, people and folders; and creating, completing, reassigning and deleting action items, renaming, re-noting, tagging, importing, sharing and deleting meetings, and managing tags and folders.
Reads
circleback_list_meetingsRecent Circleback meetings, newest as Circleback returns them: name, date, length, attendees, tags, a short excerpt of the notes and the action items.circleback_search_meetingsSearch Circleback meetings by words in their names and notes, e.g. 'pricing' or a customer's name.circleback_get_meetingOne Circleback meeting in full: the notes (to 8,000 characters), attendees, tags and action items.circleback_list_action_itemsOpen action items from Circleback meetings, with title, description, assignee name and the meetings they came from.circleback_list_tagsEvery Circleback tag this key's user can use, with its id and description.circleback_list_peoplePeople who attend this key's user's Circleback meetings, most recent meeting first: profile id, name, title, company and email.circleback_list_foldersCircleback folders this key's user can see: id, name, type, visibility, the user's access and the workspace id.
Acts, when you ask
These change something in Circleback. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
circleback_create_action_itemCreates an action item in Circleback, owned by this key's user and tied to no meeting.circleback_update_action_itemChanges one Circleback action item: mark it DONE or back to PENDING, retitle it, rewrite its description, or assign it to a person…circleback_delete_action_itemPermanently deletes one Circleback action item for everybody who can see it.circleback_update_meetingChanges one Circleback meeting for everybody it is shared with: rename it, replace its notes (notes) or add to the end of them (append_notes)…circleback_import_meetingImports a meeting held elsewhere into Circleback with its notes, and optionally its date, attendees (email required)…circleback_share_meetingChanges who can open one Circleback meeting: gives each named person (by email, which may be outside the company, or by profile id) Editor…circleback_delete_meetingPermanently deletes one Circleback meeting, its notes, transcript and recording, for everybody it was shared with.circleback_create_tagCreates a Circleback tag for tagging meetings.circleback_update_tagRenames a Circleback tag or changes its description, on every meeting that carries it.circleback_delete_tagPermanently deletes a Circleback tag and removes it from every meeting it was on.circleback_create_folderCreates a shared folder in a Circleback workspace (workspace id from circleback_list_folders).circleback_update_folderRenames a Circleback folder or changes its description, visibility, colour or icon.circleback_delete_folderPermanently deletes a shared Circleback folder for everybody in it.
Connect it
First connect Circleback on Dashboard → Connections, then add Memtro to your client once. The Circleback tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Circleback connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › What did we agree with Northwind on Tuesday?
- › What are my open action items?
- › Which meetings this month mentioned pricing?
- › Which action items from our meetings are still unassigned?
- › Assign the pricing deck action item from Tuesday to Priya Sharma
Questions
- Is this an official Circleback MCP server?
- No. It is Memtro's MCP server with Memtro's Circleback connector behind it: the connector reads Circleback through its API with the credentials you connect on Dashboard → Connections, and Circleback publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Circleback?
- Only when you ask, and only what it has been granted: create an action item owned by you; mark an action item done or pending, retitle it, or assign or unassign it; delete an action item; rename a meeting, replace or add to its notes, or add or remove its tags; import a meeting from elsewhere with its notes, attendees and transcript; share a meeting with people by email or profile, or remove their access, optionally emailing them; delete a meeting you own; create, rename or delete a tag; create, rename, restyle or delete a shared folder. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.