Can I look up an incident by number or do I need the sys_id?

Both work. You can give the AI the human-readable incident number like INC0010234, or the internal sys_id. The servicenow_get_incident tool accepts either and returns the full record.

Does LMCP store my ServiceNow data anywhere?

No. LMCP runs entirely on your Mac and connects to ServiceNow directly from your machine. Incident details are never copied to or stored on any LMCP cloud server.

Which AI assistants can use this tool?

Claude Desktop, Cursor, VS Code, Windsurf, and Zed auto-configure via local stdio. ChatGPT, Claude.ai, Grok, and Perplexity connect through the LMCP Cloud Relay connector.

AI ServiceNow Get Incident Details on Mac

The servicenow_get_incident tool lets your AI assistant fetch the full details of a specific ServiceNow incident by its number (like INC0010234) or its sys_id. Instead of opening the ServiceNow portal, hunting through the incident list, and clicking into a record, you just ask your AI in plain language and it returns the priority, state, assignee, short description, work notes, caller, and timestamps.

A concrete example prompt you can type: "Pull up ServiceNow incident INC0010234 and tell me its current state, priority, and who it's assigned to." The AI calls servicenow_get_incident, reads the record, and summarizes it for you in seconds.

LMCP is a free, native macOS MCP server with 150+ tools. It runs entirely on your Mac and connects your AI assistant to the real apps and services you already use — no API keys to juggle in a chat window, no cloud middleman storing your data. Download LMCP to get started.

Which AI agents work?

LMCP works with every major AI assistant. Desktop clients auto-configure through a local stdio connection, while web-based AIs connect through the LMCP Cloud Relay connector.

Desktop (auto-configured, local stdio): Claude Desktop, Cursor, VS Code (GitHub Copilot), Windsurf, and Zed.
Web (via LMCP Cloud Relay): ChatGPT, Claude.ai, Grok, and Perplexity.

You install once, and any of these agents can call servicenow_get_incident the moment you ask.

Automation

This tool shines when chained with others. Ask your AI to "get incident INC0010234, then draft an email to the assignee summarizing the issue and current status." The AI pulls the incident with servicenow_get_incident, then hands the details to your Mail tool to compose the message. You can also chain it into Reminders ("create a reminder to follow up on this incident tomorrow"), Notes, or Calendar to block time for a fix. The incident becomes the trigger for a whole workflow, all driven by one conversation.

Context

Because LMCP runs on your Mac, the AI works with your real, live data. The incident it reads is the actual current record from your ServiceNow instance, not a stale copy or a guess. When you ask a follow-up like "is this the same caller as the other ticket I looked at?", the AI has true context from the source system. That accuracy is what makes the answers trustworthy enough to act on.

Productivity

Manually opening ServiceNow, searching for an incident, and parsing the form takes a minute or two each time — and far longer when you're triaging a dozen tickets. With servicenow_get_incident, you get a clean summary in seconds without leaving your AI chat. For support engineers, IT ops, and managers doing standups or incident reviews, that adds up to real time saved every day. You stay in one window and let the AI do the lookups and the summarizing.

Privacy & GDPR

Everything runs locally on your Mac. The connection to your ServiceNow instance happens from your machine, and incident data is never copied to or stored on an LMCP server. There's no third-party cloud sitting between you and your data. This local-first design makes LMCP GDPR-compliant by architecture — your sensitive incident records stay under your control, on your hardware.