Model Context Protocol · Hubstaff v2 API

Team data.
One sentence.
Zero clicks.

Stop digging through the Hubstaff dashboard. A Model Context Protocol server plugs twelve tools directly into Claude — ask in English, get the answer in seconds. No exports. No filters. No wasted minutes.

claude · hubstaff-mcp
LIVE
$you
Who logged the most hours this week and what were they working on?
→ calling get_weekly_report · list_projects
Top performer logged 34.2h across two active projects. Second place was 28.7h. One team member is below threshold at 11.4h with a 34% activity average — worth reviewing.
Tools Available
12
Full API coverage
Rate Limit
1k/hr
Per application quota
Token TTL
24hr
Auto-refresh on 401
Setup Time
<3min
Clone, PAT, go
01 / How it runs

Five steps. Every time you ask.

01
You speak
Plain English in Claude
02
Claude picks
The right tool for the job
03
MCP auths
Cached token, auto-refresh
04
API answers
Hubstaff v2 responds
05
You read
Answer in the thread
02 / The toolkit

Twelve tools. Every corner of Hubstaff.

Each tool maps to a Hubstaff v2 endpoint. Claude chooses which ones to call based on what you ask — you never call them directly.

T_01
get_me
Confirm auth. Identify the current Hubstaff user and their timezone.
T_02
list_organizations
Every organization the authenticated user belongs to.
T_03
list_members
Full team roster for any organization.
T_04
list_projects
Active and archived projects with optional status filter.
T_05
list_time_entries
Granular time logs. Filter by user, project, or date range.
T_06
get_daily_activities
Pre-aggregated daily keyboard and mouse activity percentages.
T_07
list_screenshots
Screenshot metadata with image URLs for visual proof of work.
T_08
get_weekly_report
Weekly team summary. Who worked, how long, on what.
T_09
get_report_by_member
Custom date-range report grouped by team member.
T_10
get_report_by_project
Custom date-range report grouped by project.
T_11
list_tasks
Active and completed tasks across all projects.
T_12
list_payments
Payment records. Who was paid, when, and how much.
03 / Sample requests

The questions you can finally stop clicking for.

Who logged the most hours this week?
→get_weekly_report
Pull activity percentages for the whole team in March.
→get_daily_activities
Break down last 30 days of hours by project.
→get_report_by_project
Grab yesterday's screenshots for a specific team member.
→list_screenshots
Who got paid last month and how much?
→list_payments
Who's on my team and what's each person working on?
→list_members · list_projects
04 / Install

Four steps. Under three minutes.

STEP 01

Generate a PAT

Head to developer.hubstaff.com and create a Personal Access Token. The PAT is actually a refresh token — the MCP handles the exchange.

# Token page developer.hubstaff.com/personal_access_tokens
STEP 02

Clone the server

Pull the repo from private GitHub and install dependencies. Ninety-two packages, zero config.

git clone git@github.com:your-org/hubstaff-mcp.git cd hubstaff-mcp npm install
STEP 03

Drop in your token

One environment variable. Nothing else to configure. The server handles token exchange, caching, and refresh automatically.

cp .env.example .env # paste your PAT: HUBSTAFF_PAT=eyJ0eXAi...
STEP 04

Register with Claude

Add the MCP entry to your Claude Code settings. Restart the session. Start asking questions.

"hubstaff": { "command": "node", "args": ["/path/to/index.js"] }

Stop clicking.
Start asking.

The Hubstaff dashboard isn't going anywhere. But from now on, you shouldn't have to open it.

View install guide → See all 12 tools