Skip to main content
Glama
bitterdev

simple-support-system-mcp

by bitterdev

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SIMPLE_SUPPORT_SYSTEM_API_KEYNoAPI 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_PATHNoOptional. Overrides the default API path for sites that do not use the index.php dispatcher, for example /api/v1.
SIMPLE_SUPPORT_SYSTEM_BASE_URLYesRequired. 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_PROJECT_IDNoOptional. Limits the server to this one project. 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.
SIMPLE_SUPPORT_SYSTEM_TIMEOUT_MSNoOptional. Request timeout in milliseconds, default 30000.30000
SIMPLE_SUPPORT_SYSTEM_PROJECT_TOKENNoOptional. Default access token for private projects, used when a tool call passes no token of its own.

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_ticketsA

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.

get_ticketA

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.

reply_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.

set_ticket_stateA

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.

create_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.

update_ticketA

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.

delete_ticketA

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.

approve_ticketA

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

list_ticket_commentsA

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

update_commentA

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.

delete_commentA

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

approve_commentA

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

list_projectsA

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.

get_projectA

Read a single project by its numeric id.

create_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.

update_projectA

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.

delete_projectA

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.

list_ticket_attachmentsB

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

upload_attachmentA

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.

add_ticket_attachmentsA

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.

download_attachmentA

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.

delete_attachmentA

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.

get_server_infoA

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored 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
ResponsivenessNo issues