airfocus MCP server
airfocus in any MCP client, through Memtro: airfocus does not publish this server. Memtro's airfocus connector reads airfocus 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
airfocus product management: workspaces with their statuses, items (features, ideas, epics, tasks, bugs) by status, assignee, text or last update with descriptions, parents and children, comments on an item, and team members; when you ask, can create, edit, archive or delete items, add or delete comments, watch or unwatch items, and move items to another workspace.
Reads
airfocus_list_workspacesAirfocus workspaces you can see: name, alias, what kind of item they hold, item count, your permission and their statuses.airfocus_list_itemsItems in one airfocus workspace (features, ideas, epics, tasks, bugs): alias, name, status by name, assignees, progress, comment count…airfocus_get_itemOne airfocus item in full: description, status, assignees, parents and children, progress, comment, link and attachment counts.airfocus_list_commentsComments on one airfocus item, with author user id and time, as markdown cut to 1000 characters each.airfocus_list_usersAirfocus team members: user id, name, role (admin, editor, contributor) and whether disabled or pending.
Acts, when you ask
These change something in airfocus. 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.
airfocus_create_itemCreates an item in an airfocus workspace, visible to everyone with access to it; assignees may be notified by airfocus.airfocus_update_itemChanges an airfocus item: name, status, assignees (replaces the list), description (replaces it), or archives or un-archives it.airfocus_delete_itemPermanently deletes an airfocus item with its comments and links, for everyone.airfocus_add_commentAdds a comment to an airfocus item as the API key's user, visible to everyone in the workspace; watchers of the item may be notified.airfocus_delete_commentPermanently deletes a comment on an airfocus item.airfocus_watch_itemsMakes the API key's user watch (or, with watch false, stop watching) the given airfocus items in one workspace…airfocus_move_itemsMoves the given airfocus items from one workspace to another.
Connect it
First connect airfocus on Dashboard → Connections, then add Memtro to your client once. The airfocus 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 airfocus 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 changed on the roadmap this week?
- › Which bugs are assigned to Dan Fletcher and still open?
- › What do the comments on DEV-123 say?
- › What are the child items of the onboarding epic?
- › Archive the old pricing experiment idea.
Questions
- Is this an official airfocus MCP server?
- No. It is Memtro's MCP server with Memtro's airfocus connector behind it: the connector reads airfocus through its API with the credentials you connect on Dashboard → Connections, and airfocus 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 airfocus?
- Only when you ask, and only what it has been granted: create an item in a workspace; edit, re-status, re-assign or archive an item; delete an item; add a comment to an item; delete a comment; watch or unwatch items; move items to another workspace. 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.
