The Siit MCP is here: run your service desk from your AI client

Today, your entire service desk becomes something your AI tools can run. The Siit MCP server is live.

Connect Siit to Claude, Codex, or any other MCP-compatible client, then describe what you want in plain language and let your assistant do it, working directly on your live data across requests, people, your CMDB, your service catalog, and your knowledge base. It reads, and it acts, always within your own Siit permissions.

Want to see it in action? The Prompt Your Service Desk series is on YouTube.

TL;DR

• The Siit MCP server is live: connect Siit to your AI tools and run your service desk in plain language.
• Read and write across requests, people, your CMDB, service catalog, and knowledge base, not a read-only view.
• Set up in a few minutes with OAuth, no API keys to manage.
• Every action is scoped to your own Siit permissions, so the agent never does more than you can.
• Available on all plans. Works with Claude, Cursor, Copilot, Mistral, and any MCP-compatible client.

Connect in a few minutes

Add a custom connector pointing to https://mcp.siit.io/mcp and authorize with your Siit account. The exact steps vary by client. Full per-client instructions and the complete tool list are in the setup guide and the docs.

Prompts to run in your first session

Everything below is already sitting in your Siit account. The MCP lets you run all of it by asking. Each prompt is yours to copy, tweak, and build on in the same conversation.

1. See what your employees are asking for

Pulling a trend report usually means filtering views and exporting to a sheet. Ask instead.

The prompt: Which services were requested the most last week? Group them and show the volume for each.

What you get: A ranked breakdown of demand, ready to drop into a planning doc.

2. Respond to an outage across every affected request

When an app goes down, you normally scramble to find each open request and update them one by one.

The prompt: Find all open Figma requests, send each requester a message that the app is down and will be restored shortly, and tag them as incident.

What you get: every affected employee notified and every request tagged, in one move.‍

3. Hand off your queue without writing a brief

End of shift usually means manually summarizing where each request stands so the next person can pick up.

The prompt: For every open request, read the conversation and add an internal note summarizing the situation for the rest of the team.

What you get: Your whole queue summarized for whoever takes over next.

4. Turn a solved ticket into a help article

The fix lives inside one request, and the next employee asks the same question anyway.

The prompt: Review the request about the Network VPN service, create an article to help employees with VPN issues, and once it is ready, publish it.

What you get: A published knowledge base article that deflects the next wave of the same question.

5. Import your device inventory and match owners

A new batch of laptops normally means manual data entry and owner matching.

The prompt: Import this new computer inventory into Siit and match each device to the right owner.

What you get: Your CMDB updated and owners assigned, with no manual entry.

The full tool surface

Beyond the actions above, the MCP spans your whole service desk: requests, people, your catalog of apps and equipment, your service catalog, and your knowledge base, with read and write on each. The complete and always-current tool list is in the docs.

Security

Unchanged. Every action runs on behalf of the authenticated user and stays scoped to exactly what you can see and do in the Siit dashboard, nothing more. Authenticated, scoped, and auditable by design.

Where to start

Not sure where to begin? Try prompt 1 (see what your employees need) or prompt 5 (import your inventory). Both deliver a result in seconds and work whatever your setup looks like.

Connect the MCP from the setup guide, and watch the full series on Youtube. Available on all plans.