Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Read Homebase locations, employees, shifts, timecards, labor costs and time clock status.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://homebase.usefulapi.io/mcpRun this in your terminal
claude mcp add --transport http homebase https://homebase.usefulapi.io/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"homebase": {
"url": "https://homebase.usefulapi.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"homebase": {
"type": "http",
"url": "https://homebase.usefulapi.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://homebase.usefulapi.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.
homebase_get_companyThe Homebase company this API key belongs to: name, owner (id, name, email, phone) and created/updated times. GET /company.
homebase_list_locationsList 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_locationOne location by uuid: name, address, phone, website, time zone and POS merchant id. GET /locations/{location_uuid}.
homebase_get_location_planThe Homebase subscription plan of a location: plan number, price, last update and trial state. GET /locations/{location_uuid}/plan.
homebase_list_employeesList 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_employeeOne 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_shiftsList 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_shiftOne shift of a location by id, with its labor data and optional note. GET /locations/{location_uuid}/shifts/{id}.
homebase_list_deleted_shiftsThe 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_timecardsList 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_uu
homebase_get_timecardOne 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_timecardsThe 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_laborAggregate 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_roleAggregate 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_employeeAggregate 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_statusThe 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
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 6 ms (HTTP 200)
No sign-in needed
Read 16 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.22.3) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, dotnet-mcp
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP server for .NET symbols, XAML, source generators, and restricted workspace edit
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Use Homebase from Claude, Cursor, or any MCP client — locations, employees, shifts, timecards, labor reports and time clock status. Hosted, no local install: connect with your own Homebase credentials.
Live endpoint: https://homebase.usefulapi.io/mcp · Homepage: https://usefulapi.io/homebase
https://homebase.usefulapi.io/mcp.claude mcp add --transport http homebase https://homebase.usefulapi.io/mcp, then run /mcp to log in.{
"mcpServers": { "homebase": { "url": "https://homebase.usefulapi.io/mcp" } } }
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, and the login page asks for your Homebase credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/homebase/
| Tool | Type | What it does |
|---|---|---|
homebase_get_company | read | Get company |
homebase_list_locations | read | List locations |
homebase_get_location | read | Get location |
homebase_get_location_plan | read | Get location plan |
homebase_list_employees | read | List employees |
homebase_get_employee | read | Get employee |
homebase_list_shifts | read | List shifts |
homebase_get_shift | read | Get shift |
homebase_list_deleted_shifts | read | List deleted shifts |
homebase_list_timecards | read | List timecards |
homebase_get_timecard | read | Get timecard |
homebase_list_deleted_timecards | read | List deleted timecards |
homebase_get_labor | read | Get labor report |
homebase_get_labor_by_role | read | Get labor report by role |
homebase_get_labor_by_employee | read | Get labor report by employee |
homebase_get_timeclock_status | read | Get time clock status |
homebase_usage_status | meta | Usage status (free-tier meter) |
homebase_request_feature | meta | Request a missing feature |
homebase_upgrade | meta | Upgrade to Pro or Pro+ |
homebase_cancel_subscription | meta | Cancel the Pro subscription |
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Pro (per user) | $9/mo or $90/yr (2 months free) | Unlimited* |
\*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to support@usefulapi.io.
Pro covers this 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 support@usefulapi.io.
MIT © usefulapi. Not affiliated with or endorsed by Homebase.