Simple Support System MCP

What simple-support-system-mcp MCP server does

The simple-support-system-mcp MCP server gives an MCP-compatible assistant access to a Simple Support System installation running on Concrete CMS. It covers the main support workflow: finding tickets, reading their comments and attachments, replying, and moving tickets through workflow states. It also supports ticket creation and editing, project administration, moderation, and attachment handling.

Ticket searches can be filtered by project, state, type, priority, assignee, text, and change date. Results support sorting and pagination, with compact summaries available by default. Ticket reads can include the full comment history and attached files. Replies trigger the helpdesk's notification emails, and state changes notify the people involved.

How it works

The process runs as a local Node.js program and communicates through stdio. It does not open a listening port. Requests are sent to the configured Simple Support System REST API, whose response formats and error envelopes are normalized before results are returned to the client.

The API base URL comes from configuration. By default, the server appends /index.php/api/v1; an existing /api/v1 suffix is preserved, and a custom API path can be supplied for installations with a different dispatcher. Creating a ticket returns a status response rather than the new record, so callers must use ticket listing to find the created ticket's ID.

Setup and configuration

Install dependencies and compile the project with npm install followed by npm run build. Register the compiled entry point in an MCP client, passing the server's environment variables in that client's configuration.

SIMPLE_SUPPORT_SYSTEM_BASE_URL is required and identifies the Concrete CMS site. SIMPLE_SUPPORT_SYSTEM_API_KEY is optional; when present, it is sent as the X-Api-Key header and enables administrative operations. Without it, anonymous access can still read public projects and approved tickets, create tickets, and write comments, but cannot change states, approve, delete, or manage projects.

SIMPLE_SUPPORT_SYSTEM_API_PATH overrides the default API path. SIMPLE_SUPPORT_SYSTEM_PROJECT_TOKEN supplies a default token for private projects when a tool call does not provide one. SIMPLE_SUPPORT_SYSTEM_TIMEOUT_MS changes the request timeout from its 30-second default.

Tools and capabilities

The simple-support-system-mcp MCP server exposes tools for:

• Listing, reading, creating, updating, replying to, approving, and deleting tickets.
• Listing, editing, approving, and deleting ticket comments.
• Listing, creating, updating, reading, and deleting support projects.
• Uploading files, linking them to tickets, listing attachments, downloading them, and removing them.
• Inspecting the configured API URL, key presence, and accepted ticket values through get_server_info.

Accepted ticket types are bug, enhancement, proposal, and task. Priorities range from trivial to blocker. Workflow states include new, open, in_progress, on_hold, resolved, duplicate, invalid, wont_fix, and closed; new is creation-only. Closed and invalid tickets cannot be edited until their state changes.

Limitations and notes

Deletion of tickets, comments, projects, or attachments is irreversible and requires confirm: true. The API has no trash or restore function. Project deletion also removes all tickets and comments inside that project.

Private projects require their access token unless an API key grants full access. Uploaded files are initially placed in the site's file manager; a separate attachment operation links them to a ticket. Tests use a stubbed HTTP layer and do not require live credentials.