Everhour MCP server

What the model can do

Everhour time tracking: the team's time records for a period with totals by person and project, timers running now, projects with budgets, clients, team members, a task search and timesheets; can also start or stop a timer, set, change or delete time, add, change, estimate or delete a task, create, change or archive a project, add or change a client, and submit, approve or reject a timesheet, when you ask.

Reads

• everhour_usersMembers of the Everhour team: name, email, role and status.
• everhour_projectsProjects in Everhour (its own and those synced from Asana, Jira, Trello and others; the id prefix says which) with client…
• everhour_search_tasksFind Everhour tasks by words in their name, optionally within one project, with status, due date and time tracked.
• everhour_timeTime records for the whole team over a period, newest first, with hours, person, task, project and comment, and totals by person and by project.
• everhour_timersTimers running now across the Everhour team: who, on which task, since when.
• everhour_clientsClients in Everhour, with the ids of their projects.
• everhour_timesheetsTimesheet weeks across the Everhour team: timesheet id, person, week and the latest approval action (submitted, approved, rejected, discarded).

Acts, when you ask

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

• everhour_create_taskAdd a task to one of Everhour's own projects (ids starting ev:).
• everhour_create_clientAdd a client in Everhour by name, with no projects attached.
• everhour_start_timerStart an Everhour timer on a task for the connected user, with an optional comment.
• everhour_stop_timerStop the connected user's running Everhour timer; its time is recorded on the timer's task.
• everhour_set_timeSet the time logged on a task for one person and one day in Everhour.
• everhour_update_time_recordChange an Everhour time record (id from everhour_time): its duration, and optionally its date or comment.
• everhour_delete_time_recordDelete an Everhour time record (id from everhour_time).
• everhour_update_taskChange an Everhour task: rename it, close or reopen it, set or clear its due or start date, or replace its description.
• everhour_set_task_estimateSet (or replace) an Everhour task's overall time estimate, in hours.
• everhour_delete_taskPermanently delete an Everhour task together with ALL time logged on it, by everyone.
• everhour_create_projectCreate an Everhour project, as a board or a list, optionally for a client and private to its members.
• everhour_update_projectRename an Everhour project, move it to another client, or change its colour.
• everhour_archive_projectArchive an Everhour project (archived: true) or bring it back (false).
• everhour_update_clientRename an Everhour client, or archive or reactivate it.
• everhour_submit_timesheetSubmit an Everhour timesheet week for approval (the timesheet id is the user id followed by the YYWW week id; see everhour_timesheets)…
• everhour_review_timesheetApprove or reject a submitted Everhour timesheet week (id from everhour_timesheets), with an optional comment.

Connect it

First connect Everhour on Dashboard → Connections, then add Memtro to your client once. The Everhour 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 Everhour 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 logged time on Acme last week?
• › How many hours did Priya Sharma log in October?
• › Who has a timer running right now, and on what?
• › How much of the Northwind budget has been spent?
• › Log three hours on the Northwind design review task for yesterday

Questions

Is this an official Everhour MCP server?

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

Only when you ask, and only what it has been granted: add a task to an Everhour project; add a client in Everhour; start an Everhour timer on a task as the connected user (stops any timer already running); stop the connected user's running Everhour timer; set the time a person logged on a task for a day in Everhour, replacing what was there; change an Everhour time record; delete an Everhour time record; rename, close, reopen or reschedule an Everhour task; set an Everhour task's estimate; permanently delete an Everhour task and all its time records; create an Everhour project; rename an Everhour project, change its client or colour; archive or unarchive an Everhour project; rename, archive or reactivate an Everhour client; submit an Everhour timesheet week for approval; approve or reject an Everhour timesheet. 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