Run Risotto from Claude, or from your own code
Connect Claude to search tickets, draft runbooks and check the audit log, or wire Risotto into your systems with the API and webhooks.
RisottoGet ticketIT-482RunningDone
RisottoGet ticket agent activityIT-482RunningDone
The agent matched the request to your Figma access runbook, since Jordan Lee asked for an Editor seat.
That runbook needs manager approval, and Morgan Blake declined it at 10:14 AM.
Risotto told Jordan in Slack, then closed the ticket without granting access.
Ask Claude about your service desk
Claude reads the same Risotto tickets, runbooks, knowledge and audit log your team works from, and answers in plain English.
- “Which open tickets mention the VPN this week?”
- “Why did the agent close IT-482 without an answer?”
- “What changed in our runbooks since Monday?”
Claude answers the second one from the ticket’s own record: the runbook the agent chose and why, each tool it ran, and every message. The Assistant in the dashboard works with the same tools.
Ask for a draft. Approve it in Risotto.
Admins and managers can ask Claude to draft a change to a Risotto runbook, and it arrives with tracked changes. The live runbook stays as it is until someone approves the draft in the dashboard.
Claude can also set up access rules, forms and departments, and write, test and publish script tools.
Each person’s Claude works inside their role
Every member of your Risotto org can connect Claude with their own sign-in. Admins and managers can change setup. Members can read and update tickets, search knowledge and look up people. Department supervisors can also run their department’s tools. When someone’s role changes, their Claude connection follows it.
Connect Risotto to the systems you already run
Risotto also has a public API with scoped keys, signed webhooks for ticket and access events, inbound webhooks that start automations, and an audit-events API for your SIEM. The code, the events and the scopes are on the developers page.
Bring your own MCP servers
Connect any MCP server to Risotto, and its tools join your runbooks, automations and script tools. You pick which tools to import. Each one waits for approval until you turn that off. When the server’s tool list changes, it’s marked “Needs review” for you to accept.
Frequently asked questions
Does Risotto have an MCP server?
Yes. Risotto’s MCP server works with Claude, Cursor and other MCP clients that sign in with OAuth. Each person gets the tools their role allows. Security and trust
How do I connect Claude to Risotto?
Copy the server URL from Settings → Developers → Risotto MCP server, paste it into Claude, and sign in to Risotto to approve the connection. Admins see each connected client on the same page and can revoke it.
Does Risotto have a public API and webhooks?
Yes. Risotto’s public API covers tickets, comments, departments, runbooks and audit events. Signed outbound webhooks report ticket and access events to your systems, and inbound webhooks start automations. Risotto for developers
Can Risotto use tools from our other MCP servers?
Yes. Connect the server in Risotto’s integration settings, choose the tools to import, and use them in runbooks, automations and script tools. Integrations