Skip to content
Everhour logo

Everhour MCP server

Time tracking software that integrates into project management tools to track billable hours, set budgets, and monitor spending.

Everhour is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
4
Works with
Any MCP client
Auth
API key
License
MIT, open source
Updated
September 2026

About the Everhour MCP server

Connect Everhour once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Everhour and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Everhour tools your AI can run

Once connected, your assistant can call any of these Everhour actions by asking in plain language.

  • Create Task

    Creates a new task in a project.

    2 fields

  • Start Timer

    Starts a timer for a specific task.

    1 field

  • Stop Timer

    Stops the currently running timer. Fails if no timer is currently active.

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Give your assistant Everhour

Connect Everhour once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Everhour MCP, answered.

No. That is the point of it. One Activepieces server exposes Everhour alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Everhour in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 4 tools, including Create Task, Start Timer, Stop Timer, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.