ServiceNow MCP Server

What the code does

We read the source, 19 h ago · rules 3dff92dd89df

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

          fs.writeFileSync(outFd, pdfBuffer);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mcp-server-servicenow -- npx -y @mindstone/mcp-server-servicenow

{
  "mcpServers": {
    "mcp-server-servicenow": {
      "args": [
        "-y",
        "@mindstone/mcp-server-servicenow"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.mcp-server-servicenow]
command = "npx"
args = ["-y", "@mindstone/mcp-server-servicenow"]

{
  "mcpServers": {
    "mcp-server-servicenow": {
      "args": [
        "-y",
        "@mindstone/mcp-server-servicenow"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "mcp-server-servicenow": {
      "args": [
        "-y",
        "@mindstone/mcp-server-servicenow"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: SERVICENOW_INSTANCE (ServiceNow instance name (e.g. acme for acme.service-now.com)), SERVICENOW_USERNAME (ServiceNow username), SERVICENOW_PASSWORD (ServiceNow password), SERVICENOW_CLIENT_ID (OAuth 2.0 client ID (optional; alternative to username/password when the instance enforces MFA/SSO — requires an OAuth application registry entry with the client credentials grant enabled)), SERVICENOW_CLIENT_SECRET (OAuth 2.0 client secret (optional; used with SERVICENOW_CLIENT_ID instead of username/password)). The author declared them in the registry entry; get the values from the project itself.