kickserv-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KICKSERV_ACCOUNT | No | Your Kickserv account slug. Required for live mode. | |
| KICKSERV_API_TOKEN | No | Your Kickserv API token. Required for live mode. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_customersA | List customers, optionally filtered by a search term (name, contact, email, or address). |
| get_customerA | Get full details for one customer by ID. |
| list_jobsA | List jobs, filterable by status and/or customer. |
| get_jobA | Get full details for one job by ID. |
| create_jobC | Create a new job for a customer. Returns the created job record. |
| list_invoicesA | List invoices, filterable by status (open | paid | overdue) and/or customer. |
| revenue_snapshotA | Summarize money state: total open, overdue, and paid invoice amounts, plus pipeline value of unfinished jobs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: creating jobs, fetching individual customers or jobs, listing entities with filters, and a revenue summary. No two tools overlap in function.
All tools use lowercase with underscores; most follow verb_noun pattern (e.g., create_job, list_customers). 'revenue_snapshot' is a noun_noun exception, but the overall style is consistent and predictable.
With 7 tools covering customers, jobs, invoices, and a revenue report, the count is well-scoped for a focused business management service. It's neither too sparse nor overwhelming.
The tool set lacks update and delete operations for all entities, and there is no way to create a customer or invoice. This creates significant gaps in typical CRUD workflows that agents would likely need.