3,400+ servers built on vurb.ts
Vinkius

Bring Itsm
to Cursor

Learn how to connect ServiceNow to Cursor and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Count RecordsCreate RecordDelete RecordGet RecordList Change RequestsList IncidentsQuery CmdbQuery TableSearch KnowledgeUpdate Record
ServiceNow

What is the ServiceNow MCP Server?

Connect your ServiceNow instance to any AI agent and manage your entire IT service lifecycle through natural conversation.

What you can do

  • Incident Management — Create, update, and resolve incidents. Query open tickets by priority, assignment group, or SLA breach status
  • Service Requests — Submit and track service catalog requests, view approval chains, and check fulfillment status
  • Change Management — Create change requests, review CAB approvals, and monitor scheduled change windows
  • CMDB Queries — Search configuration items, explore CI relationships, and audit asset records across your infrastructure
  • Knowledge Base — Search and retrieve knowledge articles to help with incident resolution and self-service
  • User Management — Look up user profiles, group memberships, and role assignments across your organization
  • Custom Table Queries — Execute SysParm-filtered queries against any ServiceNow table with full dot-walking support

How it works

1. Subscribe to this server
2. Enter your ServiceNow instance URL and credentials
3. Start managing IT operations through Claude, Cursor, or any MCP-compatible client

Your AI agent becomes your ITSM command center — no more navigating complex Fiori dashboards to triage a P1.

Who is this for?

  • IT Service Managers — triage incidents and track SLA compliance through simple chat commands
  • DevOps Engineers — create change requests and query CMDB relationships without manual data entry
  • Help Desk Analysts — resolve tickets faster by searching the knowledge base and updating records via conversation
  • IT Directors — get real-time dashboards on incident volume, resolution times, and backlog health

Built-in capabilities (10)

count_records

Useful for dashboards and metrics without fetching full records. Get record count from a ServiceNow table

create_record

Provide fields as JSON string. Common tables: incident, change_request, sc_request, problem. Create a new record in any ServiceNow table

delete_record

This action is irreversible. Delete a ServiceNow record

get_record

Returns all fields. Get a single ServiceNow record by sys_id

list_change_requests

Filter by state, risk, type. Example: risk=high^state=new List change requests

list_incidents

Filter by priority, state, assignment_group, or any field. Example query: priority=1^state=1 (open P1 incidents). List incidents with optional filters

query_cmdb

Common tables: cmdb_ci_server, cmdb_ci_appl, cmdb_ci_db_instance, cmdb_ci_network. Example query: name=PROD-WEB-01 Query ServiceNow CMDB configuration items

query_table

). Use SysParm encoded query syntax: field=value^field2=value2. Supports dot-walking for related fields. Query any ServiceNow table with SysParm filters

search_knowledge

Returns matching articles with KB numbers and descriptions. Search the ServiceNow Knowledge Base

update_record

Only specify the fields you want to change. Update an existing ServiceNow record

Why Cursor?

Cursor's Agent mode turns ServiceNow into an in-editor superpower. Ask Cursor to generate code using live data from ServiceNow and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

  • Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

  • Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

  • MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

  • VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

See it in action

ServiceNow in Cursor

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

ServiceNow and 3,400+ other MCP servers. One platform. One governance layer.

Teams that connect ServiceNow to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

3,400+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself3,400+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for ServiceNow in Cursor

The ServiceNow MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

ServiceNow
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures ServiceNow for Cursor

Every tool call from Cursor to the ServiceNow MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I query incidents filtered by priority and assignment group?

Yes. Use the query_table tool with the incident table and SysParm query filters like priority=1^assignment_group=Network. Full dot-walking is supported for related fields.

02

How do I create a change request through the agent?

Use the create_record tool with the change_request table. Provide key fields like short_description, category, risk, and assignment_group. The agent returns the CHG number immediately.

03

Can the agent search the knowledge base for solutions?

Absolutely. The search_knowledge tool searches across all published knowledge articles using keyword or category filters, returning relevant articles with their KB numbers and resolution steps.

04

Does it support custom tables beyond the standard ITSM modules?

Yes. The query_table tool works with any ServiceNow table — standard or custom (u_ prefixed). Pass the table name and your SysParm filters, and the agent handles pagination and field expansion automatically.

05

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

06

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

07

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

08

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

09

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

10

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.