How do I use simple-support-system-mcp?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@simple-support-system-mcp list open support tickets" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

simple-support-system-mcp

by bitterdev

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

simple-support-system-mcp

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 talks to any site that runs the package. Nothing is hardcoded, the site URL and the API key come from environment variables. It speaks stdio only and never opens a port.

Install

npm install
npm run build

claude mcp add simple-support-system \
  -e SIMPLE_SUPPORT_SYSTEM_BASE_URL=https://support.example.com \
  -e SIMPLE_SUPPORT_SYSTEM_API_KEY=your-api-key \
  -- node "/absolute/path/to/simple-support-system-mcp/dist/src/index.js"

Or in ~/.claude.json / claude_desktop_config.json:

{
  "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"
      }
    }
  }
}

Related MCP server: Project Planner MCP

Environment

Variable	Purpose
`SIMPLE_SUPPORT_SYSTEM_BASE_URL`	Required. Base URL of the Concrete CMS site, for example `https://support.example.com`. The API path `/index.php/api/v1` is appended automatically, a URL that already ends in `/api/v1` is used as it is.
`SIMPLE_SUPPORT_SYSTEM_API_KEY`	API key of the installation, sent as the `X-Api-Key` header. Without it only the public part of the API is reachable.
`SIMPLE_SUPPORT_SYSTEM_API_PATH`	Optional. Overrides the default API path for sites that do not use the `index.php` dispatcher, for example `/api/v1`.
`SIMPLE_SUPPORT_SYSTEM_PROJECT_TOKEN`	Optional. Default access token for private projects, used when a tool call passes no token of its own.
`SIMPLE_SUPPORT_SYSTEM_PROJECT_ID`	Optional. Limits the server to this one project, see Limiting the server to one project.
`SIMPLE_SUPPORT_SYSTEM_TIMEOUT_MS`	Optional. Request timeout in milliseconds, default `30000`.

The API key is generated when the package is installed and lives in the site config under simple_support_system.api_key. Calls without it run as an anonymous visitor: reading public projects and their approved tickets, creating tickets and writing comments still work, everything administrative (state changes, deleting, approving, projects) does not.

Tools

The three everyday tools are list_tickets, get_ticket and reply_to_ticket, plus set_ticket_state to move a ticket along.

Tool	Purpose
`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.
`delete_comment`	Deletes a comment. Irreversible, needs `confirm: true`.
`list_projects`	Lists the support projects, with access tokens when an API key is configured.
`get_project`	Reads one project by id.
`create_project`	Creates a project, private projects get a generated access token.
`update_project`	Changes name, handle or visibility of a project.
`delete_project`	Deletes a project with every ticket and comment inside it. Irreversible, needs `confirm: true`.
`list_ticket_attachments`	Lists the files attached to a ticket.
`upload_attachment`	Uploads a local file into the file manager and returns its file id.
`add_ticket_attachments`	Links uploaded file ids to a ticket.
`download_attachment`	Resolves the download URL of an attachment and can save it to a local path.
`delete_attachment`	Removes a file from a ticket. Irreversible, needs `confirm: true`.
`get_server_info`	Shows the configured API URL, whether a key is present and the accepted states, types and priorities. The key itself is never returned.

Reading tools are annotated as read only, the four delete_ tools as destructive. All of them additionally require confirm: true, so a delete cannot happen as a side effect of a vague instruction. There is no trash and no restore on the API side, a deleted ticket, comment or project is gone.

Working a ticket

list_tickets   { "state": "open", "sortBy": "updatedAt" }
get_ticket     { "ticketId": 42 }
reply_to_ticket{ "ticketId": 42, "comment": "Thanks for the report, we are on it." }
set_ticket_state { "ticketId": 42, "state": "in_progress" }

list_tickets also takes projectHandle instead of projectId and resolves it through the project list first.

Values the API accepts

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
Tickets in the state closed or invalid are locked: the API refuses edits of the ticket, its comments and its attachments until the state changes.

Attachments

upload_attachment      { "filePath": "/tmp/screenshot.png" }      -> fileId
add_ticket_attachments { "ticketId": 42, "fileIds": [123] }

upload_attachment puts the file into the file manager of the site without linking it anywhere, the second call attaches it. create_ticket takes the same ids in attachmentFileIds.

Private projects

A private project is only reachable with its access token. Pass it per call as token, or set SIMPLE_SUPPORT_SYSTEM_PROJECT_TOKEN as the default. With an API key the token is not needed, the key already grants full access.

Limiting the server to one project

Set SIMPLE_SUPPORT_SYSTEM_PROJECT_ID to hand the server to someone who should only work in one project, typically together with that project's access token and without an API key. list_tickets and create_ticket then use this project when none is given, list_projects shows only this project, and every tool that takes a ticket id first checks that the ticket belongs to it. A different project id or handle is rejected. Without an API key the site itself already keeps other private projects closed, the setting additionally keeps the public projects of the installation out of view.

Notes on the API

The package answers in several shapes, the server normalises all of them so tools return the bare resource:

Collections come back as a plain array, single tickets and comments inside a ticket or comment key, attachments inside data.
Failures arrive either as {"errors": [...]} or as a Concrete EditResponse with an error flag. The second one can come with status 200, so a 200 alone is not treated as success. Every error becomes a tool error with the message the API sent.
create_ticket answers with a status envelope and not with the new record, so the id of a freshly created ticket has to be looked up with list_tickets.
download_attachment follows the redirect the API returns and reports the resolved URL.

Verification

npm run build
npm test

The tests run against a stubbed HTTP layer, they never touch a live site and need no credentials. They cover the URL and form encoding the PHP controllers expect (including PHP boolean and array notation), the response envelopes, the error mapping, the filtering and sorting of list_tickets, and the guard rails of the destructive tools.

License

MIT, see LICENSE.

Available Tools

23 tools

add_ticket_attachmentsAttach files to a ticketA

Link already uploaded files to a ticket by their file ids. Files that are attached already are skipped, and the API rejects a call that would add nothing. Tickets in the states closed or invalid are locked by the API and reject edits.

Inputs: fileIds (required), ticketId (required), token.

approve_commentApprove commentA

Idempotent

Approve a moderated comment so it becomes publicly visible. Requires an API key.

Inputs: commentId (required).

approve_ticketApprove ticketA

Idempotent

Approve a moderated ticket so it becomes visible and editable through the API. Requires an API key.

Inputs: ticketId (required).

create_projectCreate projectA

Create a support project. The handle has to be unique, a duplicate is rejected with status 409. A private project gets an access token generated by the API, which is returned in the response. Requires an API key.

Inputs: name (required), handle (required), isPrivate.

create_ticketCreate ticketA

Create a new ticket in a project, identified by projectId or projectHandle. Attachments have to be uploaded first with upload_attachment, then passed as attachmentFileIds. The API answers with a status envelope and not with the new ticket, so use list_tickets afterwards to get the id.

Inputs: title (required), content (required), ticketType (required), ticketPriority (required), +5 more.

delete_attachmentDelete an attachmentA

DestructiveIdempotent

Remove a file from a ticket. The link between ticket and file is gone for good and cannot be restored from here, the file itself stays in the file manager of the site. Requires confirm set to true. Tickets in the states closed or invalid are locked by the API and reject edits.

Inputs: fileId (required), confirm (required), ticketId (required), token.

delete_commentDelete commentA

DestructiveIdempotent

Permanently delete a comment from a ticket. This cannot be undone, the text is gone afterwards. Requires confirm set to true.

Inputs: confirm (required), ticketId (required), commentId (required).

delete_projectDelete projectA

DestructiveIdempotent

Permanently delete a project together with every ticket, every comment and every attachment link inside it. This is the most destructive call of the whole API, it cannot be undone. Requires an API key and confirm set to true.

Inputs: confirm (required), projectId (required).

delete_ticketDelete ticketA

DestructiveIdempotent

Permanently delete a ticket together with all its comments and attachment links. This cannot be undone, there is no trash and no restore. Requires an API key and confirm set to true. Prefer set_ticket_state with "closed" or "invalid" unless the record really has to disappear.

Inputs: confirm (required), ticketId (required).

download_attachmentDownload an attachmentA

Read-only

Resolve the download URL of a ticket attachment and, when outputPath is given, save the file to that local path. Without outputPath only the URL is returned.

Inputs: fileId (required), ticketId (required), token, outputPath.

get_projectGet projectA

Read-only

Read a single project by its numeric id.

Inputs: projectId (required), token.

get_server_infoServer infoA

Read-only

Show how this server is configured: the API base URL it talks to, whether an API key is present, and the ticket states, types and priorities the API accepts. The API key itself is never returned.

Inputs: no named parameters.

get_ticketGet ticketA

Read-only

Read a single ticket with its attachments and, unless switched off, all comments in one call. Use this before replying or changing a state so the current content and state are known.

Inputs: ticketId (required), token, includeComments.

list_projectsList projectsA

Read-only

List the support projects. With an API key all projects are returned including private ones and their access tokens, otherwise only public projects and those matching the given token.

Inputs: token.

list_ticket_attachmentsList ticket attachmentsB

Read-only

List the files attached to a ticket, with their file id, file name and public URL.

Inputs: ticketId (required), token.

list_ticket_commentsList ticket commentsA

Read-only

List the comments of a ticket, oldest first as the API returns them. With an API key unapproved comments are included as well.

Inputs: ticketId (required), token.

list_ticketsList ticketsA

Read-only

List tickets, optionally filtered by project, state, type, priority, assignee or a text search. The API itself only filters by project, every other filter is applied by this server on the returned list. Returns a compact summary per ticket by default, set format to "full" for the complete records including attachments. This is the default way to find a ticket id.

Inputs: limit, state, token, format, +12 more.

reply_to_ticketReply to ticketA

Post a reply as a comment on a ticket. This is the normal way to answer a ticket. The reply triggers the notification mails of the package. Without an API key and without a logged in session the email field is required, and moderation may hold the comment back until it is approved.

Inputs: comment (required), ticketId (required), email, token.

set_ticket_stateChange ticket stateA

Idempotent

Move a ticket to another workflow state and notify the people involved. Requires an API key. The state "new" is only set when a ticket is created and is rejected here. Tickets in the states closed or invalid are locked by the API and reject edits.

Inputs: state (required), ticketId (required).

update_commentUpdate commentA

Idempotent

Replace the text of an existing comment and notify the people involved. Tickets in the states closed or invalid are locked by the API and reject edits.

Inputs: content (required), ticketId (required), commentId (required).

update_projectUpdate projectA

Idempotent

Change name, handle or visibility of a project. Only the given fields are touched. Switching a public project to private generates an access token. Requires an API key.

Inputs: projectId (required), name, handle, isPrivate.

update_ticketUpdate ticketA

Idempotent

Change title, content, type, priority or assignee of a ticket. Only the given fields are touched, and the API rejects a call that changes nothing. Set assigneeUserId to null to unassign. Tickets in the states closed or invalid are locked by the API and reject edits. Use set_ticket_state for the workflow state.

Inputs: ticketId (required), title, content, ticketType, +2 more.

upload_attachmentUpload a fileA

Upload a local file into the file manager of the site and return its file id. The file is not linked to a ticket yet, pass the id to add_ticket_attachments or to create_ticket.

Inputs: filePath (required), fileName.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored 2026-10-19 11:50 across 23 tools

Disambiguation5/5

Each tool targets a distinct resource+action across tickets, comments, projects, and attachments, and descriptions clarify the boundaries (e.g., reply_to_ticket creates a comment while update_comment edits it, upload_attachment vs add_ticket_attachments vs delete_attachment are cleanly separated). An agent can reliably pick the right tool without guessing.

Naming Consistency5/5

Consistent snake_case verb-first naming throughout: list_/get_/create_/update_/delete_ for resources, plus clear action verbs like set_ticket_state, reply_to_ticket, approve_ticket. The only deviations (list_ticket_comments, add_ticket_attachments) follow the same pattern.

Tool Count4/5

23 tools is on the heavier side, but the surface spans four resources (tickets, comments, projects, attachments) each needing full lifecycle plus moderation and state handling, so nearly every tool earns its place. Slightly over the comfortable range but justified by scope.

Completeness4/5

Strong coverage: full CRUD for tickets and projects, comment management with moderation, attachment upload/link/download/delete lifecycle, and state transitions. Minor gaps remain, such as no way to list users to resolve assigneeUserId and no standalone create_comment (covered by reply_to_ticket).

Maintenance

ActivityMaintained

ResponsivenessOutdated data

Resources

Related MCP Connectors

Muninx MCP ServerA
com.muninx
Remote MCP server for managing Muninx tickets, messages, ticket search, and support analytics.
Customer Support Project Management
82
https://api.muninx.com/mcp
canhelpto support inbox
com.canhelpto
Customer support for MCP servers: work your tickets from Claude or any MCP client. Service key auth.
Customer Support Email
1
https://canhelpto.com/api/mcp
NexTool MCP for GLPIB
com.nextoolsolutions
MCP server for GLPI: tickets, ITIL, assets, knowledge base. GLPI 10/11. Not affiliated with Teclib'.
Customer Support Documentation Access Project Management
10211
https://mcp.nextoolsolutions.com/mcp
Support Service Management McpD
io.github.varvararatta
MCP server for Support & Service Management
Customer Support Project Management
2
https://support-service-management-mcp.mcpize.run/mcp

Related MCP Servers

swsd-mcp
Customer Support CRM
mikimatsub
A
license
A
quality
B
maintenance
MCP server for SolarWinds Service Desk (SWSD/Samanage) enabling reading and modifying tickets, comments, knowledge-base articles, and more via each user's own API token.
Updated 2 days ago (2026-11-09 16:49 UTC)
52
1,719 npm
4
MIT
Project Planner MCP
Developer Tools Project Management Code Analysis
brnbio
A
license
A
quality
D
maintenance
MCP server for structured Laravel project planning. Scans projects, creates tickets, and exports as JSON.
Updated 10 months ago (2026-01-19 19:25 UTC)
3
5 npm
MIT
kanban-mcp
Project Management Developer Tools
Rafael09ED
A
license
Not graded
quality
D
maintenance
MCP server for task/ticket management with dependency tracking, supporting CRUD operations, status management, project filtering, and automatic data migrations.
Updated a year ago (2025-07-24 03:11 UTC)
21 npm
1
AGPL 3.0
ticksy-mcp
Customer Support CRM
artkrsk
A
license
A
quality
D
maintenance
MCP server for the Ticksy support ticket API, enabling AI agents to read and write support tickets.
Updated 4 months ago (2026-07-24 16:18 UTC)
16
8 npm
MIT

simple-support-system-mcp

Install

Environment

Tools

Working a ticket

Values the API accepts

Attachments

Private projects

Limiting the server to one project

Notes on the API

Verification

License

Available Tools

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

swsd-mcp

Project Planner MCP

kanban-mcp

ticksy-mcp