Scoro MCP server

What the model can do

Scoro work management: projects, tasks, time entries, contacts, people and invoices, the comments on a task; can comment on a task, log time, change a task (name, status, owner, due date, completion), create or change a project, add or change a contact, and delete a task or a time entry.

Reads

• scoro_projectsProjects in Scoro: number, name, client company, status, manager, start and deadline, tags.
• scoro_tasksTasks in Scoro: name, project, status, due date, priority, assignees, planned and actual hours.
• scoro_task_commentsThe comments on one Scoro task, oldest first as Scoro returns them, as plain text with the author's user id.
• scoro_time_entriesTime entries in Scoro with hours, person (user id), task, description and billed state, and the total hours over what was returned.
• scoro_contactsContacts in Scoro, companies and people: name, type, position, whether client or supplier, tags.
• scoro_usersPeople with a Scoro login: user id, name, email, position, active.
• scoro_invoicesInvoices in Scoro: number, client, project, status, currency, total, paid and outstanding amounts, dates, whether sent.

Acts, when you ask

These change something in Scoro. 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.

• scoro_add_task_commentAdds a comment to a Scoro task, as the Scoro user named by user_id (the author; find it with scoro_users, and use the person who asked…
• scoro_log_time_entryLogs a time entry in Scoro against a task, for the Scoro user named by user_id (find it with scoro_users; the person the time belongs to…
• scoro_update_taskChanges an existing Scoro task: its name, description (replaces the old one), status, owner, priority, start or due time, project…
• scoro_create_projectCreates a new project in Scoro with a name, and optionally the client company, project manager, status…
• scoro_update_projectChanges an existing Scoro project: its name, status (for example completed or cancelled), manager, deadline, client company, privacy or description…
• scoro_create_contactAdds a contact to Scoro: a company, or a person with a first and last name, optionally with a position, one email, one phone…
• scoro_update_contactChanges an existing Scoro contact's name, last name, position, or client and supplier flags.
• scoro_delete_taskPermanently deletes a Scoro task, and with Scoro's Subtasks feature on, all of its subtasks too.
• scoro_delete_time_entryPermanently deletes one Scoro time entry.

Connect it

First connect Scoro on Dashboard → Connections, then add Memtro to your client once. The Scoro tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

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 Scoro 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

• › How many hours were logged on the Northwind website project this month?
• › Which tasks on the Acme rebrand are overdue?
• › Which Scoro invoices still have money outstanding?
• › Log 2 hours against the BigCo onboarding task for me
• › Move the homepage copy task to Friday and give it to Tom Hughes

Questions

Is this an official Scoro MCP server?

No. It is Memtro's MCP server with Memtro's Scoro connector behind it: the connector reads Scoro through its API with the credentials you connect on Dashboard → Connections, and Scoro 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 Scoro?

Only when you ask, and only what it has been granted: add a comment to a Scoro task; log a time entry against a Scoro task; change a Scoro task's name, description, status, owner, priority, dates, project or completion; create a Scoro project; change a Scoro project's name, status, manager, deadline or client; add a company or person contact in Scoro; change a Scoro contact's name, position or client and supplier flags; delete a Scoro task (and its subtasks), permanently; delete a Scoro time entry, permanently. 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.

Other MCP servers · Work management

• Clio Manage MCP server
• Linear MCP server
• Jira MCP server
• Asana MCP server
• monday.com MCP server
• Airtable MCP server