# Homebase MCP connector

Connecting Homebase to Elaichi lets Claude, ChatGPT, Cursor and Microsoft Copilot read your employees, shifts, timecards, locations and labor hours, with every request running as the person who asked and recorded in an audit log.

Source: https://elaichi.ai/connectors/homebase/

## Facts

| | |
| --- | --- |
| Application | Homebase |
| Category | HRIS |
| AI tools | 16 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Homebase is connected

- Who is clocked in right now at the Downtown location?
- Total labor hours by role for last week
- List timecards deleted this month across all locations

## Connect Homebase in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Homebase.
2. Optionally set Share with, then press Connect.
3. Paste a Homebase API key. One person generates a token in Homebase and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Homebase tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Homebase MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Homebase MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Homebase MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Homebase MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Homebase MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Homebase to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Homebase tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Homebase through Elaichi

### See who is on shift this week

Scheduling. Ask for the shifts at one location or across all of them and get the roster back in plain language, without opening the Homebase calendar.

### Check who is clocked in right now

Store managers. Pull the current timeclock statuses for a location to see who has started, who is on break and who has not shown up yet.

### Review timecards before the pay run

Payroll. List the timecards for the period, spot missing clock-outs or odd hours, and ask which timecards were deleted so nothing slips through.

### Compare labor hours by role and location

Finance. Ask for labor by role or by employee across locations to see where hours are running ahead of the plan.

### Look up an employee's details quickly

HR. Get a single employee's record, their role and their location without searching through the Homebase team page.

### Check location plans against real shifts

Operations. Pull the location plans and the shifts actually scheduled, then ask where coverage is thinner than planned.

## Elaichi vs Zapier MCP vs Composio for Homebase

All three can connect Homebase to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Homebase tools | Allow or restrict single Homebase tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Homebase call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Homebase to Claude?

Two steps. In Elaichi, pick Homebase and paste the API key from your Homebase settings; there is no OAuth application to register and no client ID or secret to generate. Then in Claude, open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude can now read your Homebase employees, shifts and timecards as you.

### Does Homebase work with ChatGPT and Cursor as well as Claude?

Yes. Once Homebase is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Homebase once and every client uses it.

### What can an AI agent actually do with my Homebase data?

It can read what is in Homebase: your company, locations, employees, shifts, timecards, location plans, labor hours by role or by employee, timeclock statuses, and which shifts or timecards were deleted. So you can ask who is clocked in at a location, how many labor hours a role used last week, or which timecards are missing a clock-out. Short, concrete asks work better than long sentences.

### Does connecting Homebase give the AI access to every location and every employee?

No. Access follows the person who signed in, so the AI sees the Homebase locations, shifts and timecards that person can already see, and nothing more. Elaichi can narrow that further with roles and restrictions, but it can never widen what Homebase itself allows.

### Can my team share one Homebase connection?

Yes. One person connects Homebase with the API key and shares the connection with a team, so nobody else ever handles the credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who asked for a timecard or a shift.

### Can I stop an agent from deleting or changing things in Homebase?

This Homebase connector only reads: it lists and looks up employees, shifts, timecards, locations and labor, and cannot create, change or delete any of them. You can still restrict any individual action, such as reading timecards, for a role or for one person. A restricted action still appears in Elaichi's tool search flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Homebase connection when someone leaves?

Offboarding that person in Elaichi ends their access to Homebase through every client at once. A shared Homebase connection keeps working for everyone else on the team. If you want to remove Homebase entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

### Does the Homebase MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Homebase is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Homebase?

Yes. Both let Claude, ChatGPT or Cursor use Homebase. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Homebase call.

### How is Elaichi different from Composio for Homebase?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Homebase: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 16 Homebase tools

Every tool below is callable through https://api.elaichi.ai/mcp once Homebase is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Homebase company** (List). Retrieve the company for the current account. Returns one record (the company and its owner); the connector uses it to check the key on connect.
- **List all Homebase deleted shifts** (List). Retrieve the IDs of deleted shifts for a given location. Use it to remove shifts deleted since the last sync. Required: location_uuid, start_date, end_date. The connector pages through all results (Homebase's Link header; limit sets the page size, sent as per_page).
- **List all Homebase deleted timecards** (List). Retrieve the IDs of deleted timecards for a given location. Use it to remove timecards deleted since the last sync. Required: location_uuid, start_date, end_date. The connector pages through all results (Homebase's Link header; limit sets the page size, sent as per_page).
- **Get single Homebase employee by ID** (Get). Retrieve a single employee for a given location. Required: id, location_uuid.
- **List all Homebase employees** (List). Retrieve employees for a given location. Required: location_uuid. The connector pages through all results (Homebase's Link header; limit sets the page size, sent as per_page).
- **List all Homebase labor** (List). Retrieve aggregate labor for a given location, grouped by hour or by day. Returns one record: the location's labor totals for the date range. Required: location_uuid, start_date, end_date.
- **List all Homebase labor by employee** (List). Retrieve aggregate labor for a given location, grouped by employee. Required: location_uuid, start_date, end_date.
- **List all Homebase labor by role** (List). Retrieve aggregate labor for a given location, grouped by role. Required: location_uuid, start_date, end_date.
- **List all Homebase location plans** (List). Retrieve plan for location. Returns one record: the location's Homebase plan. Required: location_uuid.
- **Get single Homebase location by ID** (Get). Retrieve a given location for the current account. Required: id.
- **List all Homebase locations** (List). Retrieve locations for the current account.
- **Get single Homebase shift by ID** (Get). Retrieve a single shift for a given location. Required: id, location_uuid.
- **List all Homebase shifts** (List). Retrieve shifts for a given location. Required: location_uuid, start_date, end_date. The connector pages through all results (Homebase's Link header; limit sets the page size, sent as per_page).
- **Get single Homebase timecard by ID** (Get). Retrieve a single timecard for a given location. Required: id, location_uuid.
- **List all Homebase timecards** (List). Retrieve timecards for a given location. Known limitation: time off labor totals (paid time off, time off, sick time, unpaid time off and the FFCRA fields) are always zero on individual timecards; use labor_by_employee.list for employees' totals including time off. Required: location_uuid, start_date, end_date. The connector pages through all results (Homebase's Link header; limit sets the page size, sent as per_page).
- **List all Homebase timeclock statuses** (List). Retrieve the current timeclock status for a given job. Returns one record for the job (an employee at a location; job ids come from employees.list, job.id). Required: job_id.
