Workiz MCP connector
The Workiz connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent look up and update clients, calls, client notes, ad groups and availability in Workiz, with every action running as the signed-in person and recorded in an audit log.
- Connects with an API key
- Free 14-day trial
- No credit card
Which availability slots are open tomorrow afternoon?
Working in Workiz with Elaichi
-
Get single Workiz ad group by ID
-
List all Workiz ad groups
-
List all Workiz availability blocking entities
How to connect Workiz to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Workiz 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.
Workiz 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.
Workiz 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.
Workiz 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.
Workiz 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 Workiz 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 Workiz through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Workiz is logged.
-
Office
Catch a client up after a call
Pull up the call that just came in, find the Workiz client it belongs to, and add a note on what was agreed before the next line rings.
-
Dispatch
Check who is free before promising a time
Ask which availability slots are open this afternoon and what is already blocking the calendar, then commit to a window you can keep.
-
Sales
Add a new client while still on the phone
Create the client in Workiz from a few details and attach a note on what they need, so the lead never sits in a notepad.
-
Marketing
Keep ad groups tidy
List the ad groups Workiz is tracking, rename the ones that drifted, and remove the ones for campaigns that have ended.
-
Customer service
Read the history before you call back
Ask for every note on a client and the recent calls tied to them, and get the whole story in one place.
-
Operations
Shape the fields the office actually uses
Add a custom field or regroup the existing ones so technicians capture the gate code, the dog's name, or the best time to call.
Try asking
- “Which availability slots are open tomorrow afternoon?”
- “Add a note to the Johnson client about the gate code.”
- “List this morning's calls and which clients they belong to.”
What connecting Workiz gets you
6 screens from Elaichi, each doing one job for your Workiz account.
Ask Elaichi to work across your apps.
Which availability slots are open tomorrow afternoon?
Add a note to the Johnson client about the gate code.
List this morning's calls and which clients they belong to.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Workiz questions in plain words.
Get answers from live clients, calls and client notes without opening a single screen.
Copy the endpoint
AI apps
One endpoint brings Workiz to every client.
Claude, ChatGPT and Cursor reach Workiz through one org endpoint, no SDK, no shared API key.
Tool catalog
98 Workiz tools, no custom code needed.
Clients, calls, client notes, ad groups, availability and custom fields, all in one catalog.
Toolboxes
Every team gets its own Workiz toolbox.
Dispatch sees availability, the office sees clients and notes, marketing sees ad groups.
Shared connections
Share a Workiz connection, never the API key.
Teammates work through the account the owner connected and never see the credential.
Audit log
Every Workiz action names who did it.
When, who, what happened, type and resource, in a log nobody can edit.
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.
Workiz digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch clients
Workiz
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
Workiz
Queued
Workflows
A schedule starts real Workiz work.
New calls are fetched, grouped, drafted into a digest, approved by a person, then posted to Workiz.
Workiz health
Refreshed 4 minutes ago · every 15 minutes · from the clients collection
Clients
1,284 ↓ 12%
Calls
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Clients created
Last 14 days
By team
Share of activity
Dispatch 34%
Front office 27%
Sales 21%
Marketing 18%
Collections and dashboards
Workiz health, counted, not asked for.
Four metrics, fourteen days of clients created and a split by team, refreshed on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Workiz
All three can connect Workiz 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 Workiz tools | Allow or restrict single Workiz 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 Workiz 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.
Workiz tools for your AI agents
98 tools are ready to call through Elaichi's MCP endpoint the moment you connect Workiz, 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 Workiz to Claude?
Open Elaichi, choose Workiz, and paste the API key from your Workiz account. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Workiz is available in Claude.
Does Workiz work with ChatGPT and Cursor as well as Claude?
Yes. Once Workiz 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 Workiz once and every client picks it up.
What can an AI agent actually do with my Workiz data?
It can find a Workiz client, read and add client notes, list recent calls and open a specific one, check availability slots and what is blocking the calendar, and create or clean up ad groups and custom fields. You ask in plain language, such as which slots are open tomorrow or add a note to this client. Short, concrete asks work better than long paragraphs.
Does connecting Workiz give the AI everything in my account?
No. Every call into Workiz runs as the person who signed in to Elaichi, so the agent sees only what that person's Workiz access allows. Elaichi can narrow that further with roles and restrictions, and it never widens it beyond what the person already has.
Can I stop an agent from deleting or changing things in Workiz?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Workiz clients and notes while restricting deleting ad groups or custom fields, for a role or for one person. A restricted tool still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Workiz connection when someone leaves?
Offboarding that person in Elaichi ends their access to Workiz through every client at once. A shared Workiz connection keeps working for everyone else on the team. If you disconnect Workiz in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.
Does the Workiz MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Workiz 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 Workiz?
Yes. Both let Claude, ChatGPT or Cursor use Workiz. 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 Workiz call.
How is Elaichi different from Composio for Workiz?
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 Workiz: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Workiz 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