Runn MCP server
Runn in any MCP client, through Memtro: Runn does not publish this server. Memtro's Runn connector reads Runn 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
Runn resource planning: people, projects and clients; who is assigned to which project, in which role and for how many hours a day; time actually worked; leave; project notes and milestones. Can add a project note or time worked, create or delete an assignment, book or delete leave, create a project or client, rename, confirm or archive a project, and add a milestone, each only when asked.
Reads
runn_list_peopleRunn people: name, work email, team, tags and whether archived.runn_list_projectsRunn projects: name, client id, team, confirmed or tentative, archived, pricing model, budget and expenses budget, manager ids and tags.runn_list_assignmentsRunn assignments (planned work): person, project, role, start and end dates, hours per day, billable, phase and note.runn_list_actualsRunn actuals (time worked) per day: person, project, role and billable and non-billable hours and notes, with totals.runn_list_leaveRunn leave bookings: person, first and last day, hours a day for partial days.runn_project_notes_and_milestonesOne Runn project's notes (text, who wrote it, when) and milestones (title, date, icon, note).runn_referenceRunn clients (name, website, archived), roles (name, default hour cost, standard rate and how many people hold it) or teams, by id.
Acts, when you ask
These change something in Runn. 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.
runn_add_project_noteAdd a note to a Runn project.runn_add_timeAdd time worked in Runn for one person on one project and role on one day.runn_create_assignmentAssign a person to a Runn project in a role for every working day from start to end, at the same hours a day.runn_delete_assignmentDelete a Runn assignment.runn_book_leaveBook leave in Runn for a person from start to end, whole days or hours_per_day for partial days.runn_delete_leaveDelete a Runn leave booking.runn_create_projectCreate a Runn project for a client, tentative unless confirmed is true.runn_update_projectChange a Runn project's name, confirmed or tentative state, archived state, client, team or managers (manager_ids replaces the list).runn_create_clientCreate a Runn client.runn_add_milestoneAdd a milestone to a Runn project on a date, with an icon (start, end, flag, dollar or warning) and an optional note.
Connect it
First connect Runn on Dashboard → Connections, then add Memtro to your client once. The Runn 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 Runn 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
- › Who has capacity next month?
- › Who is assigned to the Northwind rebuild, and for how many hours a day?
- › How many billable hours did the design team log last week?
- › Who is on leave in the week of 14 December?
- › Book Maya Okafor on leave from 22 to 24 December
Questions
- Is this an official Runn MCP server?
- No. It is Memtro's MCP server with Memtro's Runn connector behind it: the connector reads Runn through its API with the credentials you connect on Dashboard → Connections, and Runn 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 Runn?
- Only when you ask, and only what it has been granted: add a note to a project; add time worked for a person on a project (adds to what is there); assign a person to a project for a date range and hours a day; delete an assignment (permanent); book leave for a person (merges with overlapping leave); delete a leave booking (permanent); create a project for a client; rename, confirm or tentative, archive or unarchive a project; create a client; add a milestone to a project. 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.