Hubstaff API and MCP server

Hubstaff's API cannot add time that needs approval, and an API token is yours to create and renew. Sign in to Hubstaff once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Not affiliated with Hubstaff.

Hubstaff has no API for this. So we run one for you.

Hubstaff's own API, a GitHub MCP server and Cotlet compared
What you need Hubstaff's APIGitHub MCP serverCotlet
Manual time that needs approval No Partly Yes, 15 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when Hubstaff changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 17, 2026. Sources: Hubstaff Support: Hubstaff MCP Server · Hubstaff developers: Authentication · Hubstaff developers: Manual time requests · Hubstaff developers: Timesheets

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to Hubstaff in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect Hubstaff to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 15 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. Hubstaff and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
      https://cotlet.dev/mcp/v1 \
      --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
      "mcpServers": {
        "cotlet": {
          "url": "https://cotlet.dev/mcp/v1",
          "headers": {
            "Authorization": "Bearer ${COTLET_API_KEY}"
          }
        }
      }
    }
    Codex
    # ~/.codex/config.toml
    [mcp_servers.cotlet]
    url = "https://cotlet.dev/mcp/v1"
    bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/hubstaff with its own method and path, such as POST /api/v1/hubstaff/requests/{request_id}/manual-time-request/review, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the Hubstaff API and MCP server do?

15 tools on your own Hubstaff account. Agents call them as operations of the MCP tools hubstaff_read and hubstaff_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

Hubstaff tools in Cotlet's MCP server and REST API
Tool What it does Access
list_organizations Organizations you belong to, with ID, name and your role in each. read
list_members Members of an organization with user ID, name, email and role. read
list_projects Projects in an organization with status, billable default and client. read
list_tasks Tasks in a project with status, assignees and due date. read
list_timesheets Timesheets for a pay period with member, status, tracked time and activity levels. read
list_manual_time_requests Manual time requests with member, project, times, reason and status. read
list_time_off_requests Time off requests with member, policy, dates and status. read
get_daily_activity Tracked time and activity levels per day, member, project and task. read
approve_timesheet Approve a submitted timesheet so its hours count for payroll. writeasks first
deny_timesheet Deny a timesheet with a reason so the member can fix it. writeasks first
review_manual_time_request Approve or deny one manual time request that is waiting for review. writeasks first
add_time_entry Add manual time to a member on a project. writeasks first
create_project Create a project with a billable default and its members. write
create_task Add a task to a project and assign it to members. writeasks first
assign_project_member Add a member to a project or change their role on it. writeasks first

Scroll the table for all 15 tools.

Ask in plain words. Your agent does the rest.

Is it safe to connect Hubstaff?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

How much do the Hubstaff API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while Hubstaff is enabled for agents, so 20 calls a day come to 550 credits.

Cotlet credit packs: price, credits and calls at 25 credits each
Credits Price, one time Calls at 25 credits Per 1,000 credits
5,000 $29 200 $5.80
15,000 $79 600 $5.27
32,000 $149 1,280 $4.66
60,000 $249 2,400 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Questions

Does Hubstaff have an API?

Hubstaff has a full REST API, API v2, with read and write scopes, and an official MCP server that is read-only (checked 17 Oct 2026). The MCP server reads organizations, members, projects, tasks and time and activity data for owners and managers, cannot create or change anything, and is switched on per organization after an email to Hubstaff support. The API covers approvals, time entries, projects and tasks, but you create and renew the token or OAuth app yourself.

How do I get access?

Sign up free, open Hubstaff under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 15 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Hubstaff yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Hubstaff sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: approve_timesheet, deny_timesheet, review_manual_time_request, add_time_entry, create_task, assign_project_member wait for your OK by default. You can switch that off per tool for scheduled runs.

Which Hubstaff role does my agent need?

The role you sign in with. Approving timesheets and manual time needs an owner or manager, and manual time can also be reviewed by a project manager or a team lead with manual time approval for that member. Creating projects needs an owner, an organization manager or a team lead with the permission.

Should I use a Hubstaff MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Hubstaff changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

Who runs Cotlet?

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

Is Cotlet affiliated with Hubstaff?

No. Cotlet is independent and not affiliated with Hubstaff.

Give your agent access to Hubstaff.

Free 7-day trial with 2,000 credits, no card needed.