Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Ivanti MCP Load incident INC0012345 and add a note about the user's call."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Production FastMCP server for Ivanti Neurons ITSM. Tools call Ivanti's OData REST API. MCP is only the contract between a client (IDE, gateway, or agent) and this process.
Auth follows the same split used by Azure MCP and Atlassian Rovo:
Inbound — the MCP client authenticates to this server (HTTP only).
Outbound — this server authenticates to Ivanti with a tenant API key.
STDIO is for a local subprocess. HTTP is fail-closed: it will not start without MCP_JWKS_URI or MCP_JWT_SECRET.
Author: Clinton Follette.
Tool | Access | Notes |
| read | Loads the incident by |
| write | Creates a journal ( |
| write, destructive | Reads |
Structured output is typed. Tool annotations set readOnlyHint / destructiveHint / idempotentHint so clients can skip confirmations on reads.
Related MCP server: ServiceNow-MCP
Cursor / Claude Desktop / VS Code:
{
"mcpServers": {
"ivanti": {
"command": "mcp-ivanti",
"env": {
"IVANTI_BASE_URL": "https://your-tenant.ivanti.com",
"IVANTI_API_KEY": "<rest-api-key>"
}
}
}
}pip install .
mcp-ivantiexport MCP_TRANSPORT=http
export MCP_HOST=127.0.0.1
export MCP_PORT=8001
export MCP_JWKS_URI=https://login.example.com/.well-known/jwks.json
export MCP_JWT_ISSUER=https://login.example.com
export MCP_JWT_AUDIENCE=mcp-ivanti
mcp-ivantiEndpoint: http://127.0.0.1:8001/mcp. Health: GET /health.
Internal machine-to-machine can use an HMAC JWT (MCP_JWT_SECRET, HS256) instead of JWKS. Do not put this process on the public internet without TLS in front of it.
Variable | Required | Purpose |
| yes | Tenant origin |
| yes | REST key. Sent as |
| no | Default |
| no |
|
| if quick action | Quick Action id |
| no | Default |
| no | Hide write tools |
Tokens never go in git. Copy .env.example to .env.
HTTP without inbound JWT configuration refuses to boot.
mask_error_details is on. Vendor 401s do not echo keys.
RecId values are rejected if they contain path characters.
Prefer binding HTTP to loopback or an internal hostname; set MCP_ALLOWED_HOSTS to enable Host/Origin protection.
See SECURITY.md.
MIT. Copyright (c) 2026 Clinton Follette.
Create a journal note on an incident. Writes Notes, Summary, and ParentLink_RecID on the journal business object.
Inputs: notes (required), rec_id (required), summary. Returns: linked, rec_id, journal_id
Load a full Ivanti incident by RecId. Returns subject (Subject), description (Symptom), category, status, requester, and ownership fields.
Inputs: rec_id (required). Returns: owner, impact, rec_id, source, +20 more
Mark an incident resolved. Reads Status first and no-ops if already closed. Writes Status (or a Quick Action) and an optional close note.
Inputs: rec_id (required), resolution_note. Returns: detail, rec_id, status, skipped
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 3 tools
Each tool has a clearly distinct purpose: get_incident reads incident data, add_note writes to the journal, and resolve_incident changes status. There is no meaningful overlap between read and write operations.
All tool names use lowercase snake_case with a verb-first pattern. However, add_note does not explicitly reference incidents like the other two tools, so using add_incident_note would make the naming more consistent.
Three tools is at the lower end of the typical range but appropriate for a focused incident-handling server. Each tool is essential and earns its place without redundancy.
The set covers the common workflow of viewing an incident, adding a note, and resolving it. However, it lacks create, update, search/list, and other lifecycle operations, so it only partially covers the broader incident management domain.
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
Build and run AI workflows, agents, data tables and 1000+ API integrations from any MCP client.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
AI-powered incident management and server monitoring via MCP.
