Teamwork.com MCP server
Teamwork.com in any MCP client, through Memtro: Teamwork.com does not publish this server. Memtro's Teamwork.com connector reads Teamwork.com 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
Teamwork.com: projects by status, task lists, tasks by project, assignee, status or text, milestones, time logged, and people. Can create, update, assign, complete, reopen or delete tasks and subtasks, comment, log, edit or delete unbillable time, start a timer, create or edit projects, create task lists, milestones and tags, and complete milestones.
Reads
teamwork_list_projectsProjects in Teamwork.com, by name: status, dates and description.teamwork_list_tasklistsTask lists in one Teamwork.com project: id, name and status.teamwork_list_tasksTasks in Teamwork.com, in one project or across all: name, status, priority, dates and progress.teamwork_list_timeTime logged in Teamwork.com between two dates: who, on what, for how long and whether billable.teamwork_list_peoplePeople in Teamwork.com (account users, collaborators and client contacts): name, email, title and company.teamwork_list_milestonesMilestones in one Teamwork.com project: id, name, deadline and status.
Acts, when you ask
These change something in Teamwork.com. 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.
teamwork_create_taskCreates a task in a Teamwork.com task list, as the key's user, with an optional description, start and due date.teamwork_add_commentAdds a comment to a Teamwork.com task, as the key's user.teamwork_log_timeLogs unbillable time on a Teamwork.com task for the key's user: the date worked, hours and minutes, and what was done.teamwork_update_taskChanges a Teamwork.com task: name, description, start or due date, who is assigned (replaces the list), priority, progress, estimate…teamwork_create_subtaskAdds a subtask under a Teamwork.com task, as the key's user, optionally assigned and dated.teamwork_complete_taskMarks a Teamwork.com task complete, or reopens a completed one with reopen true.teamwork_delete_taskDeletes a Teamwork.com task and all its subtasks.teamwork_create_tasklistCreates a task list in a Teamwork.com project, with an optional description.teamwork_create_projectCreates a Teamwork.com project with a name and optional description and start and end dates.teamwork_update_projectChanges a Teamwork.com project's name, description, or start and end dates.teamwork_create_milestoneAdds a milestone to a Teamwork.com project with a title, a deadline and the people responsible.teamwork_complete_milestoneMarks a Teamwork.com milestone complete.teamwork_start_timerStarts a running timer for the key's user on a Teamwork.com task, unbillable.teamwork_update_timeChanges a logged Teamwork.com time entry: the date, hours and minutes, or description.teamwork_delete_timeDeletes a logged Teamwork.com time entry.teamwork_create_tagCreates a Teamwork.com tag, optionally limited to one project.
Connect it
First connect Teamwork.com on Dashboard → Connections, then add Memtro to your client once. The Teamwork.com 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 Teamwork.com 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 is overdue on the Acme website project?
- › Who logged time on the Northwind rollout this week, and how much was billable?
- › Which tasks are due today across all projects?
- › Create a task in the Launch list on the BigCo project: send the final copy deck, due Friday
- › Mark the homepage review task complete and assign the copy edit to Sam Ortiz
Questions
- Is this an official Teamwork.com MCP server?
- No. It is Memtro's MCP server with Memtro's Teamwork.com connector behind it: the connector reads Teamwork.com through its API with the credentials you connect on Dashboard → Connections, and Teamwork.com 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 Teamwork.com?
- Only when you ask, and only what it has been granted: create a task in a Teamwork task list; add a comment to a Teamwork task; log unbillable time on a Teamwork task; change a task: name, description, dates, assignees, priority, progress, estimate or task list; add a subtask under a task; mark a task complete, or reopen it; delete a task and its subtasks, permanently; create a task list in a project; create a project, or change its name, description or dates; add a milestone to a project, or mark one complete; start a timer on a task, stopping any timer already running; change or delete a logged time entry; create a tag. 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.