Homebase MCP by usefulapi is answering right now. Last checked 9 min ago. It exposes 16 tools. Last commit 10 Oct 2026.
Read Homebase locations, employees, shifts, timecards, labor costs and time clock status.
Uptime history
28 hours of history
28 hours agonow
100.0%
Uptime 24h
92 of 92 checks
16
Tools
read from the server
135 ms
Response time
average over 24h
0
Stars
last commit 10 Oct 2026
Nothing serious here today
Today is the operative word: we check Homebase MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.
run in your terminal
claude mcp add homebase --transport http https://homebase.usefulapi.io/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"homebase": {
"url": "https://homebase.usefulapi.io/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.homebase]
url = "https://homebase.usefulapi.io/mcp".cursor/mcp.json
{
"mcpServers": {
"homebase": {
"url": "https://homebase.usefulapi.io/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"homebase": {
"url": "https://homebase.usefulapi.io/mcp"
}
}
}Available tools 16
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
homebase
homebase_get_company
The Homebase company this API key belongs to: name, owner (id, name, email, phone) and created/updated times. GET /company.
homebase_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_get_labor
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_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_labor_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_location
One location by uuid: name, address, phone, website, time zone and POS merchant id. GET /locations/{location_uuid}.
homebase_get_location_plan
The Homebase subscription plan of a location: plan number, price, last update and trial state. GET /locations/{location_uuid}/plan.
homebase_get_shift
One shift of a location by id, with its labor data and optional note. GET /locations/{location_uuid}/shifts/{id}.
homebase_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_get_timeclock_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_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_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_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_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_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_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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://homebase.usefulapi.io/mcp | streamable-http | answering | 70 ms | 9 min ago |
Alternatives to Homebase MCP by usefulapi
same job, measured the same wayCin7 Core MCP by usefulapi
by usefulapi
Read Cin7 Core products, stock by location, sales, purchases, customers, suppliers and transfers.
Nookal MCP by usefulapi
by usefulapi
Read Nookal locations, practitioners, availability, appointments, clients, cases and invoices.
NexHealth MCP by usefulapi
by usefulapi
Read and write NexHealth appointments, patients, providers and locations.
H
Holydb MCP
by holydb
Read-only MCP server for HolyDB: find Catholic parish Mass times by location and time.
YouCanBook.me MCP by usefulapi
by usefulapi
Manage YouCanBook.me bookings, booking pages, appointment types, team members and locations.
Water Conditions
by aybeeare
Real-time water temperature and tides for 8,000+ locations, by name or lat/long coordinates.
DunkAPI
by noahowsh
NBA, WNBA and college basketball data: play-by-play, shot locations, box scores, odds. REST and MCP.
MapTiler MCP by usefulapi
by usefulapi
Geocoding, elevation, IP geolocation and coordinate transforms from the MapTiler Cloud API.
Homebase MCP by usefulapi — questions
Answers built from our own checks of this server.
What can Homebase MCP by usefulapi do?
It exposes 16 tools, read directly from the server on our last check. Among them: homebase_get_company, homebase_get_employee, homebase_get_labor, homebase_get_labor_by_employee, homebase_get_labor_by_role, homebase_get_location and 10 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Homebase MCP by usefulapi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 135 ms. The bar chart above shows every period we have measured.
How do I connect Homebase MCP by usefulapi?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Homebase MCP by usefulapi need an API key?
No. Homebase MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 16 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Homebase MCP by usefulapi?
It answers our handshake in 135 ms on average, which is faster than 75% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Homebase MCP by usefulapi open source?
Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.