UseHourly

app.usehourlyPublished by usehourly.appOfficial publisherv1.1.0Updated Oct 28, 2026

Freelancer time tracking for AI assistants: log time, timers, timesheets, sign-off links, invoices.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFinance

Overview

AI-generated overview

UseHourly is a freelancer time tracker whose MCP server lets an assistant log time, run timers, build timesheets, share sign-off links and prepare invoices.

What you can do
  • Log and edit time entries and notes against clients and projects, and start or stop timers
  • Build weekly timesheets and month or year summaries with per-project totals
  • Create private sign-off links for a client's timesheet
  • Prepare invoices from billable hours and track paid and unpaid status
  • Pull reports and exports for a week, month or custom date range
When to use it
Useful for freelancers and small studios already tracking billable hours in UseHourly who want to dictate entries or ask an assistant to assemble a timesheet, sign-off link or invoice without opening the app.
Requirements
A UseHourly account and a personal access token created under Account > AI assistants (read-only or read and write, with an expiry). Remote clients connect to the Streamable HTTP endpoint with an Authorization Bearer header, or use OAuth login where supported; stdio-only clients run the npm package usehourly-mcp via npx with USEHOURLY_API_TOKEN set. Network access to usehourly.app.
Before you install
The token grants access to your own time and client data, and a read-and-write token lets the assistant create and change entries, timesheets and invoices. Choose read-only where possible and set an expiry. The token is sent as a Bearer credential to usehourly.app, so keep it out of shared configs and logs.

Installation

In SourceWeft

  1. Open UseHourly in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.usehourly%2Fusehourly/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "usehourly": {
      "type": "http",
      "url": "https://usehourly.app/api/mcp"
    }
  }
}

README

UseHourly

The free, open-source time tracker your AI assistant can use. Connect Claude, ChatGPT, Cursor or any MCP assistant and say "log 3 hours on Acme, then make this week's timesheet for sign-off". Or log your day in seconds yourself: type 1.5, 1:30 or 90m, press Enter, done.

Live: https://usehourly.app · Free to use, no paywall, no ads.

[smithery badge]

https://github.com/Zontak-LLC/usehourly/raw/main/public/landing/assistant-demo.mp4

[The weekly timesheet]

What it does

  • Quick entry. Pick a project, type the time the way you would say it, add a note. Or press Start and let the timer count.
  • Weekly timesheet. Every project and every day in one editable grid. Fill several days at once, add more entries to a day, move an entry to another date.
  • Month calendar with per-project totals.
  • Invoices. Turn billable hours into a PDF invoice, track paid and unpaid, re-download any time.
  • Year summary. Hours, earnings, invoiced and received by quarter and month, ready for your accountant.
  • Export. Excel for any week, month or custom date range (for example March 3 to April 20), and one zip with everything: every client, all time.
  • Try it first. "Try it with sample data" on the home page opens a throwaway account filled with a month of work. No sign-up; keep it with one click if you like it.
  • Switching from Toggl or Clockify? Import their CSV export from the Account page. Clients and projects are created for you, and importing the same file twice adds nothing.
  • AI first: works with your assistant (MCP). Any MCP client (Claude, Cursor, VS Code, ChatGPT, your own agent) can log time, start timers, build a client's timesheet, create a private sign-off link and prepare invoices. See below.
  • Free calculator. Hours calculator: add up times and get decimal hours, no account needed.
  • Your data is yours. Per-user isolation; everything you log can be exported at any time.

Use it from any AI assistant (MCP server)

UseHourly runs a remote Model Context Protocol server at https://usehourly.app/api/mcp (Streamable HTTP). It has 32 tools for projects, clients, time entries, timers, timesheets, invoices and reports; each one runs as you, so it only sees your own data. Create a token on Account > AI assistants (read-only or read and write, with an expiry), then:

bash
claude mcp add --transport http usehourly https://usehourly.app/api/mcp --header "Authorization: Bearer <your token>"

That example is for Claude Code. Other clients just need the URL and an Authorization: Bearer <token> header in their MCP settings.

Cursor (~/.cursor/mcp.json):

json
{ "mcpServers": { "usehourly": { "url": "https://usehourly.app/api/mcp", "headers": { "Authorization": "Bearer <your token>" } } } }

VS Code (.vscode/mcp.json):

json
{ "servers": { "usehourly": { "type": "http", "url": "https://usehourly.app/api/mcp", "headers": { "Authorization": "Bearer <your token>" } } } }

For clients that can only run local (stdio) servers, such as Claude Desktop, there is a small bridge published on npm (usehourly-mcp): set the command to npx with args ["-y", "usehourly-mcp"] and USEHOURLY_API_TOKEN to your token.

Then ask: "Log 2 hours on the Acme website for yesterday" or "Make an invoice for Acme for September."

Stack

Next.js 16 (App Router) · React 19 · Tailwind CSS v4 · shadcn/ui · NextAuth v5 (credentials) · tRPC v11 · Prisma 7 with Cloudflare D1 · Vitest · Biome · deployed to Cloudflare Workers with OpenNext.

Run it locally

You need Node 22+.

bash
npm install                 # also runs `prisma generate`
cp wrangler.example.jsonc wrangler.jsonc   # then set account_id and database_id (see Deploy)
# .env.local and .dev.vars (keep the two in sync):#   AUTH_SECRET=<a long random string, e.g. `openssl rand -base64 32`>#   AUTH_URL=http://localhost:3028
npm run d1:migrate:local    # create the local D1 databasenpm run dev                 # http://localhost:3028

Register an account on the sign-up page and you are in.

bash
npm test                    # scenario tests (Vitest)npx biome check             # lint and formatnpx tsc --noEmit            # type check

Deploy

It runs on Cloudflare Workers with a D1 database:

  1. cp wrangler.example.jsonc wrangler.jsonc and fill in your Cloudflare account id and a D1 database (npx wrangler d1 create usehourly-db). wrangler.jsonc is git-ignored, so your ids stay out of the repo.
  2. Put your public address in .env.production.local: NEXT_PUBLIC_APP_URL=https://app.example.com (it is baked into the build) and set the same value as AUTH_URL in wrangler.jsonc.
  3. npm run d1:migrate:remote
  4. npx wrangler secret put AUTH_SECRET
  5. npm run deploy

Email (optional)

Password reset and email confirmation need an email service. UseHourly sends through Resend: verify your sending domain there, then set two values on the Worker:

bash
npx wrangler secret put RESEND_API_KEYnpx wrangler secret put EMAIL_FROM        # for example: UseHourly <[email protected]>

Without them the app works as before, and the forgot-password page says email isn't set up.

Deploy from CircleCI

.circleci/config.yml runs the checks on every push and, on main, applies the D1 migrations and deploys. The deploy token is a secret, so keep it out of the project settings: create a context named usehourly-production (Organization Settings > Contexts), add an expression restriction pipeline.git.branch == "main", and put the token in it. Only the deploy job on main can read it.

Context variableValue
CLOUDFLARE_API_TOKENa token with Workers Scripts: Edit and D1: Edit

In the CircleCI project settings add these environment variables:

VariableValue
CLOUDFLARE_ACCOUNT_IDyour Cloudflare account id
D1_DATABASE_IDthe id of your D1 database
APP_URLyour public address, for example https://app.example.com

Optional: WORKER_NAME, D1_DATABASE_NAME, CUSTOM_DOMAIN. AUTH_SECRET stays a Worker secret (npx wrangler secret put AUTH_SECRET, once); CI never sees it. scripts/ci-wrangler-config.mjs writes wrangler.jsonc from these variables, so no account ids live in the repository.

Support

UseHourly is free. If it saves you time you can sponsor it on GitHub.

Supporters

Thank you to everyone who helps keep UseHourly free:

Be the first: sponsor UseHourly on GitHub.

Credits and license

Built on the excellent next-shadcn-admin-dashboard template by Mohammed Arham Khan.

Released under the MIT License. The code is open; the name "UseHourly" and its logo are not part of the license.

Source: README.md at commit 67ef879

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v1.1.0LatestOct 20, 2026
  2. v1.0.1Oct 17, 2026
  3. v1.0.0Oct 17, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts