Endpoints: 28,729MCP servers: 18,413Payout addresses: 2,070Paid calls: 1,517Letters: 13Defects: 1,321counted just now
teppi

MCP serverio.usefulapi/kickserv

Look up Kickserv customers, jobs, notes and time entries, and create jobs, tasks and charges.
UNRATEDActivestreamable-httpkickserv.usefulapi.io

Overview

Score?
UNRATED 0.102
of what a free look can see, on 1 looks
Looks
6
last 3 hr ago
Tools
20

More info

URL
kickserv.usefulapi.io/mcp
streamable-http
Says it is
kickserv-mcp 1.0.0
protocol 2025-06-18
In the record since
4 days ago

Among servers18,413 with a card

0median 0.606 · this server 0.102 · highest on record 0.8561

Toolsfrom sha256:3e2d3dba58…cc6293

The tools this server lists, read out of the definition it returned
ToolSchema
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.
input · no output
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 ki
input · no output
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.
input · no output
kickserv_create_customer
WRITE: create a new customer. Kickserv assigns the customer number. Kickserv: POST /{account}/customers.xml.
input · no output
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 categ
input · no output
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
input · no output
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
input · no output
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.
input · no output
kickserv_get_task
Fetch one task (appointment / to-do attached to a job) by id. Kickserv: GET /{account}/tasks/{task_id}.xml.
input · no output
kickserv_list_customer_jobs
List the jobs for one customer, 30 per page. Kickserv: GET /{account}/customers/{customer_number}/jobs.xml.
input · no output
kickserv_list_customer_notes
List the notes on one customer. Kickserv: GET /{account}/customers/{customer_number}/notes.xml.
input · no output
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.
input · no output
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
input · no output
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.
input · no output
kickserv_list_job_notes
List the notes on one job. Kickserv: GET /{account}/jobs/{job_number}/notes.xml.
input · no output
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.
input · no output
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}/job
input · no output
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.
input · no output
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/
input · no output
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). Total
input · no output
Verify it yourselfnpx teppi-check https://kickserv.usefulapi.io/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M3RGE5C083PNAWVGW1748FTC