Skip to main content
The Everhour MCP server lets an AI assistant read and write your Everhour data on your behalf — start a timer, log time, check your timesheet, or find a task — without you switching tabs or memorizing IDs. You describe what you want in plain language and the assistant calls the right tool. It implements the Model Context Protocol (MCP), an open standard for connecting AI clients to external tools and data. Any MCP-capable client can connect.

​
What you can do

Once connected, your assistant has access to 28 tools covering everyday time tracking:
  • Track time in real time — start, stop, and check your running timer, with or without a task attached.
  • Log and edit time — add entries (in seconds), fix a duration, clear a wrong entry, or log time retroactively.
  • Review timesheets — read your weekly timesheet with daily totals and a per-task breakdown, or raw entries over any month.
  • Find work across tools — search tasks, list recently tracked tasks, and resolve a task ID or URL from Asana, Jira, GitHub, Linear, and other integrations to the matching Everhour task.
  • Keep a shortlist — pin and unpin favorite tasks, and read the pinned list back.
  • Read projects, clients, and team — list and fetch projects, clients, and team members.
  • Report on the team — pull hours by project or member, project budgets, time off, and weekly capacity over any date range (subject to your role).
See the tools reference for the full list.

​
Interactive cards

Some tools return an interactive card alongside their text answer: a timer with a Stop button, a task list where every row starts tracking, a full task card, and a timesheet you can switch between a month grid and a week list. Actions inside a card call Everhour directly, so a timer you stop there is stopped everywhere. Cards render in clients that support MCP Apps. Everywhere else the same answer arrives as text, with nothing missing. See the card reference for which tool returns which card.

​
Authentication

Clients connect with OAuth 2.1. You add the server URL and approve access in your browser — no app to create and no credentials to copy, because Everhour registers your client automatically. The access token is short-lived and refreshes on its own. See Connect an MCP client. For clients that can’t do OAuth, or for headless automation, you can authenticate with an Everhour API key in an X-Api-Key header instead. The key is long-lived and grants full account access, so prefer OAuth where it’s available.
Whichever method you use, the assistant can only do what your Everhour role allows — the same permissions that govern the REST API. See Data, privacy, and permissions for what Everhour receives, how long access lasts, and which tools prompt before they run.

​
Requirements

  • An active Everhour account, on any plan. The MCP server is included in every plan at no extra cost.
  • An MCP-capable AI client (see supported clients).

​
Server details

Endpoint

POST https://api.everhour.com/mcp

Transport

Streamable HTTP

Protocol

MCP 2025-06-18, JSON-RPC 2.0

Authentication

OAuth 2.1 (or X-Api-Key for manual setups)

​
Next steps

Connect an MCP client

Set up Claude, ChatGPT, Cursor, and other clients.

Everhour in Claude

Ask for your time in plain language, and see what the cards do.

Tools reference

Every tool the assistant can call, and the cards they return.

Data, privacy, and permissions

What Everhour receives, what your role allows, and how access ends.