swsd-mcp

Plug SolarWinds Service Desk into any Model Context Protocol client. Zero credentials at rest.

Any MCP client

Standard Model Context Protocol — works wherever MCP works. See the compatibility matrix →

Zero credentials at rest

Each user’s SWSD token is forwarded per-request, never persisted, never logged.

Profile-scoped tools

Pick triage, agent, knowledge, or full to control which of the 35 tools across 10 categories each deployment exposes.

MCP Apps UI

Seven read tools ship rich UI bundles for capable hosts — incident detail, solution detail, incident list, comment thread, audit timeline, catalog-item form, custom-field explorer. Text-only clients are unaffected.

Service Catalog

Browse, inspect, and submit catalog requests with swsd_list_catalog_items, swsd_get_catalog_item, and swsd_create_service_request.

Self-hostable

Stdio for local agents, Streamable HTTP for hosted/Copilot Studio. Docker image and Azure Container Apps recipe included.

Listed on the MCP Registry

Find swsd-mcp in MCP host install pickers via registry.modelcontextprotocol.io.

See it in action

The seven MCP Apps widgets render rich UI alongside structured tool output. Below: a few captured with synthetic example data (“Acme Corp”). The full gallery + per-widget detail lives on the Widgets reference.

incident-list widget showing a sortable table of Acme Corp tickets

comment-thread widget showing a threaded conversation between Alex Kim and Jane Doe

audit-timeline widget showing a vertical timeline of ticket state changes

catalog-item-form widget rendering a "New laptop request" form with dropdowns and helptext