# 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.

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

## Facts

| | |
| --- | --- |
| Application | Kickserv |
| Category | CRM |
| AI tools | 36 |
| 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 Kickserv is connected

- 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

## Connect Kickserv in Elaichi

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

1. Open Connections, choose Add connection, and pick Kickserv.
2. Optionally set Share with, then press Connect.
3. Paste a Kickserv API key. One person generates a token in Kickserv 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 Kickserv tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Kickserv 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.

## Kickserv 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`.

## Kickserv 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.

## Kickserv 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.

## Kickserv 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 Kickserv 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 Kickserv 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 Kickserv through Elaichi

### Book a new job from one message

Dispatch. 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.

### Catch the customer record up after a call

Office. 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.

### Check today's jobs before heading out

Field crew. 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.

### Add charges to a job as work finishes

Billing. 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.

### See who is carrying the most jobs

Management. 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.

### Set up a new technician in minutes

Operations. Create the Kickserv employee record with the name, role and contact details, then keep it updated as the person moves between crews.

## 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. Endpoint: 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](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 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 my team share one Kickserv connection?

Yes. One person connects Kickserv in Elaichi and shares it with a team, and nobody else ever handles the Kickserv API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every job, note or charge.

### 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.

## All 36 Kickserv tools

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

- **List all Kickserv customer jobs** (List). List a customer's jobs (GET /{account_slug}/customers/{customer_number}/jobs, as XML). Records come back as the connector parses Kickserv's XML (each field {_text, _attributes}). Kickserv returns 30 records a page; the connector pages with page while a page is full. From the jobs list docs ("Scope by customer number"). Required: customer_number.
- **List all Kickserv customer notes** (List). List customer notes (GET /{account_slug}/customers/{customer_number}/notes, as XML). Records come back as the connector parses Kickserv's XML (each field {_text, _attributes}). Required: customer_number.
- **Create a Kickserv customer note** (Create). Create a customer note (POST /{account_slug}/customers/{customer_number}/notes, as XML). The connector sends the fields as Kickserv's XML body (&lt;note&gt;...&lt;/note&gt;). Required: customer_number.
- **Get single Kickserv customer note by ID** (Get). Get a customer note (GET /{account_slug}/customers/{customer_number}/notes/{note_id}, as XML). Required: id, customer_number.
- **Update a Kickserv customer note by ID** (Update). Update a customer note (PATCH /{account_slug}/customers/{customer_number}/notes/{note_id}, as XML). The connector sends the fields as Kickserv's XML body (&lt;note&gt;...&lt;/note&gt;). Required: id, customer_number.
- **Delete a Kickserv customer note by ID** (Delete). Delete a customer note (DELETE /{account_slug}/customers/{customer_number}/notes/{note_id}, as XML). Required: id, customer_number.
- **List all Kickserv customers** (List). List customers (GET /{account_slug}/customers, as XML). Records come back as the connector parses Kickserv's XML (each field {_text, _attributes}). Kickserv returns 30 records a page; the connector pages with page while a page is full.
- **Create a Kickserv customer** (Create). Create a customer (POST /{account_slug}/customers, as XML). The connector sends the fields as Kickserv's XML body (&lt;customer&gt;...&lt;/customer&gt;; lists as type="array"). Kickserv assigns the customer number (customer_number, id and account_id are ignored). Required: name.
- **Get single Kickserv customer by ID** (Get). Get a customer (GET /{account_slug}/customers/{customer_number}, as XML). Required: id.
- **Update a Kickserv customer by ID** (Update). Update a customer (PATCH /{account_slug}/customers/{customer_number}, as XML). The connector sends the fields as Kickserv's XML body (&lt;customer&gt;...&lt;/customer&gt;; lists as type="array"). customer_number, id and account_id can't be changed. Required: id.
- **Delete a Kickserv customer by ID** (Delete). Delete a customer (DELETE /{account_slug}/customers/{customer_number}, as XML). Required: id.
- **List all Kickserv employees** (List). List employees (GET /{account_slug}/employees, as XML). Records come back as the connector parses Kickserv's XML (each field {_text, _attributes}). Active and inactive employees, all in one reply.
- **Create a Kickserv employee** (Create). Create an employee (POST /{account_slug}/employees, as XML). The connector sends the fields as Kickserv's XML body (&lt;employee&gt;...&lt;/employee&gt;). Required: cell_phone, name.
- **Get single Kickserv employee by ID** (Get). Get an employee (GET /{account_slug}/employees/{employee_number}, as XML). Required: id.
- **Update a Kickserv employee by ID** (Update). Update an employee (PATCH /{account_slug}/employees/{employee_number}, as XML). The connector sends the fields as Kickserv's XML body (&lt;employee&gt;...&lt;/employee&gt;). Employees can't be deleted: set active false to deactivate one. Required: id.
- **List all Kickserv items** (List). List items (GET /{account_slug}/items, as XML). Records come back as the connector parses Kickserv's XML (each field {_text, _attributes}). Kickserv returns 30 records a page; the connector pages with page while a page is full. Only active items unless inactive (inactive only) or all (every item) is true; Kickserv takes them as bare flags (?inactive, ?all).
- **Create a Kickserv job charge** (Create). Create a job charge (POST /{account_slug}/jobs/{job_number}/job_charges, as XML). The connector sends the fields as Kickserv's XML body (&lt;job_charge&gt;...&lt;/job_charge&gt;). A line item (charge) on the job. Required: job_number, job_charge_type_id.
- **List all Kickserv job notes** (List). List job notes (GET /{account_slug}/jobs/{job_number}/notes, as XML). Records come back as the connector parses Kickserv's XML (each field {_text, _attributes}). Required: job_number.
- **Create a Kickserv job note** (Create). Create a job note (POST /{account_slug}/jobs/{job_number}/notes, as XML). The connector sends the fields as Kickserv's XML body (&lt;note&gt;...&lt;/note&gt;). Required: job_number.
- **Get single Kickserv job note by ID** (Get). Get a job note (GET /{account_slug}/jobs/{job_number}/notes/{note_id}, as XML). Required: id, job_number.
- **Update a Kickserv job note by ID** (Update). Update a job note (PATCH /{account_slug}/jobs/{job_number}/notes/{note_id}, as XML). The connector sends the fields as Kickserv's XML body (&lt;note&gt;...&lt;/note&gt;). Required: id, job_number.
- **Delete a Kickserv job note by ID** (Delete). Delete a job note (DELETE /{account_slug}/jobs/{job_number}/notes/{note_id}, as XML). Required: id, job_number.
- **List all Kickserv jobs** (List). List jobs (GET /{account_slug}/jobs, as XML). Records come back as the connector parses Kickserv's XML (each field {_text, _attributes}). Kickserv returns 30 records a page; the connector pages with page while a page is full.
- **Create a Kickserv job** (Create). Create a job (POST /{account_slug}/jobs, as XML). The connector sends the fields as Kickserv's XML body (&lt;job&gt;...&lt;/job&gt;; lists as type="array"). Required: customer_id, job_type_id.
- **Get single Kickserv job by ID** (Get). Get a job (GET /{account_slug}/jobs/{job_number}, as XML). Required: id.
- **Update a Kickserv job by ID** (Update). Update a job (PATCH /{account_slug}/jobs/{job_number}, as XML). The connector sends the fields as Kickserv's XML body (&lt;job&gt;...&lt;/job&gt;; lists as type="array"). employee_ids replaces the job's assigned employees. Required: id.
- **Delete a Kickserv job by ID** (Delete). Delete a job (DELETE /{account_slug}/jobs/{job_number}, as XML). Required: id.
- **Create a Kickserv task** (Create). Create a task (POST /{account_slug}/tasks, as XML). The connector sends the fields as Kickserv's XML body (&lt;task&gt;...&lt;/task&gt;; lists as type="array"). Required: job_id, name, task_type_id.
- **Get single Kickserv task by ID** (Get). Get a task (GET /{account_slug}/tasks/{task_id}, as XML). Required: id.
- **Update a Kickserv task by ID** (Update). Update a task (PATCH /{account_slug}/tasks/{task_id}, as XML). The connector sends the fields as Kickserv's XML body (&lt;task&gt;...&lt;/task&gt;; lists as type="array"). employee_ids replaces the task's assigned employees. Required: id.
- **Delete a Kickserv task by ID** (Delete). Delete a task (DELETE /{account_slug}/tasks/{task_id}, as XML). Required: id.
- **List all Kickserv time entries** (List). List time entries (GET /{account_slug}/jobs/{job_number}/time_entries, as XML). Records come back as the connector parses Kickserv's XML (each field {_text, _attributes}). Required: job_number.
- **Create a Kickserv time entry** (Create). Create a time entry (POST /{account_slug}/jobs/{job_number}/time_entries, as XML). The connector sends the fields as Kickserv's XML body (&lt;time_entry&gt;...&lt;/time_entry&gt;). Required: job_number, number_of_hours, started_on, employee_id.
- **Get single Kickserv time entry by ID** (Get). Get a time entry (GET /{account_slug}/jobs/{job_number}/time_entries/{time_entry_id}, as XML). Required: id, job_number.
- **Update a Kickserv time entry by ID** (Update). Update a time entry (PATCH /{account_slug}/jobs/{job_number}/time_entries/{time_entry_id}, as XML). The connector sends the fields as Kickserv's XML body (&lt;time_entry&gt;...&lt;/time_entry&gt;). Required: id, job_number.
- **Delete a Kickserv time entry by ID** (Delete). Delete a time entry (DELETE /{account_slug}/jobs/{job_number}/time_entries/{time_entry_id}, as XML). Required: id, job_number.
