Skip to main content
Glama
matheuscalma

servicenow-mcp

by matheuscalma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SNOW_PASSWORDYesThe password for ServiceNow basic authentication
SNOW_USERNAMEYesThe username for ServiceNow basic authentication
SNOW_INSTANCE_URLYesThe URL of your ServiceNow instance (e.g. https://devXXXXXX.service-now.com)
SNOW_TIMEOUT_SECONDSNoThe timeout in seconds for HTTP requests to the ServiceNow instance15

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_incidentA

Create a new ServiceNow incident and return its number and sys_id.

Use this when a user reports a problem that should be tracked as a ticket.

Args:
    short_description: One-line summary of the issue (required, shown in lists).
    description: Longer free-text details, steps to reproduce, impact, etc.
    urgency: "1" (High), "2" (Medium) or "3" (Low). Defaults to "3".

Returns:
    {"number": "INC0010001", "sys_id": "...", "short_description": ..., "state": ..., "urgency": ...}
    The `number` is what humans reference; `sys_id` is the stable record id.
query_incidentsA

List ServiceNow incidents, newest first, optionally filtered by text and/or state.

Use this to find existing tickets before creating a new one, to check on a
ticket by number, or to answer "what incidents are open about X?".

Args:
    query_text: What to search for. An incident number ("INC0010001") matches
        exactly; anything else runs ServiceNow's keyword search over the
        incident's text fields, falling back to a substring match on
        short_description/description. Leave empty to list the most recent incidents.
    state: Filter by state. Accepts a numeric code ("1".."8") or a name such as
        "New", "In Progress", "On Hold", "Resolved", "Closed", "Canceled".
        Leave empty for any state.
    limit: Maximum number of incidents to return (1-100). Defaults to 5.

Returns:
    A list of {"number", "sys_id", "short_description", "state", "state_code",
    "urgency", "created_on"}; an empty list means nothing matched.
update_incidentA

Update an existing incident by number: append a work note and/or change its state.

Use this to record progress on a ticket or move it through its lifecycle.
At least one of `work_notes` or `state` must be provided.

Args:
    number: The incident number, e.g. "INC0010001".
    work_notes: Text to append to the (internal) work notes journal.
    state: New state as a numeric code ("1".."8") or a name such as "In Progress",
        "On Hold", "Resolved", "Closed". Note: resolving/closing on most instances
        also requires resolution fields and will be rejected by ServiceNow if missing.

Returns:
    {"number", "sys_id", "changed": {field: new value, ...}, "state": <current state>}
    describing exactly what was applied.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a distinct operation: create, query (list/search), and update. There is no overlap in purpose; an agent can clearly differentiate when to use each.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern using snake_case (create_incident, query_incidents, update_incident), with plural nouns for collection queries and singular for single-item operations, which is predictable.

Tool Count4/5

With 3 tools, the set is minimal but covers the core incident lifecycle (create, read/search, update). It is slightly thin—missing a dedicated get_incident or delete_incident—but still well-scoped for a focused incident-only server.

Completeness3/5

The tools cover create, list/search, and update, but lack an explicit 'get by ID' tool (though query_incidents can filter by number) and a delete/close operation. The update tool warns about missing resolution fields for closing, indicating gaps in full lifecycle support.

Maintenance

ActivityMaintained
ResponsivenessSyncing

Resources