MCP.Market

Simple Support System MCP server

by bitterdev·io.github.bitterdev/simple-support-system-mcp·v1.0.3
No reviews yet

MCP server for the Simple Support System helpdesk API: read, answer and move tickets.

B78/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

0 stars23 downloads/wk

Reviews

Write one

Nobody has reviewed Simple Support System yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Simple Support System tools (23, 11 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • add_ticket_attachments

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

  • approve_comment

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

  • approve_ticket

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

  • create_projectwrite action

    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.

  • create_ticketwrite action

    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.

  • delete_attachmentwrite action

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

  • delete_commentwrite action

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

  • delete_projectwrite action

    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.

  • delete_ticketwrite action

    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.

  • download_attachment

    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.

  • get_project

    Read a single project by its numeric id.

  • get_server_info

    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.

  • get_ticket

    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.

  • list_projects

    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.

  • list_ticket_attachments

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

  • list_ticket_comments

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

  • list_tickets

    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.

  • reply_to_ticketwrite action

    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_state

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

  • update_commentwrite action

    Replace the text of an existing comment and notify the people involved. …

  • update_projectwrite action

    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.

  • update_ticketwrite action

    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. … Use set_ticket_state for the workflow state.

  • upload_attachmentwrite action

    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.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan17 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 59 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Simple Support System compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,255 servers
Tools
23
the typical server has 7
Tools that change things
48%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
23
more than 9% of 12,191 servers with a package

What its tools let an agent do: 8 read · 4 create · 6 change · 4 delete · 1 send or post

Install Simple Support System in Claude Code, Cursor or VS Code

Runs npx -y simple-support-system-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add simple-support-system-mcp -- npx -y simple-support-system-mcp
Add to Cursor

What the publisher says

From the Simple Support System repository's README, as published. We do not edit it. Read it on GitHub

<!-- Author: Fabian Bitter (fabian@bitter.de) -->

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

Register the server in Claude Code:

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 / claudedesktopconfig.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"
      }
    }
  }
}

Environment

The API key is generated when the package is installed and lives in the site config under simplesupportsystem.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 listtickets, getticket and replytoticket, plus setticketstate to move a ticket along.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Simple Support System: common questions

Is Simple Support System MCP server safe?
Mostly: it is graded B (78/100). Read the Simple Support System safety report
How do I install Simple Support System?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Simple Support System need an API key?
Yes. The registry entry asks for SIMPLE_SUPPORT_SYSTEM_API_KEY, SIMPLE_SUPPORT_SYSTEM_PROJECT_TOKEN.
Is Simple Support System maintained?
The last commit was 100 days ago (2026-07-27). The latest release is v1.0.3.
How does Simple Support System compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,255 servers); tools 23 (the typical server has 7); tools that change things 48% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from bitterdev →