Helpdesk
SolarWinds Service Desk MCP connector
Connecting SolarWinds Service Desk to Elaichi lets Claude, ChatGPT, Cursor, and other AI clients read, create, and update incidents, users, groups, and categories inside each person's own permissions, with every action recorded in an audit log.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect SolarWinds Service Desk to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect SolarWinds Service Desk once
-
Open Connections, choose Add connection, and pick SolarWinds Service Desk.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a SolarWinds Service Desk API key. One person generates a token in SolarWinds Service Desk and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect SolarWinds Service Desk to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect SolarWinds Service Desk to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect SolarWinds Service Desk to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect SolarWinds Service Desk to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with SolarWinds Service Desk through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Service desk
Triage the incident queue in plain language
Ask which SolarWinds Service Desk incidents are still unassigned or have gone quiet, pull up a single incident with its details, and update the priority, category, or assignee without opening each record.
-
IT support
Log an incident straight from a conversation
When someone reports a broken laptop or a locked account over chat, create the SolarWinds Service Desk incident on the spot with the right requester, category, and description.
-
IT support
Catch the incident up after the fix
Once the work is done, update the SolarWinds Service Desk incident with what changed and its new state, and pull the related task to confirm nothing is left open.
-
IT operations
Pull attachments and tasks for a review
Download the screenshots and log files attached to an incident and check the linked task so an engineer has the whole picture before a handover or a post-incident review.
-
HR
Set up and retire service desk users
Create a SolarWinds Service Desk user for a new hire, place them in the right group and role, and update or remove the record when they change teams or leave.
-
IT management
Keep categories and groups tidy
List every category and group in SolarWinds Service Desk, spot duplicates or stale entries, and rename, merge, or remove them so incidents land in the right place.
Try asking
- “Which groups have no active users assigned right now?”
- “List categories used by the service desk team.”
- “Show users added to the IT operations group this month.”
AI tools
SolarWinds Service Desk tools for your AI agents
27 tools are ready to call through Elaichi's MCP endpoint the moment you connect SolarWinds Service Desk, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting SolarWinds Service Desk gets you
6 screens from the product, each doing one job for your SolarWinds Service Desk account.
The agent
Ask about users and groups, get answers.
Plain language questions answered from live SolarWinds Service Desk users, groups and categories.
- users
- roles
- groups
- categories
Ask Elaichi to work across your apps.
Which groups have no active users assigned right now?
List categories used by the service desk team.
Show users added to the IT operations group this month.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Reach SolarWinds Service Desk from any MCP client over OAuth, no SDK, no shared key.
Copy the endpoint
Tool catalog
27 SolarWinds Service Desk tools, ready now.
Users, roles, groups and categories with list, create, update and delete methods.
- List all SolarWinds Service Desk users
- Get single SolarWinds Service Desk user by ID
- Delete a SolarWinds Service Desk user by ID
- Update a SolarWinds Service Desk user by ID
Toolboxes
Every team gets its own toolbox.
Scope SolarWinds Service Desk toolboxes so service desk, IT ops and HR see different tools.
- Service desk
- IT operations
- HR
- Security
Shared connections
Teammates work without seeing a credential.
One person connects SolarWinds Service Desk, then shares that connection with teams and members.
- Service desk
- IT operations EMEA
- HR onboarding
- Security review
Audit log
Answer who changed which group, exactly.
Every SolarWinds Service Desk call is logged with time, actor, action, type and resource.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a digest gets posted.
Six steps fetch and group tickets, draft a digest, await approval, post back.
SolarWinds Service Desk digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch users
SolarWinds Service Desk
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
SolarWinds Service Desk
Queued
Collections and dashboards
Service desk health, counted on a schedule.
Four metrics, 14 days of records created and a team breakdown, no model involved.
SolarWinds Service Desk health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Roles
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
Service desk 34%
IT operations EMEA 27%
HR onboarding 21%
Security review 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect SolarWinds Service Desk to Claude?
First, connect SolarWinds Service Desk in Elaichi: paste in the API key from your SolarWinds Service Desk account, and Elaichi confirms the connection. There is no OAuth application to register and no client ID or secret to generate. Then, in Claude, open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and SolarWinds Service Desk incidents, users, and groups are available in Claude.
Does SolarWinds Service Desk work with ChatGPT and Cursor as well as Claude?
Yes. Once SolarWinds Service Desk is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect SolarWinds Service Desk once and every client uses it.
What can an AI agent actually do with my SolarWinds Service Desk data?
An agent connected to SolarWinds Service Desk can list and read incidents, create new ones, update their state, priority, or assignee, and remove them if you allow it. It can look up users, roles, groups, and categories, create or change users, groups, and categories, download the files attached to an incident, and pull up a task by its reference. In practice that means asking for the open incidents in a category, logging a report from a chat, or bringing a ticket up to date after a call.
Does connecting SolarWinds Service Desk give the AI access to every incident and user?
No. Each person signs into Elaichi as themselves, so an agent working in SolarWinds Service Desk sees only the incidents, users, and groups that person's own SolarWinds Service Desk role already allows. Elaichi can narrow that further, for example to reading only, but it can never widen access beyond what the person already has.
Can I stop an agent from deleting or changing things in SolarWinds Service Desk?
Yes. Restrictions in Elaichi work per action, so you can allow reading and creating SolarWinds Service Desk incidents while blocking deletion of incidents, users, groups, or categories. A blocked action is never advertised to Claude, ChatGPT, or any other client, so no prompt, however worded, can reach it.
What happens to a SolarWinds Service Desk connection when someone leaves?
Offboarding a person in Elaichi ends their access to SolarWinds Service Desk through every AI client at once. A shared SolarWinds Service Desk connection keeps working for everyone else on the team. If you disconnect SolarWinds Service Desk in Elaichi, it disappears from Claude, ChatGPT, Cursor, and every other client in one step.
Put SolarWinds Service Desk in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.