What you can do with SolarWinds Service Desk

Built for

IT Service Desk Managers, IT Support Teams, CMDB Administrators, IT Operations

Example workflows

Morning incident triage

Turns the incident backlog into a standup brief before agents open the console.

Try this

List open incidents in SolarWinds Service Desk sorted by priority, summarize counts by status, and flag anything unassigned.

Problem linked to repeat tickets

Connects root-cause work to the live ticket queue.

Try this

Show recent problems in SolarWinds Service Desk and summarize any with multiple related incidents still open.

CMDB before a change

Grounds change planning in live asset and dependency data.

Try this

Find configuration items and hardware tied to our London site in SolarWinds Service Desk before we schedule a network change.

Knowledge for a repeat issue

Pulls knowledge-base answers before drafting a user reply.

Try this

Search SolarWinds Service Desk solutions for VPN login failures and summarize the top matching articles.

Context to know first

What can AI agents do with SolarWinds Service Desk?

Agents can list or fetch incidents, problems, changes, releases, and risks; manage hardware, mobile devices, other assets, and configuration items; look up users, groups, departments, sites, contracts, vendors, and purchase orders; search knowledge solutions; add timeline comments; and create or update records when you ask.

How do I connect SolarWinds Service Desk on MCPBundles?

In SolarWinds Service Desk, open Setup → Users & Groups → Users, choose Generate token, and paste it when you connect on MCPBundles. Pick the region that matches your tenant — United States, Europe, or Asia-Pacific.

Which SolarWinds Service Desk workflows should agents run first?

Start with read-only queue reviews: open incidents, assignment groups, and knowledge articles. Move to writes — new incidents, comments, asset updates — only after you confirm the target record in a follow-up prompt.

Related editorial

SolarWinds Service Desk ITSM Workflows with AI

How AI agents can triage incidents, trace problems and changes, review CMDB inventory, and pull knowledge articles from your service desk tenant.

Read article

AI Skill
SKILL.md

Domain knowledge for SolarWinds Service Desk — workflow patterns, data models, and gotchas for your AI agent.

SolarWinds Service Desk

Cloud-based ITSM platform following ITIL practices. Manages the full IT service lifecycle: incident → problem → change → release, plus asset management and procurement.

Entity Model

Service Management (ITIL)
  • Incidents — service disruption reports. Lifecycle: New → Assigned → In Progress → Resolved → Closed. Priority/severity levels drive SLA timers.
  • Problems — root cause investigations linked to multiple incidents. Lifecycle mirrors incidents with additional root cause analysis fields.
  • Changes — planned modifications to IT infrastructure. Full CAB workflow: Requested → Planned → Approved → Implementing → Completed.
  • Releases — bundled changes deployed together. Tracks deployment scheduling and success/rollback status.
  • Risks — risk register entries with impact/probability assessments. Can link to changes and releases.
Asset Management / CMDB
  • Assets — general IT assets (software licenses, cloud resources).
  • Hardwares — physical IT equipment (servers, laptops, monitors) with specs, warranty, and location.
  • Mobiles — mobile devices (phones, tablets) with carrier, IMEI, and MDM data.
  • Configuration Items — CMDB entries with relationships to other CIs. The authoritative record for infrastructure dependencies.
  • Catalog Items — requestable items in the self-service portal (new laptop, software access, etc.).
Procurement
  • Contracts — vendor agreements with renewal dates, cost, and linked assets.
  • Vendors — supplier directory with contact info and contract relationships.
  • Purchase Orders — procurement requests linked to vendors and budget lines.
Organization
  • Users — service desk agents and end users.
  • Groups — assignment groups for routing incidents/changes.
  • Roles — permission sets assigned to users.
  • Departments — organizational structure for reporting and assignment.
  • Sites — physical locations. Assets and users are associated with sites.
  • Categories — hierarchical taxonomy for classifying incidents, changes, and assets.
  • Solutions — knowledge base articles for known issue resolution.
  • Audits — change audit trail across all entities.
  • Change Catalogs — templates for standard/pre-approved changes.

Operational order

  1. Ticket work: get_incidents / get_problems / get_changes to list queues; pass id on the same tool for detail; upsert_* to create (omit id) or update (pass id); upsert_comment for timeline notes; delete_* only when retiring test or duplicate rows.
  2. Knowledge: get_solutions before drafting agent replies; upsert_solution to publish or revise articles.
  3. Assets / CMDB: get_hardwares, get_other_assets, and get_configuration_items for inventory; asset upserts need upstream-required fields (hardware serial, other_asset manufacturer + asset_type).
  4. Org routing: get_groups, get_users, get_departments, get_sites for assignment context; categories and roles are read-only directory lookups.
  5. Procurement: get_vendors, get_contracts, get_purchase_orders for spend and renewal reviews.
  6. Compliance: get_audits is read-only tenant-wide change history.

Gotchas

  • Regional API host: Token auth routes to a regional API base — US https://api.samanage.com, EU https://apieu.samanage.com, APAC https://apiau.samanage.com. Match the region to the tenant (EU console hosts use appeu.samanage.com).
  • Create payloads: Incidents, problems, and changes require a registered requester_email on create. The API wraps bodies as {incident: {...}}, {problem: {...}}, etc.
  • Comments: Use upsert_comment with object_type of incidents, problems, or changes plus the parent object_id.
  • Pagination: List endpoints use integer page and per_page (default 25, max 100). List responses are JSON arrays.
  • Hardware vs other assets vs CIs: Hardware needs serial numbers; other assets need manufacturer and asset_type; configuration items track CMDB dependencies separately.
  • Roles and categories: Exposed as read-only lists — permission and taxonomy edits stay in the admin UI.

Tools in this Server (62)

Delete Catalog Item

Permanently delete a catalog item by id.

Delete Change

Permanently delete a change record by id.

Delete Change Catalog

Permanently delete a change catalog template by id.

Delete Comment

Delete a comment from an incident, problem, or change thread by parent ids and comment_id.

Delete Configuration Item

Permanently delete a configuration item by id.

Delete Contract

Permanently delete a contract by id.

Delete Department

Permanently delete a department by id.

Delete Group

Permanently delete an assignment group by id.

Delete Hardware

Permanently delete a hardware asset by id.

Delete Incident

Permanently delete an incident by id. This cannot be undone on most tenants.

Delete Mobile

Permanently delete a mobile device asset by id.

Delete Other Asset

Permanently delete a non-hardware asset by id.

Delete Problem

Permanently delete a problem record by id.

Delete Purchase Order

Permanently delete a purchase order by id.

Delete Release

Permanently delete a release record by id.

Delete Risk

Permanently delete a risk register entry by id.

Delete Site

Permanently delete a site by id.

Delete Solution

Permanently delete a knowledge base solution by id.

Delete User

Permanently delete or deactivate a user by id depending on tenant policy.

Delete Vendor

Permanently delete a vendor by id.

Get Audits

List audit log entries across the tenant. Read-only compliance trail showing who changed which object and when. Paginate with page and per_page.

Get Catalog Items

List or fetch self-service catalog items. Omit id to browse requestable services; pass id for form fields and fulfillment metadata.

Get Categories

List ticket and asset categories (read-only taxonomy on most tenants). Omit id to list categories; pass id for subcategory trees.

Get Change Catalogs

List or fetch standard change templates. Omit id to list templates; pass id for pre-approved workflow definitions.

Get Changes

List or fetch change records. Omit id to review the change calendar backlog; pass id for CAB state, plans, and linked incidents or releases.

Get Configuration Items

List or fetch CMDB configuration items. Omit id to browse dependencies; pass id for relationships and impact context.

Get Contracts

List or fetch vendor contracts. Omit id to review renewals; pass id for terms, linked assets, and expiration dates.

Get Departments

List or fetch organizational departments. Omit id to list departments; pass id for hierarchy and linked users.

Get Groups

List or fetch assignment groups. Omit id to list routing groups; pass id for members and notification settings.

Get Hardwares

List or fetch hardware assets (laptops, servers, monitors). Omit id to inventory hardware; pass id for warranty, assignment, and location fields.

Get Incidents

List or fetch SolarWinds Service Desk incidents. Omit id to page open and closed tickets; pass id for full detail including requester, assignee, SLA, ...

Get Mobiles

List or fetch mobile device assets. Omit id to list phones and tablets; pass id for carrier, IMEI, and assignment details.

Get Other Assets

List or fetch non-hardware assets (furniture, peripherals, licenses). Omit id to list assets; pass id for assignment and custom fields.

Get Problems

List or fetch problem records (root-cause investigations). Omit id to browse the backlog; pass id for linked incidents, RCA fields, and assignment con...

Get Purchase Orders

List or fetch purchase orders. Omit id to review open POs; pass id for line items and approval state.

Get Releases

List or fetch release trains bundling changes. Omit id to list releases; pass id for deployment schedule and linked changes.

Get Risks

List or fetch risk register entries. Omit id to review open risks; pass id for impact, probability, and mitigation context.

Get Roles

List permission roles configured on the tenant. Omit id to list roles; pass id for permission metadata. Role assignment changes are not exposed on thi...

Get Sites

List or fetch physical sites/locations. Omit id to list sites; pass id for address and linked assets.

Get Solutions

List or fetch knowledge base solutions. Omit id to search published articles; pass id for full body, tags, and vote metadata.

Get Users

List or fetch Service Desk users (agents and end users). Omit id to directory-search users; pass id for role, department, and contact fields.

Get Vendors

List or fetch vendor directory entries. Omit id to list suppliers; pass id for contacts and linked contracts.

Upsert Catalog Item

Create or update a service catalog item. Omit id with name to create; pass id to update description or availability.

Upsert Change

Create or update a change record. Omit id with name, requester_email, and priority to register a change; pass id to update plans, priority, or workflo...

Upsert Change Catalog

Create or update a standard change catalog entry. Omit id with name to create; pass id to update template fields.

Upsert Comment

Add or update a comment on an incident, problem, or change. Provide object_type, object_id, and body to post a new comment; include comment_id to revi...

Upsert Configuration Item

Create or update a CMDB configuration item. Omit id with name to create; pass id to update description, type, or state.

Upsert Contract

Create or update a contract record. Omit id with name to create; pass id to update renewal dates, cost, or vendor links.

Upsert Department

Create or update a department. Omit id with name to create; pass id to update title or description.

Upsert Group

Create or update an assignment group. Omit id with name to create a group; pass id to rename or adjust membership-related fields.

Upsert Hardware

Create or update a hardware asset. Omit id with name and serial to create; pass id to update assignment, status, or descriptive fields. Upstream requi...

Upsert Incident

Create or update an incident. Omit id and supply name plus requester_email to open a ticket; pass id to change title, description, priority, or state.

Upsert Mobile

Create or update a mobile device asset. Omit id with name to create; pass id to update carrier, IMEI, or assignment fields.

Upsert Other Asset

Create or update a non-hardware asset. Omit id with name, manufacturer, and asset_type to create; pass id to update descriptive or assignment fields.

Upsert Problem

Create or update a problem record. Omit id with name and requester_email to log a new problem; pass id to update description, priority, or state.

Upsert Purchase Order

Create or update a purchase order. Omit id with name to create; pass id to update status or vendor linkage.

Upsert Release

Create or update a release record. Omit id with at least name to create; pass id to update title, description, priority, or state.

Upsert Risk

Create or update a risk register entry. Omit id with name to add a risk; pass id to update description, priority, or state.

Upsert Site

Create or update a site. Omit id with name and location to create; pass id to update address or descriptive fields.

Upsert Solution

Create or update a knowledge base article. Omit id with name and description to draft an article; pass id to publish updates or revise content.

Upsert User

Create or update a user record. Omit id with email and name to invite a user; pass id to update profile or assignment metadata.

Upsert Vendor

Create or update a vendor. Omit id with name and reseller_type_id to create; pass id to update contact or classification fields.

Frequently Asked Questions

What is the SolarWinds Service Desk MCP server?

Solarwinds Service Desk is a cloud-based IT service management platform that streamlines the process of handling IT service requests, asset management, and incident management. It is primarily used to improve IT service delivery and support operations. It provides 62 tools that AI agents can use through the Model Context Protocol (MCP).

How do I connect SolarWinds Service Desk to my AI agent?

Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/solarwinds-service-desk. Authentication is handled automatically.

How many tools does SolarWinds Service Desk provide?

SolarWinds Service Desk provides 62 tools that can be called by AI agents, along with a SKILL.md that gives your AI agent domain knowledge about when and how to use them.

What authentication does SolarWinds Service Desk require?

SolarWinds Service Desk uses API Key. SolarWinds Service Desk requires credentials. Connect via MCPBundles and authentication is handled automatically.

What can AI agents do with SolarWinds Service Desk?

Agents can list or fetch incidents, problems, changes, releases, and risks; manage hardware, mobile devices, other assets, and configuration items; look up users, groups, departments, sites, contracts, vendors, and purchase orders; search knowledge solutions; add timeline comments; and create or update records when you ask.

How do I connect SolarWinds Service Desk on MCPBundles?

In SolarWinds Service Desk, open Setup → Users & Groups → Users, choose Generate token, and paste it when you connect on MCPBundles. Pick the region that matches your tenant — United States, Europe, or Asia-Pacific.

Which SolarWinds Service Desk workflows should agents run first?

Start with read-only queue reviews: open incidents, assignment groups, and knowledge articles. Move to writes — new incidents, comments, asset updates — only after you confirm the target record in a follow-up prompt.

Who is this integration for?

Service desk leads, L1/L2 support engineers, change managers, and CMDB owners who want queue summaries, dependency context, and procurement visibility in chat instead of exporting lists from the admin UI.

Setup Instructions

Connect SolarWinds Service Desk to any MCP client in minutes

MCP URL
https://mcp.mcpbundles.com/bundle/solarwinds-service-desk

One-click install:

The link prefills the Add custom connector dialog — you still review the values and click Add, then Connect to complete OAuth.

Or add manually

  1. Open claude.ai → Settings → Connectors.
  2. Click the + button and choose Add custom connector.
  3. Set Name to SolarWinds Service Desk and paste the MCP URL into Remote MCP server URL.
  4. Click Add. SolarWinds Service Desk will appear under Not connected — select it and click Connect to complete OAuth.
Name: SolarWinds Service Desk
Remote MCP server URL: https://mcp.mcpbundles.com/bundle/solarwinds-service-desk
Authentication: OAuth

Custom connectors at claude.ai require a paid Claude plan (Pro, Max, Team, or Enterprise).

Ready to use SolarWinds Service Desk?

Sign in to connect your credentials and start running tools from the chat.

SolarWinds Service Desk MCP Server & Skill — 62 Tools