Available Tools and Capabilities

Available tools and capabilities

The Xurrent MCP server exposes 21 tools across the major Xurrent surfaces. Tool availability depends on your PAT's scopes, and the write tools additionally depend on your roles in Xurrent. Tools marked (write) change data in your instance.

Cross-domain search

• global_search: Searches across requests, knowledge articles, request templates, problems, workflows, tasks, and people. Use this as the primary starting point when you do not know which surface holds the record. Recognizes a request ID such as #704540 as a direct lookup. Results are grouped by type and ranked by relevance.

Inbox and assignments

• list_inbox: Returns a prioritized list of assignments that require your direct action. May include requests, problems, tasks, project tasks, and approval tasks.
• search_inbox: Searches your inbox for service requests, tasks, and problem records.
• filter_inbox_records: Filters inbox items by record type, status, impact, service, or team.

Requests

• list_active_requests: Lists all active (open) requests that were requested by or for you.
• summarize_request: Summarizes a request's status, recent updates, and next steps.
• search_request_template: Finds predefined request templates, such as access requests or hardware provisioning. Returns the template ID and any form fields needed to submit it.
• create_request (write): Creates a new request, either from a request template or generically against a support domain. Team, service instance, and requested-for values are resolved by name, and you are asked to choose when a name is ambiguous.
• update_request (write): Updates an existing request's subject, status, category, impact, team, member, requested-for, service instance, or completion reason. A note is required when moving a request to Completed or Waiting for Customer.

Knowledge

• search_knowledge_articles: Searches for knowledge articles, FAQs, or documentation that can help answer questions.
• filter_knowledge_articles: Filters knowledge articles by service or after a last-updated date.
• summarize_knowledge_article: Summarizes a knowledge article's key steps and applicable services.

Problems and tasks

• summarize_problem: Summarizes a problem's status, recent updates, and next steps.
• create_problem (write): Creates a new problem on a service. Requires the Problem Manager role on the account that owns the service.
• update_problem (write): Updates an existing problem's subject, status, category, impact, service, team, or member. Moving a problem to Accepted, In Progress, or Solved assigns it to you. A note is required when moving a problem to Waiting for or Solved.
• summarize_task: Summarizes a task's status, recent updates, and next steps.
• update_task (write): Updates an existing task you have access to.
• summarize_project_task: Summarizes a project task's status, recent updates, and next steps.

Notes

• post_notes (write): Posts a note on a request, task, or problem. Notes are public by default, meaning they are visible to the requester. Internal (specialist-only) notes are supported on requests only.

Boards and services

• list_agile_board_items: Lists items on a given agile board. Items can be requests, problems, tasks, or project tasks.
• service_availability: Checks the status and availability of services you have access to.

Example prompts

• "Show me everything in my inbox that's high impact."
• "Summarize request 1234 and tell me what's blocking it."
• "Find knowledge articles about VPN setup and summarize the top one."
• "Start a new request from the laptop replacement template."
• "Add an internal note to request 1234 with what I found in the logs."
• "Set request 1234 to waiting for customer and let them know we need the error screenshot."
• "Open a problem on the Email service for the recurring Outlook crashes and assign it to my team."
• "What's on the engineering agile board this sprint?"
• "Is the email service available right now?"
• "Search everywhere for anything related to onboarding."

Tool naming conventions

All Xurrent MCP tools follow a consistent verb_noun pattern, for example list_inbox, summarize_request, create_problem. The verbs map to action types: list, search, filter, summarize, create, update, and post. Anything prefixed with create, update, or post writes to your instance. This makes the surface predictable for both people and AI clients discovering what is available.