SolarWinds Service Desk MCP connector
Connecting SolarWinds Service Desk to Elaichi lets Claude, ChatGPT, Cursor, Microsoft Copilot, 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.
- Connects with an API key
- Free 14-day trial
- No credit card
ChatGPT
Elaichi connected
Which groups have no active users assigned right now?
Working in SolarWinds Service Desk with Elaichi
-
List all SolarWinds Service Desk users
-
-
Governance
/
Audit log
Last 24 hours
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
Claude · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect SolarWinds Service Desk to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
SolarWinds Service Desk MCP connector for 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.
SolarWinds Service Desk MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
SolarWinds Service Desk MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
SolarWinds Service Desk MCP connector for 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.
SolarWinds Service Desk MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with SolarWinds Service Desk through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in SolarWinds Service Desk is logged.
-
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.”
What connecting SolarWinds Service Desk gets you
6 screens from Elaichi, each doing one job for your SolarWinds Service Desk account.
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, Cursor or Microsoft Copilot
The agent
Ask about users and groups, get answers.
Plain language questions answered from live SolarWinds Service Desk users, groups and categories.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot share one endpoint.
Reach SolarWinds Service Desk from any MCP client over OAuth, no SDK, no shared key.
ElaichiToolsTool catalog
27 SolarWinds Service Desk tools, ready now.
Users, roles, groups and categories with list, create, update and delete methods.
ElaichiToolboxesToolboxes
Every team gets its own toolbox.
Scope SolarWinds Service Desk toolboxes so service desk, IT ops and HR see different tools.
ElaichiConnectionsShared connections
Teammates work without seeing a credential.
One person connects SolarWinds Service Desk, then shares that connection with teams and members.
ElaichiAudit logAudit log
Answer who changed which group, exactly.
Every SolarWinds Service Desk call is logged with time, actor, action, type and resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
SolarWinds Service Desk digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
SolarWinds Service Desk
Queued
Automations
A schedule fires, a digest gets posted.
Six steps fetch and group tickets, draft a digest, await approval, post back.
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%
Collections and dashboards
Service desk health, counted on a schedule.
Four metrics, 14 days of records created and a team breakdown, no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for SolarWinds Service Desk
All three can connect SolarWinds Service Desk to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over SolarWinds Service Desk tools | Allow or restrict single SolarWinds Service Desk tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per SolarWinds Service Desk call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting deletion of incidents, users, groups, or categories. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot, and every other client in one step.
Does the SolarWinds Service Desk MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. SolarWinds Service Desk is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for SolarWinds Service Desk?
Yes. Both let Claude, ChatGPT or Cursor use SolarWinds Service Desk. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every SolarWinds Service Desk call.
How is Elaichi different from Composio for SolarWinds Service Desk?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to SolarWinds Service Desk: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put SolarWinds Service Desk in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
- ChatGPT
- Claude
- Cursor
- Microsoft Copilot