Kickserv MCP connector
The Kickserv connector brings customers, jobs, job charges, employees and notes into Claude, ChatGPT, Cursor and Microsoft Copilot, so every person on your team works inside their own Kickserv access with each action logged.
- Connects with an API key
- Free 14-day trial
- No credit card
List today's jobs and the notes left on each one
Working in Kickserv with Elaichi
-
List all Kickserv customer jobs
-
List all Kickserv customer notes
-
Get single Kickserv customer note by ID
How to connect Kickserv to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Kickserv 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.
Kickserv 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.
Kickserv 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.
Kickserv 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.
Kickserv 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 Kickserv 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 Kickserv through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Kickserv is logged.
-
Dispatch
Book a new job from one message
Give the customer, the address and the problem, and a Kickserv job is created on that customer's record, ready to schedule. No switching tabs between the phone call and the calendar.
-
Office
Catch the customer record up after a call
Update the phone number, fix the billing address and add a note about the gate code, all from one ask. The Kickserv customer record is current before the next call comes in.
-
Field crew
Check today's jobs before heading out
Ask which Kickserv jobs are on the list and read the notes left on each one. Technicians arrive knowing what was promised and what to bring.
-
Billing
Add charges to a job as work finishes
Pick the right item from the Kickserv price list and add it as a charge on the job. Nothing waits until the end of the week to be remembered.
-
Management
See who is carrying the most jobs
List jobs across the team and ask which employees are stretched this week. Rebalance the schedule with the real Kickserv numbers in front of you.
-
Operations
Set up a new technician in minutes
Create the Kickserv employee record with the name, role and contact details, then keep it updated as the person moves between crews.
Try asking
- “List today's jobs and the notes left on each one”
- “Create a job for Maria Lopez, water heater replacement, Thursday morning”
- “Add a note to the Henderson job: gate code is 4471”
What connecting Kickserv gets you
6 screens from Elaichi, each doing one job for your Kickserv account.
Ask Elaichi to work across your apps.
List today's jobs and the notes left on each one
Create a job for Maria Lopez, water heater replacement, Thursday morning
Add a note to the Henderson job: gate code is 4471
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Kickserv about today's jobs in plain language.
Answers come from live Kickserv jobs, customers and notes, not a stale export.
Copy the endpoint
AI apps
One endpoint puts Kickserv in every client.
Claude, ChatGPT and Cursor reach Kickserv jobs through one org endpoint, no SDK, no shared key.
Tool catalog
36 Kickserv tools, ready without writing code.
Customers, jobs, charges, employees, items and notes are covered from the first connection.
Toolboxes
Every team gets its own Kickserv toolbox.
Dispatch books jobs, billing adds charges, and the office keeps customer records current.
Shared connections
Share a Kickserv connection, not an API key.
Teammates work through the connection while the Kickserv API key stays out of sight.
Audit log
Every Kickserv change names the person behind it.
When, who, what happened and which job or customer, kept in one append-only log.
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.
Kickserv digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch jobs
Kickserv
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
Kickserv
Queued
Workflows
A schedule starts the Kickserv job digest itself.
New Kickserv jobs are fetched, grouped, drafted into a digest, approved, then posted back.
Kickserv health
Refreshed 4 minutes ago · every 15 minutes · from the jobs collection
Jobs
1,284 ↓ 12%
Customers
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Jobs created
Last 14 days
By team
Share of activity
Dispatch 34%
Office 27%
Field crew 21%
Billing 18%
Collections and dashboards
Kickserv health numbers arrive without anyone asking.
Jobs created over 14 days, split by team, refreshed on a schedule with no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Kickserv
All three can connect Kickserv 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 Kickserv tools | Allow or restrict single Kickserv 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 Kickserv 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.
Kickserv tools for your AI agents
36 tools are ready to call through Elaichi's MCP endpoint the moment you connect Kickserv, 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 Kickserv to Claude?
Connect Kickserv in Elaichi by pasting your Kickserv API key, then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate. The whole Kickserv setup takes a few minutes.
Does Kickserv work with ChatGPT and Cursor as well as Claude?
Yes. Once Kickserv is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Kickserv once and every client picks it up.
What can an AI agent actually do with my Kickserv data?
It can list and look up Kickserv customers, jobs, employees and price list items, create new customers and jobs, add charges to a job, and write, read, update or delete notes on customers and jobs. Short concrete asks work best, such as adding a note to a named job or listing today's jobs. It cannot do anything in Kickserv that the connected tools do not cover.
Does connecting Kickserv give the AI access to everything in my account?
No. Every call to Kickserv runs inside the access of the person whose connection is in use, so the agent sees and changes only what that person could see and change in Kickserv. Elaichi can narrow that access further with roles and restrictions, and it never widens it.
Can I stop an agent from deleting or changing things in Kickserv?
Yes. Restrictions in Elaichi work per action, so you can restrict deleting Kickserv customers or notes, or creating jobs, 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 against Kickserv, whatever the prompt says.
What happens to a Kickserv connection when someone leaves?
Offboarding a person in Elaichi ends their access to Kickserv through every client at once. A Kickserv connection shared with a team keeps working for everyone else. If you want it gone entirely, disconnecting Kickserv once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the Kickserv MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Kickserv 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 Kickserv?
Yes. Both let Claude, ChatGPT or Cursor use Kickserv. 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 Kickserv call.
How is Elaichi different from Composio for Kickserv?
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 Kickserv: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Kickserv 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