Using it from Claude
If you already work in Claude, you can log time, work your Sales opportunities and read reports there instead of opening the app. You connect it once, sign in with your normal Google account, and everything Claude does afterwards runs as you, with exactly the access you already have.
There’s nothing to install and no key to copy.
Connecting
Section titled “Connecting”The address to connect to is:
https://work.cloverhound.com/mcpClaude Desktop and claude.ai
Section titled “Claude Desktop and claude.ai”-
Open Settings → Connectors, then choose Add → Add custom connector.
-
Name it and paste the address.
The name is only the label in your connectors list, so Work is fine. The second field takes the address above.
Leave Advanced settings alone — the OAuth client ID and secret are for servers that issue them in advance, and this one registers Claude automatically. Leave Individual sign-in switched on: that’s what makes the connection yours, so Claude sees exactly your access and nobody else’s.
-
Sign in, then read the consent screen before approving.
See Before you approve — it’s worth the few seconds.
One connection covers Claude Desktop and claude.ai together; you don’t repeat it on each machine. If you come back later and it says you aren’t connected yet, Connect starts the same sign-in again.
Claude Code
Section titled “Claude Code”claude mcp add --scope user timeler --transport http https://work.cloverhound.com/mcpThen run /mcp, pick timeler, and finish signing in.
What you can ask for
Section titled “What you can ask for”You don’t call anything by name. Ask in plain language:
| Ask | What happens |
|---|---|
| “What projects can I log to?” | Lists the projects you’re assigned to. |
| “Log 2 hours on the Acme migration for yesterday” | Writes the entry. |
| “I worked 9:00 to 11:30 on the website redesign” | Works out the duration for you. |
| “Change Tuesday’s entry to 3 hours and make it non-billable” | Edits it. |
| “What did I log last week?” | Lists your entries with the total. |
| “How many hours did I bill in July?” | Your own summary, split billable and not. |
| “Which projects are over budget?” | Budget consumption per project. |
| “Billable dollars per engineer this year” | Totals hours and billed value per person, by the server, in one call. |
| “Which fixed-fee projects closed this year ran over budget?” | Budget vs value of work (hours × rate, plus billable expenses) per project, most over first. |
| “Which projects have no linked opportunity?” | The clean-up list. |
| “Show each engineer’s effective rate last quarter, by customer” | Team report with billable amount, effective rate and target, broken down by customer. |
Notice what comes back with the answer — the project, the customer, the number of entries behind the total, and what share of the budget it represents. Asking a follow-up (“who logged what, and when?”) works the same way.
It can also look up Service Desk tickets in the queues you can reach. Creating and updating them isn’t supported.
Sales opportunities
Section titled “Sales opportunities”If you’re in the Sales module, Claude can work your deals too:
| Ask | What happens |
|---|---|
| “What’s closing this month?” | Lists open deals by close date. |
| “Find the Acme renewal” | Searches deal, company, contact, note and next-step text. |
| “Show me everything on the Globex deal” | The full record, with linked projects and recent notes. |
| “Create a $40k opportunity for Acme, closing end of Q4” | Creates it, owned by you. |
| “Push the Initech deal to Negotiation and set the next step to send the SOW” | Moves the stage and updates the field. |
| “We won the Acme deal” | Marks it won with today’s close date. |
| “We lost Globex on price” | Marks it lost and records the reason. |
| “Which open deals include Dev or MS work?” | Filters by service type and totals each type. |
| “What have we won that’s still being delivered?” | Lists Active Won deals: won, not yet closed. |
| “Mark the Acme deal as Pro Svc and Dev” | Sets the deal’s service types. |
| “How’s my pipeline this quarter?” | Your own deals: open, won, lost, weighted value and win rate. |
| “Show the pipeline by quarter for the last two years” | Workspace-wide, for Sales admins. |
A few rules follow the deal:
- Editing a Salesforce-synced deal takes it over. Any change, stage move, win or loss makes the app its owner, and the nightly Salesforce sync stops updating it. That’s the same as editing it in the app. Claude checks with you first and tells you when it happened.
- Winning doesn’t set up delivery. Creating or linking the delivery project and the fulfillment step still happen on the deal in the app.
- Opportunities can’t be deleted from Claude. Close them as lost instead.
- Workspace-wide pipeline numbers are for Sales admins, the same as the Reports pages. Everyone in Sales can ask about their own pipeline.
- Settled deals older than two years are left out of a plain list, the same as the Opportunities page. Searching for one by name, or asking for a date range, reaches them.
Project notes
Section titled “Project notes”Claude can read a project’s internal notes and add new ones, attributed to you:
| Ask | What happens |
|---|---|
| “What’s been noted on the Acme migration project?” | Lists the project’s notes, oldest first. |
| “Add a note to Acme migration: customer re-signed the SOW for phase 2” | Adds the note under your name. |
Editing or deleting a note is done on the project page, not through Claude. These permissions were added later: if you connected before, disconnect and reconnect to pick them up.
Ticket contents never leave the app
Section titled “Ticket contents never leave the app”Ticket tools return metadata only — queue, state, priority, owner, responsible, company, requester, dates and SLA clocks. The subject line and every note and reply stay behind, for every ticket in every queue.
So Claude can tell you what’s breaching SLA, what’s unassigned, or how much is open for a company. It cannot tell you what any ticket says. To read one, open it in the app.
You can still search: a query matches a ticket number, or a word in a subject Claude never gets to see. It reports which tickets matched, not what they say.
Tickets in restricted queues are narrower again — number, queue, state, responsible and dates — and a query searches their numbers only, never their subjects. That holds even if you hold a grant on the queue and can read every word in the app: the restriction is about where the text may travel, not about who may read it.
The same rule follows tickets into the time tools. A time entry linked to a ticket carries the ticket’s number, never its subject.
Deciding what it can do without asking
Section titled “Deciding what it can do without asking”Once connected, the connector’s page in Settings → Connectors has a Tool permissions section, split in two:
- Read-only tools — looking things up. Set to Always allow by default, so questions get answered without interruption.
- Write/delete tools — logging time, editing an entry, deleting one, creating, editing, moving, winning or losing an opportunity, and adding a project note. Set to Needs approval by default, so Claude asks before each.
That split isn’t something you have to set up; the connector labels each tool as read-only or not, and Claude groups them accordingly. You can override any single one — always allow, ask each time, or never.
Things worth knowing before you rely on it
Section titled “Things worth knowing before you rely on it”Deleting is permanent. Time entries are deleted outright — there’s no archive and no undo. Claude will confirm with you first, but once it’s gone it’s gone.
Billable time may round up. If a project has a billing increment, a 45-minute billable entry can be stored as 60. Claude tells you when what was saved differs from what you asked for.
Some projects need a note. The entry is refused without one, and Claude will ask you for it.
Say the range out loud. Reports default to the last 30 days and the entry list to the last 14, so ask for “last quarter” explicitly rather than assuming. Every answer states the range it actually covered — worth reading, because an empty result can mean “nothing in that window” rather than “nothing at all”.
Reports show what you can already see. If you aren’t a Time admin, a team report covers those people’s hours on your projects, not their totals. The answer says so; repeat that when you pass the numbers on.
Before you approve
Section titled “Before you approve”The consent screen asks you to trust an application with your timesheet, so it’s worth a few seconds.
An application’s name is chosen by whoever registered it and isn’t verified by anyone — someone could register a connector calling itself “Claude”. What is checked, and what the screen shows you, is the address your approval is sent to:
Approving sends an authorization code to
https://claude.ai. Only approve if you started this from that application.
What it can and can’t do
Section titled “What it can and can’t do”Approving grants:
| Permission | What it covers |
|---|---|
| Read your time entries | Your own entries |
| Create, edit and delete your time entries | Your own entries — deleting is permanent |
| Read the reports you can already see | Narrowed to your projects unless you’re a Time admin. Includes budget vs work, invoiced amounts and expenses on those projects |
| Read the tickets you can already see | Only queues you can reach, and metadata only — never subjects or replies |
| Read the Sales opportunities and pipeline you can already see | Every deal a Sales member can see in the app; workspace-wide reports only if you’re a Sales admin |
| Create and update Sales opportunities | Create, edit, move stage, win and lose. No deleting |
| Read the internal notes on projects you can already see | Notes on the projects you can open in the app |
| Add internal notes to projects you can already see | New notes under your name. No editing or deleting |
| Stay connected | Saves you re-approving every hour |
A permission only ever narrows what’s possible. It can’t show Claude anything you couldn’t already open yourself: not other people’s entries, not projects you aren’t assigned to, not another organization.
It also can’t create or edit tickets, change anyone else’s time, delete an opportunity, create delivery projects from a won deal, touch billing, invoicing or quotes, alter settings, or manage users.
Disconnecting
Section titled “Disconnecting”There are two halves, and only one of them is the one that matters.
Removing the connector in Claude — Settings → Connectors → Disconnect, or
claude mcp remove timeler in Claude Code — stops Claude from asking.
To stop the app from answering, open Profile → Connected apps and press Disconnect there. That’s the one to use if you think it was approved by mistake, or it’s on a machine you no longer have. It kills the access token, the refresh token and any pending authorization immediately, rather than at the end of the hour.
An operator can do the same across a whole organization — which is what you want when someone has left.
If it doesn’t work
Section titled “If it doesn’t work”It says it needs authentication and nothing happens. Finish signing in on the browser window it opened. If none opened, check for a blocked pop-up.
It connects but has no tools. Disconnect and reconnect. If it persists, tell an admin — the server records what happened.
It says Sales isn’t available. Sales has to be switched on for your workspace, and you need a role in it. If you have one and still see this, you may have connected before Sales was added: disconnect and reconnect.
It can’t see any projects. You may not be assigned to any yet. Check the Time module in the app; the connector only offers what you can log against.
It says you logged no time when you know you did. Ask which dates it looked at. It’s almost always a range that didn’t reach far enough back.