customer-support-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_customer_toolA | Create a new customer record. |
| get_customer_toolA | Fetch a customer by their id. |
| get_ticket_details_toolA | Get full context for a ticket: details, customer info, and all comments. |
| get_knowledge_articles_toolA | Read support knowledge-base articles for a category. |
| list_customers_toolA | List customers, optionally filtered by status. |
| create_ticket_toolB | Create a support ticket for an existing customer. |
| list_tickets_toolA | List tickets with optional filters. Use this to find tickets matching criteria. |
| get_ticket_toolC | Fetch a single ticket by id. |
| assign_ticket_toolC | Assign a ticket to a support team. |
| add_comment_toolC | Add a comment to a ticket. |
| change_ticket_status_toolA | Change a ticket's status. Only valid transitions are allowed. |
| resolve_ticket_toolC | Mark a ticket as resolved. |
| delete_ticket_toolA | Permanently delete a ticket and all its comments. Destructive and irreversible. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| triage_ticket | Triage a support ticket: assess, categorize, and recommend next steps. Args: ticket_id: The ticket to triage. |
| daily_queue_review | Review the open ticket queue and produce a prioritized action list. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Most tools are distinct, but get_ticket_tool and get_ticket_details_tool overlap, as do resolve_ticket_tool and change_ticket_status_tool. The descriptions provide clear guidance on when to use each, so an agent can disambiguate, though slight redundancy exists.
All tool names follow a consistent verb_noun pattern with snake_case, e.g., get_customer_tool, list_tickets_tool, change_ticket_status_tool. No mixed conventions or irregular verbs.
With 13 tools covering customers, tickets, comments, assignments, and knowledge articles, the count is well-scoped for a customer support server. Each tool serves a clear purpose without excessive redundancy.
The surface covers core customer and ticket lifecycles: create/get/list for customers, full ticket management (create, list, get, status changes, resolve, assign, comment, delete). Minor gaps include no update/delete for customers and no ability to modify ticket content, but these are not critical for typical support workflows.