Connect-MCP

Kickserv MCP by usefulapi

io.usefulapi/kickserv · v1.11.1

Look up Kickserv customers, jobs, notes and time entries, and create jobs, tasks and charges.

MCPremoteno credentialsCRM & salesKnowledge & docsJobs & HR

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 20 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 88/100

What it does: 20 tools · 11 read, 9 write (incl. delete/pay) · CRM & sales, Knowledge & docs, Tasks & projects

Test call kickserv_list_customers: needs a key: HTTP 401 (920 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://kickserv.usefulapi.io/mcp

Tools

20 tools listed at last check
  • kickserv_list_customers List or search customers, 30 per page. Every filter is an exact match on that field. Use `only` to keep the response small. Kickserv: GET /{account}/customers.xml.
  • kickserv_get_customer Fetch one customer by customer number, optionally with related contacts, jobs, tasks and notes. The result's `id` is what job/task create calls need as `customer_id`. Kickserv: GET /{account}/customers/{customer_number}.xml.
  • kickserv_list_customer_jobs List the jobs for one customer, 30 per page. Kickserv: GET /{account}/customers/{customer_number}/jobs.xml.
  • kickserv_list_jobs List jobs (work orders, estimates, invoices), 30 per page, filterable by schedule window, status, assigned employee, category (job type) or job status. Kickserv: GET /{account}/jobs.xml.
  • kickserv_get_job Fetch one job by job number, optionally with its customer, assigned employees, job charges (line items), time entries and notes. Kickserv: GET /{account}/jobs/{job_number}.xml.
  • kickserv_list_customer_notes List the notes on one customer. Kickserv: GET /{account}/customers/{customer_number}/notes.xml.
  • kickserv_list_job_notes List the notes on one job. Kickserv: GET /{account}/jobs/{job_number}/notes.xml.
  • kickserv_list_job_time_entries List the time entries (hours logged by technicians) on one job. Kickserv: GET /{account}/jobs/{job_number}/time_entries.xml.
  • kickserv_get_task Fetch one task (appointment / to-do attached to a job) by id. Kickserv: GET /{account}/tasks/{task_id}.xml.
  • kickserv_list_employees List all employees (technicians and office staff), active and inactive. Use their `id` for job/task assignment and time entries, and `employee_number` to filter jobs. Kickserv: GET /{account}/employees.xml.
  • kickserv_list_items List products/services (the price list used for job charges), 30 per page. Active items only by default. Kickserv: GET /{account}/items.xml.
  • kickserv_create_customer WRITE: create a new customer. Kickserv assigns the customer number. Kickserv: POST /{account}/customers.xml.
  • kickserv_update_customer WRITE: update fields on an existing customer. Only the fields you pass change. Balances, credit limit and custom fields are not settable here. Kickserv: PATCH /{account}/customers/{customer_number}.xml.
  • kickserv_add_customer_note WRITE: add a note to a customer. Set `public` to true to make it visible to the customer. Kickserv: POST /{account}/customers/{customer_number}/notes.xml.
  • kickserv_create_job WRITE: create a job (work order) for a customer. `customer_id` is the customer's internal `id` (from kickserv_get_customer), not the customer number; `job_type_id` is the job category. Set `estimate` to create it as an estimate. Kickserv: POST /{account}/jobs.xml.
  • kickserv_update_job WRITE: update an existing job — reschedule it, rename it, change its description, category or custom job status, or reassign employees (employee_ids replaces the assignment). Totals, tax and payment fields are not settable here. Kickserv: PATCH /{account}/jobs/{job_number}.xml.
  • kickserv_add_job_note WRITE: add a note to a job. Set `public` to true to make it visible to the customer. Kickserv: POST /{account}/jobs/{job_number}/notes.xml.
  • kickserv_create_task WRITE: create a task (appointment / to-do) on a job and optionally assign employees. `job_id` is the job's internal `id` (from kickserv_get_job), not the job number. Kickserv: POST /{account}/tasks.xml.
  • kickserv_log_time_entry WRITE: log hours worked by an employee on a job. `employee_id` is the employee's `id` from kickserv_list_employees. Kickserv: POST /{account}/jobs/{job_number}/time_entries.xml.
  • kickserv_add_job_charge WRITE: add a charge (line item — a product, service or part) to a job. This changes the job's estimate/invoice total; it does NOT charge the customer's card. Pick `item_id` from kickserv_list_items. Kickserv: POST /{account}/jobs/{job_number}/job_charges.xml.

Badge

Connect-MCP badge for io.usefulapi/kickserv

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.usefulapi/kickserv.svg)](https://clawy.uk/mcp/s/io.usefulapi/kickserv)

Repository · Website