using-snow

Guides ServiceNow operations via snow-mcp tools including queries, attachments, and error handling.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/dlaporte/claude-plugins --skill using-snow-dlaporte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-snow
Source: https://github.com/dlaporte/claude-plugins/tree/main/plugins/servicenow/skills/using-snow
Command: npx skills add https://github.com/dlaporte/claude-plugins --skill using-snow-dlaporte

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Working in ServiceNow through MCP tools requires knowing the deployment's capabilities, encoded-query syntax, and how to recover from common errors; this Skill establishes that foundation before the first tool call so sessions don't fail on missing packages, read-only modes, or malformed queries. ## Core Features & Use Cases - Capability Probing: Detects read-only mode and installed tool packages via connection_info, with fallbacks to generic table tools when packages are absent. - Encoded-Query Guidance: Teaches ServiceNow encoded-query syntax (operators, dot-walking, relative-date helpers, full-text search) for query_records calls. - Attachments & Error Playbook: Covers listing, downloading, and uploading record attachments, plus a symptom-to-fix table for 401s, ACL-denied 403s, missing scoped APIs, and sys_id resolution. - Use Case: A user asks to list their team's open P1 incidents; the Skill first checks the deployment mode, then builds priority=1^active=true^assignment_group.nameLIKEservice desk and resolves any errors using the playbook. ## Quick Start Ask the assistant to show your open incidents in ServiceNow and it will load this Skill to probe the connection and run the right query.

Frequently Asked Questions about using-snow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I query ServiceNow records with encoded queries?

Use query_records with ServiceNow encoded-query syntax: clauses joined by ^, no spaces around operators, ^OR for disjunction, and ORDERBYDESC for sorting. Dot-walk reference fields like caller_id.department and use 123TEXTQUERY321 for full-text search.

How do I check if a ServiceNow MCP deployment is read-only?

Call connection_info at session start and inspect the read_only and tool_packages fields. If read_only is true, write tools are not registered, so only queries, reports, and lookups should be offered.

What happens when a ServiceNow tool package is missing?

Basic reads still work through generic table tools, such as query_records on change_request, sc_cat_item, or kb_knowledge. Change state logic, conflict checking, and catalog ordering with variables cannot be emulated without their packages.

Why does ServiceNow return a 403 or empty results via MCP?

A 403 or suspiciously empty result set reflects the authenticated user's own ACLs, identical to what they would see in the ServiceNow UI. It is not a server bug; the user's permissions determine visibility.

How do I resolve a record number like INC0010001 to a sys_id?

Run query_records on the table with query="number=INC0010001" and limit=1 to fetch the record and its sys_id. Passing a record number directly where a sys_id is expected causes an invalid sys_id error.

Can ServiceNow MCP tools run background scripts or UI actions?

No. The REST-based tools cannot run background scripts or UI-action buttons; set the underlying fields directly instead. Server-side business rules and validation still execute, but client scripts and UI policies do not.