SolarWinds Service Desk logoMCP server · Support

SolarWinds Service Desk MCP server

SolarWinds Service Desk in any MCP client, through Memtro: SolarWinds Service Desk does not publish this server. Memtro's SolarWinds Service Desk connector reads SolarWinds Service Desk through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

SolarWinds Service Desk (Samanage) IT service management: incidents and service requests by update or creation date with state, priority, category, assignee, group, requester and SLA breaches, one incident in full, problems, changes, knowledge base solutions, hardware assets, users by name and role, and time logged on a record; when you ask, can create, update or delete an incident, comment on an incident, problem or change (privately, or notifying people), log time, add or complete a task, and create a problem or a solution article.

Reads

  • solarwindssd_list_incidentsService Desk incidents and service requests: number, title, state, priority, category, assignee, group, requester, site, created…
  • solarwindssd_get_incidentOne Service Desk incident in full: everything in the list plus the longer description, resolution and code, SLA breaches…
  • solarwindssd_list_problemsService Desk problems (the cause behind repeated incidents): state, priority, assignee, group, root cause, symptoms and workaround.
  • solarwindssd_list_changesService Desk changes: state, priority, assignee, group, planned start and end, change and rollback plans.
  • solarwindssd_list_solutionsKnowledge base solutions (articles): title, state, author and the start of the text.
  • solarwindssd_list_hardwareHardware assets: name, status, asset tag, category, site, department, operating system, CPU and memory.
  • solarwindssd_list_usersService Desk users by name, role, site and department.
  • solarwindssd_list_time_tracksTime logged on an incident, problem, change or release: what, how long, when and by whom.

Acts, when you ask

These change something in SolarWinds Service Desk. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • solarwindssd_create_incidentOpens an incident in Service Desk for the service desk team to work; API calls send no notifications by default…
  • solarwindssd_update_incidentChanges a Service Desk incident: state (by state id), priority, assignee, group, category, due date, title or description, or adds and removes tags…
  • solarwindssd_delete_incidentPermanently deletes a Service Desk incident with its comments, tasks and time.
  • solarwindssd_add_commentComments on a Service Desk incident, problem, change or release.
  • solarwindssd_log_timeLogs time against a Service Desk incident, problem, change or release, as the token's user.
  • solarwindssd_add_taskAdds a task to a Service Desk incident, problem, change or release, optionally assigned to someone (by email) with a due date…
  • solarwindssd_complete_taskMarks a task on a Service Desk record as complete, or reopens it with complete false.
  • solarwindssd_create_problemOpens a problem record in Service Desk (the underlying cause of incidents), optionally linking incidents by id.
  • solarwindssd_create_solutionWrites a knowledge base solution article in Service Desk; once its state is approved it can be shown to end users in the service portal.

Connect it

First connect SolarWinds Service Desk on Dashboard → Connections, then add Memtro to your client once. The SolarWinds Service Desk tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared SolarWinds Service Desk connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › Which high priority incidents were updated today?
  • › Is there a known fix for VPN drop-outs?
  • › What changes are planned for this weekend?
  • › How much time was logged on incident 4512?
  • › Raise an incident for the broken printer on the third floor.

Questions

Is this an official SolarWinds Service Desk MCP server?
No. It is Memtro's MCP server with Memtro's SolarWinds Service Desk connector behind it: the connector reads SolarWinds Service Desk through its API with the credentials you connect on Dashboard → Connections, and SolarWinds Service Desk publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in SolarWinds Service Desk?
Only when you ask, and only what it has been granted: create an incident; update an incident's state, priority, assignee, category, due date or tags; delete an incident; comment on an incident, problem or change; log time on an incident, problem or change; add a task to an incident, problem or change; complete or reopen a task; create a problem; create a knowledge base solution. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Support

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time