[Integrations](https://hourbun.com/integrations)

# [Connect Claude to Hourbun](https://hourbun.com/integrations/claude)

By Fred Wu, maker of Hourbun · Checked 13 November 2026 · [Report a mistake](mailto:support@hourbun.com)

## The short answer

Claude connects to Hourbun as a custom connector: on claude.ai or in the Claude desktop app, open Customize, Connectors, add a custom connector with the address https://hourbun.com/api/v1/mcp, and sign in to Hourbun. The connector then works in the Claude apps on your phone too. Claude Desktop can also reach Hourbun from its configuration file, with a token and the mcp-remote bridge.

## Where in the app

- API & MCP → New token
- API & MCP → Connect an AI assistant

## What you need

- A Hourbun account in an active workspace
- Claude on claude.ai, in the desktop app or on a phone; on a Team or Enterprise plan, an Owner who adds the connector
- For Claude Desktop with a token: Node.js, which runs the mcp-remote bridge

## Set it up

The setup that the page API & MCP of Hourbun gives, with the address of the server. In a setup with a token, put the text of your token in the place of `YOUR_TOKEN`.

### Claude (Sign-in)

On claude.ai or in the Claude desktop app, open Customize, Connectors, choose Add, then Add custom connector. Paste this URL and sign in to Hourbun when Claude asks: the connector then works in the Claude apps on your phone too. On a Team or Enterprise plan, an owner adds it in Organization settings, Connectors.

[Docs of Claude](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp)

```
https://hourbun.com/api/v1/mcp
```

### Claude Desktop (Token)

With a token: put it in claude_desktop_config.json (Settings, Developer, Edit Config), then restart Claude. It runs the mcp-remote bridge with Node.js. To sign in to Hourbun instead, add the connector of Claude.

[Docs of Claude Desktop](https://modelcontextprotocol.io/docs/develop/connect-local-servers)

```
{
  "mcpServers": {
    "hourbun": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://hourbun.com/api/v1/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer YOUR_TOKEN"
      }
    }
  }
}
```

## What to ask

Ask in your own words: the assistant chooses the tools of Hourbun. Under each question, the tools that it calls. The tools of invoices and uninvoiced time answer for the owner and the admins.

- “Start my timer on Website.” Calls `list_projects`, then `start_timer`.
- “Stop my timer.” Calls `stop_timer`.
- “What did I work on yesterday?” Calls `whoami`, then `list_time_entries`.
- “Which expenses did I record this month?” Calls `whoami`, then `list_expenses`.

## The connector, or a token

The connector is the setup for most people. Add it once on claude.ai or in the Claude desktop app, sign in to Hourbun, and it works in the Claude apps on your phone too: no token, and nothing to install. On a Team or Enterprise plan, an owner adds it in Organization settings, Connectors, and each member then connects it and signs in to their own Hourbun account, with their own role.

Claude Desktop also runs MCP servers from its own file, `claude_desktop_config.json` (Settings, Developer, Edit Config). That file runs local servers only, so the setup with a token starts the bridge `mcp-remote` with Node.js, and the bridge reaches Hourbun over HTTP. The header of the token is in `env`, as `AUTH_HEADER`: an argument with a space breaks on some systems. Save the file, then restart Claude.

## Allow the connection

When Claude opens Hourbun, sign in, and Hourbun asks you to allow it. The page names Claude and where Hourbun sends your answer. Choose the **Workspace** and the **Access**: **Read**, or **Read and write** to also track time and use your timer. Then press **Allow**, or **Deny**.

The connection works in that one workspace, with your role there. Hourbun keeps it as a token of yours, with an access token that lives 1 hour and a refresh token that ends after 90 days without use, both only as secure hashes. The access of a connection never changes: for other access, connect Claude again.

## Make a token

On the page **API & MCP** of Hourbun, **New token** opens a form with the **Name**, the **Access** and **Expires after**. Name the token after Claude Desktop, so that the list says where it is used. **Read** lets Claude Desktop read your projects, clients, time and expenses; **Read and write** also lets it track time and use your timer. A token can end after 7, 30, 90 or 365 days, or never.

**Create token** shows the text of the token once, with **Copy token**. Under **Use it with an AI assistant**, choose Claude Desktop: its setup has the token in it, and **Copy setup** copies it whole. After **Done**, no page shows the token again: Hourbun keeps only a secure hash of it. The token acts as you, in this workspace and with your role, until it expires or you revoke it.

## What Claude can do

Hourbun has one MCP tool for each operation of its API, and Claude gets only the tools that your role and the access allow. With **Read**, it reads your projects, clients, tasks, time entries, timer and expenses. With **Read and write**, it also tracks time, changes and deletes your time entries, and starts, pauses, resumes, stops and discards your timer. Invoices and uninvoiced time are for the owner and the admins of the workspace: a member or a manager gets no tool for them.

Each tool calls what the REST API calls, so Claude gets the same answers, amounts and refusals as a script. An entry on an issued invoice, or an approved or submitted one, is locked, and a money field that your role does not see is left out. Hourbun keeps no prompt and no chat: a tool receives only its arguments.

## Stop the connection

Each token and each connection is in the list of the page **API & MCP**, with its access, its status and the day of its last use. **Revoke** ends it at once, and Hourbun refuses the next request of Claude. The owner and the admins of the workspace can revoke it too, and it stops when you leave the workspace.

## Questions and answers

### Does Hourbun work with Claude?

Yes. Claude connects to Hourbun's MCP server as a custom connector, with the address of the server and one sign-in to Hourbun, on claude.ai, in the desktop app and in the apps on a phone.

### Should I use the connector or Claude Desktop with a token?

The connector, in most cases: it needs no token and works in every Claude app. The setup of Claude Desktop with a token is for a desktop app that reads its MCP servers from its configuration file, with Node.js for the mcp-remote bridge.

### Can a member of a Claude Team plan connect Hourbun?

Yes, once an Owner of the Claude organisation adds the connector in Organization settings, Connectors. Each member then connects it and signs in to their own Hourbun account.

## Sources

The setup of Claude follows its own documents, read on 13 November 2026:

- [Claude documentation](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp)
- [Claude Desktop documentation](https://modelcontextprotocol.io/docs/develop/connect-local-servers)

## Related

- [Track time from ChatGPT, Claude and other AI assistants](https://hourbun.com/guides/track-time-with-chatgpt-and-claude)
- [The MCP server in the API reference](https://hourbun.com/developers#mcp)
- [Time tracking apps with an MCP server](https://hourbun.com/best/time-tracking-apps-with-an-mcp-server)
- [ChatGPT](https://hourbun.com/integrations/chatgpt)
- [Claude Code](https://hourbun.com/integrations/claude-code)
- [Codex](https://hourbun.com/integrations/codex)
- [Cursor](https://hourbun.com/integrations/cursor)
- [VS Code](https://hourbun.com/integrations/vscode)
- [Gemini CLI](https://hourbun.com/integrations/gemini-cli)
- [All integrations](https://hourbun.com/integrations)
