Disconnect ServiceNow from Your AI on Mac

The disconnect_servicenow tool lets your AI assistant sign out of ServiceNow and remove the credentials LMCP stored locally on your Mac. When you ran the connect step earlier, your ServiceNow instance URL and token were saved in the local LMCP keychain so the AI could read incidents, query the CMDB, or update tickets. This tool reverses that: it severs the link and deletes the stored secret so nothing can call ServiceNow on your behalf again until you reconnect.

A natural prompt looks like this: "Disconnect my ServiceNow account and delete the saved credentials." Your AI calls disconnect_servicenow, the token is wiped from the Mac, and you get a confirmation. It's the clean way to rotate access, hand a machine to someone else, or revoke a connection you no longer use.

LMCP is a free, native macOS MCP server that gives AI assistants access to your real Mac apps and accounts locally — no API keys to paste into a website, no cloud middleman, and over 150+ tools across mail, calendar, files and connected services. Download LMCP to get started.

Which AI agents work?

LMCP exposes disconnect_servicenow to every major MCP-capable assistant:

• Desktop clients — Claude Desktop, Cursor, VS Code (GitHub Copilot), Windsurf and Zed auto-configure through a local stdio connection. LMCP wires itself in and the tool appears automatically.
• Web AIs — ChatGPT, Claude.ai (web), Grok and Perplexity connect through the LMCP Cloud Relay connector, which bridges the web assistant to the server running on your Mac.

Whichever you use, the credentials never leave your machine — the relay only forwards the request to your local server.

Automation

This tool is the bookend of a credential lifecycle. It chains naturally with the rest of your ServiceNow workflow: connect, work, then disconnect. You can tell your AI "Finish updating ticket INC0012345, then disconnect ServiceNow" and it will complete the task before tearing down access. It also pairs with offboarding routines — "close my open incidents, export a summary to a note, and disconnect ServiceNow" runs as a single instruction. Because LMCP shares one context across tools, the AI knows what it just did before it revokes the session.

Context

Your AI works against your real ServiceNow instance and your real Mac data, not a sandbox. When it disconnects, it's removing the actual credential that authorized those reads and writes — so the action is precise and verifiable. The assistant already knows which instance is connected, so you don't need to specify URLs or IDs; a plain "disconnect ServiceNow" is enough.

Productivity

Manually revoking an OAuth token or clearing a stored secret usually means digging through ServiceNow admin settings or your Mac keychain. With LMCP it's one sentence to your AI and it's done in seconds. That matters most when you're rotating credentials on a schedule, switching between instances, or wiping a connection before handing off a laptop — tasks you'd otherwise put off because they're fiddly.

Privacy & GDPR

Everything runs locally on your Mac. Your ServiceNow token was stored on the device, and disconnect_servicenow deletes it from the device — there's no server-side copy to clean up because LMCP never sent it to a cloud. Disconnecting genuinely removes the data, which is exactly the kind of local-first, no-retention design that makes LMCP GDPR-compliant by architecture. No API keys live on a third-party server, and nothing about your ServiceNow instance is logged off-device.