Swsd runs on your own machine — the client starts it, so there is no endpoint to ping. 522 installs a week from npm. Last commit 30 Oct 2026.
MCP server for SolarWinds Service Desk tickets, catalog, knowledge, ITSM operations, and workflows.
What the code does
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const m = ALIAS_RE.exec(input.trim());
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add swsd -e 'SWSD_TOKEN=<SWSD_TOKEN>' -- npx -y swsd-mcp{
"mcpServers": {
"swsd": {
"command": "npx",
"args": [
"-y",
"swsd-mcp"
],
"env": {
"SWSD_TOKEN": "<SWSD_TOKEN>"
}
}
}
}[mcp_servers.swsd]
command = "npx"
args = ["-y", "swsd-mcp"]
env = { SWSD_TOKEN = "<SWSD_TOKEN>" }{
"mcpServers": {
"swsd": {
"command": "npx",
"args": [
"-y",
"swsd-mcp"
],
"env": {
"SWSD_TOKEN": "<SWSD_TOKEN>"
}
}
}
}{
"servers": {
"swsd": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"swsd-mcp"
],
"env": {
"SWSD_TOKEN": "<SWSD_TOKEN>"
}
}
}
}Put your own value in place of
<SWSD_TOKEN> (SolarWinds Service Desk admin token (JWT). Generate in the SWSD UI: Setup -> Users & Groups -> Users -> [your user] -> Actions -> Generate JSON Web Token. Service Desk administrator rights required).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
SWSD_BASE_URL (SWSD API base URL. US tenants: https://api.samanage.com (default). EU tenants: https://apieu.samanage.com), SWSD_PROFILE (Tool registration profile: 'triage' (14 read-heavy tools), 'agent' (37 default), 'knowledge' (15 KB-author), 'operations' (64 ITSM operations tools), 'full' (66 every tool)), SWSD_WRITE_MODE (Write safety mode: 'live' calls SWSD normally; 'dry-run' returns write payload previews without sending writes; 'disabled' rejects write tools), SWSD_ATTACHMENT_ROOT (Optional real-path boundary for local file_path attachment uploads over stdio. Files outside this directory are rejected).
Alternatives to Swsd
same job, measured the same wayMCP server for HaloPSA — clients, tickets, and PSA workflows via the HaloPSA REST API.
MCP server for HaloPSA — clients, tickets, and PSA workflows via the HaloPSA REST API.
Rust MCP server and CLI for Unraid GraphQL operations across NAS, Docker, VM, and storage workflows.
Developer-workflow MCP server for catalyst-core: migration guidance, debugging, and task planning.
Persistent knowledge graph and MCP server for AI workflows with git-tracked project context.
Persistent knowledge graph and MCP server for AI workflows with git-tracked project context.
MCP server for Front: conversations, contacts, messages, tags, and inbox workflows.
MCP server for Prefect. Monitor and debug workflows, deployments, and automations.
Swsd — questions
Answers built from our own checks of this server.