How to connect Everhour to OpenClaw
Connect Everhour to OpenClaw with ClawLink: paste your Everhour key once and 38 tools work from chat. No MCP server to run, nothing stored on your machine.
EverhourAPI KEYMCPEverhour is a time tracking and expense management software equipped with budgeting, forward resource planning, expense tracking, dashboards, and reports.. Once connected, OpenClaw can read and act on Everhour from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Everhour access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Everhour setup: install one ClawHub skill, connect Everhour in the browser, and OpenClaw can call real Everhour actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Everhour.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Everhour
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Everhour?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Everhour in the ClawLink dashboard — paste your Everhour API key once.
Verify the connection by asking OpenClaw:
Use Everhour to client list and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Everhour is connected in the dashboard, that agent calls the same 38 Everhour tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Everhour MCP for OpenClaw
Looking for a Everhour MCP server for OpenClaw? ClawLink connects Everhour to OpenClaw and exposes 38 Everhour tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Everhour integration works the same way.
What the OpenClaw Everhour integration can do
38 Everhour tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 38.
30 of 38 Everhour tools for OpenClaw
| Tool | What it does |
|---|---|
Client list everhour_client_list | Retrieves all clients in the Everhour workspace |
Expenses list everhour_expenses_list | Lists expense records from your Everhour workspace |
Get client everhour_get_client | Retrieve a specific client by ID |
Get project everhour_get_project | Retrieve a specific project |
Get section everhour_get_section | Retrieve details of a specific section by its ID |
Get timecard everhour_get_timecard | Retrieve a specific timecard for a user on a date |
Get user profile everhour_get_user_profile | Retrieve profile information of the authenticated user |
Get webhook everhour_get_webhook | Retrieve details of a specific webhook by its ID |
List expense categories everhour_list_expense_categories | Lists all expense categories available in your Everhour account |
List hooks everhour_list_hooks | Lists all webhooks configured for the Everhour account |
List invoices everhour_list_invoices | Retrieves all invoices from your Everhour workspace |
List projects everhour_list_projects | List all Everhour projects accessible by the authenticated user |
List sections everhour_list_sections | Lists all sections within a specific Everhour project |
List tags everhour_list_tags | List all tags in the Everhour workspace |
List team members everhour_list_team_members | Retrieves all team members in the authenticated Everhour workspace |
List teams everhour_list_teams | Retrieves information about the authenticated team/workspace in Everhour |
List timecards everhour_list_timecards | Retrieve all team timecards with optional date filtering |
List user timecards everhour_list_user_timecards | Retrieve timecards for a specific user with optional date filtering |
List user timesheets everhour_list_user_timesheets | Retrieve timesheets for a specific user |
Client create everhour_client_create | Creates a new client in Everhour for tracking billable work, invoicing, and project organization |
Clock in everhour_clock_in | Clock in a user for time tracking |
Clock out everhour_clock_out | Clock out a user for time tracking |
Create webhook everhour_create_webhook | Create a new webhook for event notifications in Everhour |
Project create everhour_project_create | Create a new project in Everhour |
Request timesheet approval everhour_request_timesheet_approval | Request approval for a timesheet or approve a week (for admins) |
Section create everhour_section_create | Create a new section in a project |
Task create everhour_task_create | Creates a new task in an Everhour project |
Timer start everhour_timer_start | Start a new timer for a task |
Update client everhour_update_client | Update an existing client in Everhour |
Update project everhour_update_project | Updates an existing Everhour project's settings |
Try it: find the Everhour tool you need
Browse the 30 Everhour tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Everhour to client list and walk me through the result in plain English.
Use Everhour to expenses list and walk me through the result in plain English.
Pull the relevant data from Everhour, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Everhour, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Everhour working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Everhour API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Everhour account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Everhour. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Everhour actions to the runtime in a format your agent can reliably use. | 38 tools for Everhour are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Everhour to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Everhour in the browser, and the 38 tools above work from chat. There is no SDK and no config file, and the Everhour key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Everhour skill but can't call the tools
The ClawHub skill teaches OpenClaw about Everhour, but the calls run through the ClawLink plugin and your connected account. Make sure Everhour is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Everhour from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Everhour tools
Everhour tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Everhour call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Everhour returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Everhour has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Everhour integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Everhour: link your Everhour account once in the browser and OpenClaw can call the Everhour API through 38 ready-made tools — no custom code or token handling.
How do I add Everhour to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Everhour skill from ClawHub, then you click Connect in the dashboard to authorize Everhour. OpenClaw calls the tools from the next message — no config files, and the Everhour key you paste is stored server-side instead of in your environment.
How long does it take to connect Everhour to OpenClaw?
About two minutes. Sign in, click Connect next to Everhour in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Everhour up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Everhour working from chat.
OpenClaw installed the Everhour skill but can't call the tools
The ClawHub skill teaches OpenClaw about Everhour, but the calls run through the ClawLink plugin and your connected account. Make sure Everhour is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
