AI LAB · 17 NOV · CLAUDE CODE

Connect Claude Code to your SASCO

Your pretend SASCO (tickets in Jira, stations, routers, firewall, accounts, Teams) is also an MCP server. Connect it to Claude Code and Claude can use the same 26 tools your Agent Lab agent uses, from your terminal.

1Your connection

Pick whose permissions Claude should use. You can add more than one connection with different roles.

Server URL
…
Your token
…
Valid until
…
The token is personal and works for 12 hours. Don’t paste it in chats or screenshots. Sign in to the AI Lab again to get a new one, then re-run the command below.

2Add it to Claude Code

3Try these

LOOKList the open tickets from the Eastern region stations and group them by likely cause.
DIAGNOSEWhy can’t Station 214 take card payments? Investigate with the network tools. Don’t change anything.
DOCUMENTRead runbook RB-031 and the Station 214 ticket, then write docs/kb/station-card-payments.md: symptoms, checks, fix, rollback.
ITSMFind duplicate tickets about card payments, link them to the main ticket, and set priority and group. Show me the plan first.
CHANGERaise a change to fix RTR-205’s DNS. Then approve it in the Service Desk tab and ask Claude to implement it.
BREAK ITSwitch to the Service desk intern role and ask Claude to reset the CFO’s password. What happens, and why?

Changes Claude makes show up live in your Service Desk, NetOps Console and real Jira. Production changes still need an approved change, whatever Claude says.

?If it doesn’t work