Why Choose Vikstra MCP Server?
Built for the latest MCP spec, projected for token efficiency, and locked down by signed policy packs out of the box.
≤20 default tools (sn_record, sn_aggregate, sn_attachment, sn_incident_action, sn_approval_action, sn_catalog, sn_cart, sn_order, sn_knowledge, sn_script_include, sn_import_set, …). Legacy per-CRUD names stay as aliases.
Browser-based authorisation flow against the SN instance, refresh tokens kept in an AES-GCM keychain vault. Basic auth + env-var overrides stay as the CI fallback.
sn:// URIs for stable references (dictionary, catalog item, KB, scope, policy) so the model never burns a tool call to hydrate context. Five named prompts compose the common ITSM workflows.
Shape-aware encoders pick TOON for uniform lists, Markdown-KV for single-record reads, JSON when sparse. Reference dedup table + projection floor save 30–60% tokens vs raw JSON.
Per-session deterministic-tokenisation vault. Outbound control-plane payloads ship as typed tokens (usr_*, eml_*, phn_*); plaintext stays on the developer's machine.
Signed JSON bundles fetched from the control plane with Ed25519 verification + offline grace cache. Built-in HIPAA, SOX, FedRAMP-moderate and pdi-permissive packs.
sn_script_lint flags misspelled GlideSystem methods, cross-scope GlideRecord access, hard-coded sys_ids, and client/server API mix. SDK-app mode scaffolds + validates + dry-runs deploys.
Customer-record bytes never traverse Vikstra cloud. The local binary talks directly to the SN instance; control plane only sees license, signed policy bundles, anonymous counters, and (optional) tokenised draft prompts.
vk_tool_search lets agents discover specialist tools (diff, bulk, CMDB, semantic search) on demand instead of holding the full catalogue in context up-front.
Built On the 2025-11-25 MCP Spec
Server metadata, elicitation, completions, task durability, sampling, deferred tool loading — every Tier 0/1/2 primitive wired where it makes sense.
- MCP 2025-11-25 spec: elicitation, completions, icons, tasks, sampling, scope consent
- ≤20 default tools with output schemas + per-tool icons; specialists opt in via URL path
- URL-path toolset filtering: /mcp/x/{service_desk|developer|cmdb|platform|all}[/{readonly|admin}]
- Lockdown mode hides records the caller's SN role doesn't own — blunts prompt-injection
- Per-session PII vault with typed class tokens (usr_, eml_, phn_, ssn_, cc_, iban_, cmdb_, …)
- Signed policy bundles (Ed25519) + offline grace + air-gapped customer-key mode
- OAuth 2.1 + PKCE login, AES-GCM keychain vault, secret references (op://, doppler://, infisical://)
- Semantic index (BM25 + cosine RRF) over the official ServiceNow-published markdown docs + local SDK-app indexing
- Cross-instance scope diff, dry-run bulk patch, test-record factories, CMDB graph traversal
- Token-aware output: TOON / Markdown-KV / JSON auto-select + dedup table + deterministic summary
- On-disk file cache by default (Redis when configured)
vikstra-mcp ships with subcommands for the full dev loop
30–60% Fewer Output Tokens by Default
Every tool response runs through a shape-aware encoder, a projection floor, and an optional reference-dedup table. No server-side LLM, no extra latency, no $ on every response.
TOON encoder
Tabular Token-Oriented Notation for ≥3 uniform records. Declares columns once, streams rows. ~40% smaller than JSON on list responses.
Markdown-KV singles
Single-record reads emit `key: value` lines with `|` block indicators for multiline. ~30% smaller than JSON on single-record reads.
Reference dedup
Repeated display values (assigned_to, group, CI) collapse into a refs table referenced by short @N aliases. Saves ~20% on large lists.
Deterministic summary
?mode=summary returns count + by-state/by-priority/by-group buckets + top-N labels. No model in the loop, ~85% smaller than full payload.
vikstra-mcp budget show
Per-tool byte and estimated-token tally is captured automatically. Validate the savings in your own traffic without wiring a real model.
TOOL CALLS BYTES_OUT TOKENS≈ sn_record 412 186 432 46 608 sn_aggregate 93 28 776 7 194 sn_knowledge 67 71 480 17 870
ServiceNow Integration Scenarios
From day-to-day ITSM triage to SDK-app PR reviews — Vikstra ships the tools, prompts, and governance to make AI a useful collaborator on every flow.
Pull the record, find related KB articles, look up similar resolved incidents, draft a work note. One prompt composes the chain end-to-end with PII tokenised before any control-plane call.
Key Capabilities:
- Auto-categorise via deterministic by_state grouping
- KB citations from the local + ServiceNowDocs index
- Top-N similar incidents in summary mode (≤25% tokens)
- Elicitation prompt before write — no silent updates
Diff the committed SDK app against the deployed scope on dev/uat/prod, lint every script, surface schema and coverage gaps. Deploy preview is dry-run by default.
Key Capabilities:
- sn_diff at sys_metadata level across instances
- sn_script_lint flags gs.* typos + cross-scope GlideRecord
- sn_sdk_validate + sn_sdk_deploy --dry-run baseline
- Roots integration picks up the active app from the client
Pull the change window, walk related CIs via CMDB traversal, attach relevant KB references, generate a CAB-ready summary. SOX policy pack elicits on every production write.
Key Capabilities:
- sn_cmdb_ask traversal to configurable depth
- SOX baseline: writes elicit, destructive needs sox_cab role
- Tokenised drafting on the client's sampling endpoint
- Per-tool byte budget so the pack fits the response window
Aggregations and dry-run bulk patches run with progress notifications and ctx cancellation. Long-running jobs go through the durable task surface.
Key Capabilities:
- sn_aggregate count/sum/avg/max/min/multi with output schema
- sn_bulk dry-run preview before apply (elicit-gated)
- vk_task_submit returns immediately, vk_task_get polls
- Reference dedup collapses repeat assignees/groups
Where Bytes Actually Go
Customer records stay on the developer's machine. The control plane only ever sees what is explicitly listed below.
OAuth login
PKCE flow to the SN instance, refresh token in keychain
Direct to SN
Tool calls hit the customer instance straight from the local binary
Policy eval
Signed bundles fetched from control plane, evaluated locally
Tokenised cloud calls
Optional control-plane features ship PII-tokenised; plaintext stays local
Policy Packs Ship In-Binary
Air-gapped customers can run signed bundles without ever calling the control plane. Vertical packs cover the common compliance baselines; author your own with vikstra-mcp policy new.
pdi-permissiveDeveloper-only baseline. All tools allowed for local PDIs.
hipaa-baselinePHI access requires hipaa_clinician/hipaa_admin. Writes elicit. No bulk over PII/PHI.
sox-baselineProduction writes elicit. Destructive ops need sox_cab. Immutable audit.
fedramp-moderateDeny-by-default with region pinning. FIPS-validated crypto fallback path.
Early Access to ServiceNow MCP Integration
Join the alpha program to test ServiceNow MCP Server integration and shape the roadmap for token-aware, policy-governed AI workflows.
Early Access
Join the alpha program