MCP Server: ServiceNow (DIY Wrapper Approach)

What This Repository Does

Status: Community / experimental. A native ServiceNow MCP server is not yet widely available. This article describes a DIY wrapper approach using the ServiceNow REST API directly.

This article describes how to connect build-cli to ServiceNow by building a minimal custom MCP wrapper around the ServiceNow REST API (linked in source_url). It is not a reference to an existing published MCP server repo — it is guidance for teams who want to build one.

Common use cases once a wrapper is in place:

Look up an incident or change request while working on the related code or configuration
Draft a ticket body in build-cli and submit it without switching context
Cross-reference a problem record while investigating a data quality issue

For the recommended interim workflow, see the ServiceNow Incident Description prompt article, which describes drafting ticket content in build-cli or Gemini and submitting it manually.

How to Use It

If you want to build a minimal custom MCP wrapper for ServiceNow, the REST API endpoints you need are straightforward:

GET /api/now/table/incident/{sys_id} — look up a ticket
POST /api/now/table/incident — create a ticket

Store your ServiceNow API credentials (OAuth token or basic auth) in environment variables, never in the MCP config file.

A minimal wrapper would follow the same npx-invocable pattern as the official MCP servers:

{
  "mcpServers": {
    "servicenow": {
      "command": "node",
      "args": ["/path/to/your/servicenow-mcp-wrapper.js"],
      "env": {
        "SN_INSTANCE": "your-instance.service-now.com",
        "SN_TOKEN": "your-oauth-token"
      }
    }
  }
}

If you build a working wrapper, please contribute the configuration to this hub following the InnerSource contribution guidelines.

Security considerations:

Use environment variables for credentials — never embed OAuth tokens or passwords in the config file.
Scope your API credentials to the minimum required operations.
Review the ServiceNow REST API documentation (linked in source_url) for authentication and rate-limiting details.

Relevance to the Hub

ServiceNow is the primary ITSM platform for DMDQP incident, change, and problem management. Integrating it with build-cli would reduce context-switching during investigation and change management workflows. The article also documents the recommended interim approach (using the ServiceNow Incident Description prompt) while a native MCP server is awaited.

Open question for Plan-04 editorial gate: Because no canonical ServiceNow MCP server repository exists, the human reviewer may decide this item is more accurately classified as content_type: article rather than repo. If so, the id would change to article:mcp-servicenow and the source_url field would no longer be required by the schema. This decision is deferred to the Plan-04 human review.