MCP server for the Simple Support System helpdesk API: read, answer and move tickets.
MCP server for the Simple Support System helpdesk API: read, answer and move tickets. That is what the simple mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Local MCP server (stdio) for the REST API of the Simple Support System add-on for Concrete CMS. It lets an assistant work a support queue the way a human would: find the ticket, read it with its history, write a reply, move it to the next state. Projects, attachments and moderation are covered as well.
The server publishes 14 tools. What each one is for:
States — new, open, in_progress, on_hold, resolved, duplicate, invalid, wont_fix, closed. set_ticket_state accepts all of them except new, which is only setTypes — bug, enhancement, proposal, taskPriorities — trivial, minor, major, critical, blockerlist_tickets — Lists tickets with filters for project, state, type, priority, assignee, text search and change date, sorted and paged. Compact summaries by defaultget_ticket — Reads one ticket with its attachments and, unless switched off, all of its commentsreply_to_ticket — Posts a reply as a comment on a ticket and triggers the notification mailsset_ticket_state — Moves a ticket to another workflow state and notifies everyone involvedcreate_ticket — Creates a ticket in a project, by project id or project handle, optionally with uploaded filesupdate_ticket — Changes title, content, type, priority or assignee. Only the given fields are touchedapprove_ticket — Approves a moderated ticketdelete_ticket — Deletes a ticket with all comments and attachment links. Irreversible, needs confirm: truelist_ticket_comments — Lists the comments of a ticketConfiguration is passed through the environment: SIMPLE_SUPPORT_SYSTEM_BASE_URL, SIMPLE_SUPPORT_SYSTEM_API_KEY, SIMPLE_SUPPORT_SYSTEM_API_PATH, SIMPLE_SUPPORT_SYSTEM_PROJECT_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
npm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Simple's toolset — States, Types, Priorities and 11 more — is a fair guide to whether it matches your workflow. It is maintained by bitterdev; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| States | new, open, in_progress, on_hold, resolved, duplicate, invalid, wont_fix, closed. set_ticket_state accepts all of them except new, which is only set when a ticket is created. |
| Types | bug, enhancement, proposal, task |
| Priorities | trivial, minor, major, critical, blocker |
| list_tickets | Lists tickets with filters for project, state, type, priority, assignee, text search and change date, sorted and paged. Compact summaries by default. |
| get_ticket | Reads one ticket with its attachments and, unless switched off, all of its comments. |
| reply_to_ticket | Posts a reply as a comment on a ticket and triggers the notification mails. |
| set_ticket_state | Moves a ticket to another workflow state and notifies everyone involved. |
| create_ticket | Creates a ticket in a project, by project id or project handle, optionally with uploaded files. |
| update_ticket | Changes title, content, type, priority or assignee. Only the given fields are touched. |
| approve_ticket | Approves a moderated ticket. |
| delete_ticket | Deletes a ticket with all comments and attachment links. Irreversible, needs confirm: true. |
| list_ticket_comments | Lists the comments of a ticket. |
| update_comment | Replaces the text of a comment. |
| approve_comment | Approves a moderated comment. |
{
"mcpServers": {
"simple-support-system": {
"command": "node",
"args": ["/absolute/path/to/simple-support-system-mcp/dist/src/index.js"],
"env": {
"SIMPLE_SUPPORT_SYSTEM_BASE_URL": "https://support.example.com",
"SIMPLE_SUPPORT_SYSTEM_API_KEY": "your-api-key"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SIMPLE_SUPPORT_SYSTEM_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| SIMPLE_SUPPORT_SYSTEM_API_KEY | Credential the server authenticates with. | Yes |
| SIMPLE_SUPPORT_SYSTEM_API_PATH | Filesystem location the server is allowed to use. | Optional |
| SIMPLE_SUPPORT_SYSTEM_PROJECT_TOKEN | Credential the server authenticates with. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.