1.5 MCP server

Ops I provides an MCP server.
By connecting to the MCP server, AI agents can perform Ops I operations on behalf of users.

AI agents can connect to the MCP server via endpoints (URLs) categorized by purpose and execute the tools associated with those endpoints.
Additionally, authentication is required to connect to and use the MCP server. Grant the user the appropriate permissions, issue a Ops I token, and then configure the connection settings.

This section explains the endpoints, required permissions, and tools. For use cases and configuration examples, see “Designing and Building Your Operation > Collaborating with AI agents” and “Designing and Building Your Operation > Collaborating with AI agents > Examples of collaboration with AI agents” in “JP1 Cloud Service/Operations Integration User’s Guide”.

(1) Endpoints

AI agents connect to the MCP server using the Streamable HTTP method.
Authentication is required for each endpoint to connect to and use the MCP server. You must specify the Ops I token in the X-Ops I Token header during communication.
This section explains the endpoints and the permissions required to use them.

(Table) Endpoints and required permissions

Endpoint	Required permissions (Primitive role)	Description
/ai/v1/itsm/mcp	Any of the following: itsm_admin itsm_manager itsm_user To use the "extract_symptoms_from_ticket" or "generate_knowledge_article_from_ticket" tool: ai_extension_user	Ticket and knowledge article operations
/ai/v1/manual/mcp	None	Definition file-related documentation retrieval

Endpoint

Required permissions (Primitive role)

Description

/ai/v1/itsm/mcp

Any of the following:

itsm_admin
itsm_manager
itsm_user

To use the "extract_symptoms_from_ticket" or "generate_knowledge_article_from_ticket" tool:

ai_extension_user

Ticket and knowledge article operations

/ai/v1/manual/mcp

None

Definition file-related documentation retrieval

(2) List of tools

The tools available for each endpoint are listed in the table below.

(Table) List of tools

Tool name		Description
Endpoint: /ai/v1/itsm/mcp
	search_tickets_by_symptoms	Searches for an incident ticket or case ticket based on a symptom.
	extract_symptoms_from_ticket	Extracts a symptom from an incident ticket or case ticket ID.
	get_ticket_by_id	Retrieves information about an incident ticket or case ticket from a ticket ID.
	get_work_notes	Retrieves work notes from an incident ticket or case ticket ID.
	generate_knowledge_article_from_ticket	Summarizes the contents of an incident ticket or case ticket, and returns them in knowledge article format. Tips The returned knowledge article is not saved in Ops I.
	search_knowledge_articles_by_symptoms	Searches for knowledge articles based on symptoms.
	create_incident	Creates an incident ticket.
	update_incident	Updates an incident ticket.
	create_work_note	Posts work notes for an incident ticket or case ticket.
	get_tickets	The API obtains a list of tickets.
Endpoint: /ai/v1/manual/mcp
	get_opsi_manifest_doc	Retrieves common specifications for YAML files and definition information for the following types: workflow ui uipath datamodel catalog script library attachment distribution acl statement notification notifier application Tips This endpoint does not support definitions for ui and script UI version 1.0.
	get_custom_script_doc	Retrieves definition information regarding Ops I custom scripts.
	get_playbook_doc	Retrieves information about the Playbook execution environment.

For details on "symptoms", see "Functions > Basic window structure > AI extension function" in "JP1 Cloud Service/Operations Integration User's Guide".