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.
- Connects with an API key
- Free 14-day trial
- No credit card
Who is clocked in right now at the Downtown location?
Working in Homebase with Elaichi
-
List all Homebase company
-
List all Homebase deleted shifts
-
List all Homebase deleted timecards
How to connect Homebase to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Homebase MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Homebase MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
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
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Homebase through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Homebase is logged.
-
Scheduling
See who is on shift this week
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.
-
Store managers
Check who is clocked in right now
Pull the current timeclock statuses for a location to see who has started, who is on break and who has not shown up yet.
-
Payroll
Review timecards before the pay run
List the timecards for the period, spot missing clock-outs or odd hours, and ask which timecards were deleted so nothing slips through.
-
Finance
Compare labor hours by role and location
Ask for labor by role or by employee across locations to see where hours are running ahead of the plan.
-
HR
Look up an employee's details quickly
Get a single employee's record, their role and their location without searching through the Homebase team page.
-
Operations
Check location plans against real shifts
Pull the location plans and the shifts actually scheduled, then ask where coverage is thinner than planned.
Try asking
- “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”
What connecting Homebase gets you
6 screens from Elaichi, each doing one job for your Homebase account.
Ask Elaichi to work across your apps.
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
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about shifts and timecards in plain words.
The Elaichi Agent answers from live Homebase employees, shifts, timecards and locations.
Copy the endpoint
AI apps
One endpoint for every client, no shared key.
Claude, ChatGPT and Cursor reach Homebase through one governed endpoint, each person signed in.
Tool catalog
16 Homebase tools, ready with no code.
Employees, shifts, timecards, locations, labor and timeclock statuses, covered without writing a line.
Toolboxes
Every team gets its own Homebase toolbox.
Scheduling sees shifts, payroll sees timecards, each toolbox scoped to the team that needs it.
Shared connections
Share the connection, never the API key.
One manager connects Homebase, teammates work through it without ever seeing the credential.
Audit log
Know who looked at which timecard.
Every Homebase request lands in an append-only log with who, what, when and which resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Homebase digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch employees
Homebase
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Homebase
Queued
Workflows
A schedule starts the weekly labor digest.
Timecards are fetched and grouped, an agent drafts the digest, a manager approves before it posts.
Homebase health
Refreshed 4 minutes ago · every 15 minutes · from the employees collection
Employees
1,284 ↓ 12%
Shifts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Employees created
Last 14 days
By team
Share of activity
Downtown 34%
Westside stores 27%
Payroll 21%
Operations 18%
Collections and dashboards
Homebase health, computed without asking a model.
Four metrics, 14 days of shifts created and a breakdown by team, refreshed on schedule.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Homebase tools for your AI agents
16 tools are ready to call through Elaichi's MCP endpoint the moment you connect Homebase, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
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 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.
Put Homebase in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot