How to Connect Everhour to Claude (and What It Can't Do)
Everhour’s whole design is to disappear into the project tool you already use — a timer button inside Asana, estimates next to Jira tickets, budgets living alongside ClickUp tasks. So “connecting Everhour to Claude” is really about giving Claude the data layer underneath those embeds: the estimates, logged time, and client budgets Everhour accumulates while your team works where it always has. As of mid-2026 that connection runs through community MCP servers — Everhour doesn’t publish an official one, and there’s no Everhour listing in Claude’s connectors directory — added to Claude as a custom connector on a paid plan, and answering only while a chat is open.
The servers that exist, and what they expose
Two community projects cover most of the ground:
- stefanskiasan/everhour-mcp-server — the most complete option, with 37 tools across projects, tasks (including estimates), time records, timers, sections, clients, and team members. It authenticates with your Everhour API key and, usefully, offers a read-only mode that blocks all write and delete operations — a sane default if you mainly want reporting.
- Npab19/MCP-Everhour — a Dockerized server focused on timers and timecards, built for self-hosted deployments.
Setup follows the usual custom-connector path: get your API key from Everhour’s settings, run the server with it, then add the server in Claude under Settings → Connectors. Paid Claude plan required; that’s true of every custom connector, not just this one.
Questions Everhour’s own reports make you dig for
Everhour is unusually good at storing the estimate-versus-actual picture and only okay at surfacing it the way you think about it. Claude closes that gap conversationally:
“Which Jira tasks are already over their Everhour estimates, and by how much?”
“How much of the Northwind monthly budget is burned so far — billable time only?”
“Log 90 minutes on the onboarding-revamp task for this morning.”
Because Everhour’s records point back at native Asana and Jira items, Claude’s answers come out in the language your team already uses — ticket names, not opaque time-entry IDs. For a retro or a scoping meeting, “pull every task where actuals beat the estimate by 50%+” is a legitimately great prompt.
What stays out of reach
Estimates and budgets are early-warning systems, and early warnings are only useful if something is watching. Nothing in this setup watches. Claude connectors don’t run on schedules and don’t react to events, so:
- The Northwind budget can sail through 80% on a Tuesday night, and nobody hears about it until someone happens to ask.
- Month-end arrives, three people have unlogged days, and the invoice-ready timesheet isn’t ready — Claude would have flagged it, had anyone opened a chat and asked.
- An estimate blows out on a ticket mid-sprint; the PM finds out at the next standup instead of the moment it happened.
There’s also the trust dimension: you’re handing an API key with your Everhour permissions to community code. The read-only mode in stefanskiasan’s server exists precisely because that trade-off deserves care.
The watching job is Carly’s job
Carly is an AI executive assistant whose core trick is acting on triggers in the cloud, around the clock — no chat window, no one prompting. For teams running Everhour-style budgets, that typically means:
- Budget thresholds become alerts: cross 80% on any client budget and the account lead gets an email with the burn detail, minutes later.
- Monday mornings bring last week’s estimate-versus-actual summary, sent (not drafted) via Gmail or Outlook.
- Before invoicing, anyone with missing time gets nudged automatically, so month-end closes without the chase.
You set these up by describing them — “email me when any client budget passes 80%, with the entries behind it” — and Carly interviews you on the specifics, then builds the workflow with you. AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. See integrations and the Everhour integration page.
Chat-based Everhour vs trigger-based Everhour
| Claude + community Everhour MCP | Carly | |
|---|---|---|
| Budget burn and estimate-vs-actual, on demand | Yes (in chat) | Yes |
| Log time and manage tasks by asking | Yes (write mode) | Yes |
| Alerts when a client budget crosses 80% | No | Yes |
| Nudges the team over missing time before invoicing | No | Yes |
| Weekly utilization summary, delivered | No | Yes (emailed via Gmail/Outlook) |
| Read-only safety option | Yes (server flag) | Scoped per workflow |
| Cost of entry | Paid Claude plan + self-hosted server | AI agents from $35/mo |
Frequently Asked Questions
Does Claude integrate with Everhour?
Yes, via community MCP servers — as of mid-2026 Everhour hasn’t shipped an official one and isn’t in Claude’s connectors directory. The most complete option, stefanskiasan/everhour-mcp-server, exposes 37 tools over the Everhour API; you add it to Claude as a custom connector, which needs a paid Claude plan.
Can Claude see the time my team logs inside Asana or Jira?
Yes. Everhour stores that time centrally regardless of which embed captured it, and the MCP servers read it through the Everhour API — so Claude reports on Asana- and Jira-logged hours in terms of the original tasks.
Will Claude warn me when a client budget is nearly spent?
Only if you ask at the right moment. Connectors can’t monitor anything between chats — no schedules, no event triggers. Standing budget alerts are agent-platform territory; Carly watches thresholds and emails you when they trip.
Is there a safe way to try this without write access?
Yes — stefanskiasan’s server has a read-only mode that limits Claude to list and get operations, which is the sensible starting point before you let community code edit time records.
What does this cost end to end?
The community servers are free to run yourself, but Claude custom connectors require a paid Claude plan. On the trigger-based side, Carly’s AI agents start at $35/month, with non-AI workflow steps free and unlimited.
More: Claude connectors · Can Claude send emails · Claude vs Carly · Claude Cowork alternatives · Claude time tracking · Claude + Harvest · Claude + Toggl · Claude + TickTick
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
