swsd-mcp

MCP server for SolarWinds Service Desk (SWSD / Samanage). Works with any Model Context Protocol client to read and modify SWSD tickets, comments, knowledge-base articles, and more, using each user's own SWSD API token. See the client compatibility matrix for the tested list.

📖 Full docs: mcp-swsd.pages.dev

The server holds zero credentials at rest. Tokens are forwarded per-request, never persisted, never logged, and only sent to the configured SWSD API host.

Quick start

You need:

• An MCP client installed — any MCP-compatible client works (compatibility matrix)
• A SolarWinds Service Desk admin token (JWT) — generate one in the SWSD UI: Setup → Users & Groups → Users → click your user → Actions → Generate JSON Web Token (Service Desk administrator rights required)

1. Add the config

Every stdio-capable MCP client uses the same JSON shape. Add this under mcpServers in your client's config file:

{
  "mcpServers": {
    "swsd": {
      "command": "npx",
      "args": ["-y", "swsd-mcp"],
      "env": {
        "SWSD_TOKEN": "your-jwt-here",
        "SWSD_BASE_URL": "https://api.samanage.com"
      }
    }
  }
}

Replace your-jwt-here with your token. EU tenants use https://apieu.samanage.com instead. To customize behavior, add any configuration variable (most common: SWSD_PROFILE to choose the tool set) into the same env block.

2. Drop it in the right file

Create the file if it doesn't exist. Then restart your client.

Claude Code shortcut — skip editing the file by hand. This single line pastes verbatim into any shell (bash, zsh, PowerShell, cmd):

claude mcp add swsd --env SWSD_TOKEN="your-jwt-here" --env SWSD_BASE_URL="https://api.samanage.com" -- npx -y swsd-mcp

Microsoft Copilot Studio — different path. Copilot Studio can't spawn local processes, so it needs an HTTP-transport server. See copilot-studio/README.md and the Azure Container Apps recipe.

3. Verify it works

In your MCP client, ask:

"Use swsd to check if you can connect."

The agent should call swsd_health_check and report success. If it does, you're set up. Try a few more:

• "Show me incident 60310" — id-keyed tools accept either the internal id (≥7 digits) or the human-facing number visible in the SWSD UI (≤6 digits).
• "List incidents updated in the last 7 days" — updated_within: "7d" (also "24h", "1w", "30d").
• _"What tickets a

... View full README on GitHub