Read Homebase locations, employees, shifts, timecards, labor costs and time clock status. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"homebase": {
"url": "https://homebase.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"homebase": {
"type": "http",
"url": "https://homebase.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Homebase API key.
Request a key in Homebase → Settings → API (app.joinhomebase.com/settings/api). Homebase must approve the request before the key shows on that page. The key is read only. Your key is used only to call the Homebase API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Homebase API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
homebase_get_company | read | Get company The Homebase company this API key belongs to: name, owner (id, name, email, phone) and created/updated times. GET /company. |
homebase_list_locations | read | List locations List the locations (stores or sites) of the account with uuid, name, address, phone, website and time zone. The uuid is the id every other Homebase tool needs. GET /locations. |
homebase_get_location | read | Get location One location by uuid: name, address, phone, website, time zone and POS merchant id. GET /locations/{location_uuid}. |
homebase_get_location_plan | read | Get location plan The Homebase subscription plan of a location: plan number, price, last update and trial state. GET /locations/{location_uuid}/plan. |
homebase_list_employees | read | List employees List the employees of a location with contact details and their job: level, default role, additional roles, wage type and rate, payroll id and archive date. The time-clock PIN is never returned. GET /locations/{location_uuid}/employees. |
homebase_get_employee | read | Get employee One employee of a location by user id, with contact details and job (role, wage type and rate, payroll id). The id is the job's user id from homebase_list_employees. GET /locations/{location_uuid}/employees/{id}. |
homebase_list_shifts | read | List shifts List the scheduled shifts of a location in a date range: employee, role, department, start and end, published/open state, wage rate and scheduled labor hours (regular, overtime). Filter open shifts only. GET /locations/{location_uuid}/shifts. |
homebase_get_shift | read | Get shift One shift of a location by id, with its labor data and optional note. GET /locations/{location_uuid}/shifts/{id}. |
homebase_list_deleted_shifts | read | List deleted shifts The ids of shifts deleted in a date range at a location, with their start, end and deletion time. Use it to keep a copy of the schedule in sync. GET /locations/{location_uuid}/shifts/deleted. |
homebase_list_timecards | read | List timecards List the timecards (worked time) of a location in a date range: employee, role, clock in and out, breaks, hours, labor cost, tips and approval state. Time-off hours are always 0 on timecards; use homebase_get_labor_by_employee for totals with time off. GET /locations/{location_uuid}/timecards. |
homebase_get_timecard | read | Get timecard One timecard of a location by id: clock in and out, breaks, labor hours and cost, tips, approval state. GET /locations/{location_uuid}/timecards/{id}. |
homebase_list_deleted_timecards | read | List deleted timecards The ids of timecards deleted in a date range at a location, with clock in, clock out and deletion time. Use it to keep a copy of the timecards in sync. GET /locations/{location_uuid}/timecards/deleted. |
homebase_get_labor | read | Get labor report Aggregate labor for a location in a date range, grouped by day or by hour: regular, overtime and paid hours, labor cost, tips, breaks and time off. GET /locations/{location_uuid}/labor. |
homebase_get_labor_by_role | read | Get labor report by role Aggregate labor (hours, cost, tips, overtime) for a location in a date range, grouped by role. GET /locations/{location_uuid}/labor/by_role. |
homebase_get_labor_by_employee | read | Get labor report by employee Aggregate labor (hours, cost, wage rate, tips, overtime, time off) for a location in a date range, grouped by employee. Use it for payroll totals. GET /locations/{location_uuid}/labor/by_employee. |
homebase_get_timeclock_status | read | Get time clock status The current time-clock state of one job (employee at a location): clocked_in, on_break or clocked_out, the current shift, the shifts that can be clocked into and the breaks that can be started. The job id is the `job.id` of an employee from homebase_list_employees. GET /timeclock/status. |
homebase_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
homebase_request_feature | Request a missing feature Tell usefulapi that the user needs something the Homebase tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
homebase_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Homebase tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
homebase_cancel_subscription | Cancel the Pro subscription Cancel the caller's Homebase Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run homebase_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited |
Pro covers this Homebase server only. Subscribe with homebase_upgrade (it returns a Stripe Checkout link). Cancel any time with homebase_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running homebase_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Homebase. The server calls the Homebase API with your own Homebase access, so it sees only the data that your account can see.
The login page asks for your Homebase API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Homebase API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Homebase API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Homebase.
All 16 Homebase tools are marked read-only.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Homebase server only. Run homebase_usage_status to see how many calls you used.
Ask the AI to run homebase_upgrade: it returns a Stripe Checkout link. To cancel, run homebase_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with homebase_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.