Integration

Xurrent integration

Xurrent (formerly 4me) is a service management platform for IT and enterprise service desks. Through its REST API an agent can list, read, create and update requests (tickets), problems, problem tasks, workflows (changes) and their tasks, projects and project tasks, releases, risks, time entries, people, teams, organizations, sites, services, service instances, configuration items and knowledge articles, read SLAs, contracts, request templates and enumerations, and read or add notes. Lists page 20 records at a time (per_page up to 100; the next page's search_after cursor is in the link output) and filter on the documented fields. People, requests and notes are personal data. Not exposed: archive, trash, restore and delete routes, linking and unlinking routes, attachments uploads, imports and exports, audit entries, webhooks, OAuth, SSO and SCIM, and account and configuration resources. Authentication is a personal access token (My Profile, Personal Access Tokens) with scopes for the actions used, sent as a Bearer token, plus the account id in the X-Xurrent-Account header; the API host names the environment and region.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Xurrent.Built from the 100 Xurrent tools below, on the connection you add once.

What you can do with Xurrent

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Note, 14 operations

  • add_problem_noteAdd problem notePOSTAgents: ask firstAdds a note to one problem. Xurrent creates its Note Added notifications unless suppress_note_added_notifications is true.
  • add_project_noteAdd project notePOSTAgents: ask firstAdds a note to one project. Xurrent creates its Note Added notifications unless suppress_note_added_notifications is true.
  • add_project_task_noteAdd project task notePOSTAgents: ask firstAdds a note to one project task. Xurrent creates its Note Added notifications unless suppress_note_added_notifications is true.
  • add_release_noteAdd release notePOSTAgents: ask firstAdds a note to one release. Xurrent creates its Note Added notifications unless suppress_note_added_notifications is true.
  • add_request_noteAdd request notePOSTAgents: ask firstAdds a note to one request; internal=true makes it internal. Xurrent creates its Note Added notifications unless suppress_note_added_notifications is true.
  • add_task_noteAdd task notePOSTAgents: ask firstAdds a note to one task. Xurrent creates its Note Added notifications unless suppress_note_added_notifications is true.
  • add_workflow_noteAdd workflow notePOSTAgents: ask firstAdds a note to one workflow. Xurrent creates its Note Added notifications unless suppress_note_added_notifications is true.
  • list_problem_notesList problem notesGETAgents: ask firstLists the notes of one problem (author, text, medium, time, attachments), 20 per page; page with search_after from link. Notes can hold personal data.
  • list_project_notesList project notesGETAgents: ask firstLists the notes of one project (author, text, medium, time, attachments), 20 per page; page with search_after from link. Notes can hold personal data.
  • list_project_task_notesList project task notesGETAgents: ask firstLists the notes of one project task (author, text, medium, time, attachments), 20 per page; page with search_after from link. Notes can hold personal data.
  • list_release_notesList release notesGETAgents: ask firstLists the notes of one release (author, text, medium, time, attachments), 20 per page; page with search_after from link. Notes can hold personal data.
  • list_request_notesList request notesGETAgents: ask firstLists the notes of one request (author, text, medium, time, attachments), 20 per page; page with search_after from link. Notes can hold personal data.
  • list_task_notesList task notesGETAgents: ask firstLists the notes of one task (author, text, medium, time, attachments), 20 per page; page with search_after from link. Notes can hold personal data.
  • list_workflow_notesList workflow notesGETAgents: ask firstLists the notes of one workflow (author, text, medium, time, attachments), 20 per page; page with search_after from link. Notes can hold personal data.

Person, 7 operations

  • create_personCreate personPOSTAgents: ask firstCreates a person in Xurrent (required: name, primary_email) and returns it with all its fields.
  • get_meGet meGETAgents: ask firstReturns the Xurrent person the token belongs to: name, primary email, job title, site, organization, manager, contacts and addresses. Returns personal data.
  • get_personGet personGETAgents: ask firstReturns one person by id with all its fields (references come as id and name). Returns personal data.
  • list_organization_peopleList organization peopleGETAgents: ask firstLists the people of one organization (name, site, manager), 20 per page; page with search_after from link. Returns personal data.
  • list_peopleList peopleGETAgents: ask firstLists people (personal data), 20 per page (per_page up to 100), with name, organization, site, manager by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.
  • list_team_membersList team membersGETAgents: ask firstLists the people who are members of one team (name, site, organization, manager), 20 per page. Returns personal data.
  • update_personUpdate personPATCHAgents: ask firstUpdates the fields you send on one person (by id); a field left out keeps its value. Returns the updated person.

Request, 5 operations

  • create_requestCreate requestPOSTAgents: ask firstCreates a request in Xurrent (required: category, requested_by_id, subject) and returns it with all its fields.
  • get_requestGet requestGETAgents: ask firstReturns one request by id with all its fields (references come as id and name). Returns personal data (requested_by, requested_for, ticket text).
  • list_requestsList requestsGETAgents: ask firstLists requests (personal data), 20 per page (per_page up to 100), with subject, category, impact, status, next_target_at by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.
  • list_workflow_requestsList workflow requestsGETAgents: ask firstLists the requests linked to one workflow (subject, category, impact, status, team, member, next target), 20 per page; page with search_after from link. Returns personal data.
  • update_requestUpdate requestPATCHAgents: ask firstUpdates the fields you send on one request (by id); a field left out keeps its value. Returns the updated request.

Task, 5 operations

  • create_taskCreate taskPOSTAgents: ask firstCreates a task in Xurrent (required: category, planned_duration, subject, team_id, template_id) and returns it with all its fields.
  • get_taskGet taskGETAgents: ask firstReturns one task by id with all its fields (references come as id and name).
  • list_tasksList tasksGETAgents: ask firstLists tasks, 20 per page (per_page up to 100), with subject, impact, category, status, team by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.
  • list_workflow_tasksList workflow tasksGETAgents: ask firstLists the tasks of one workflow (subject, category, status, team, member, completion target), 20 per page; page with search_after from link.
  • update_taskUpdate taskPATCHAgents: ask firstUpdates the fields you send on one task (by id); a field left out keeps its value. Returns the updated task.

Team, 5 operations

  • create_teamCreate teamPOSTAgents: ask firstCreates a team in Xurrent (required: name) and returns it with all its fields.
  • get_teamGet teamGETAgents: ask firstReturns one team by id with all its fields (references come as id and name).
  • list_person_teamsList person teamsGETAgents: ask firstLists the teams one person is a member of, 20 per page; page with search_after from link.
  • list_teamsList teamsGETAgents: ask firstLists teams, 20 per page (per_page up to 100), with name by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.
  • update_teamUpdate teamPATCHAgents: ask firstUpdates the fields you send on one team (by id); a field left out keeps its value. Returns the updated team.

Configuration item, 4 operations

  • create_configuration_itemCreate configuration itemPOSTAgents: ask firstCreates a configuration item in Xurrent (required: product_id, status) and returns it with all its fields.
  • get_configuration_itemGet configuration itemGETAgents: ask firstReturns one configuration item by id with all its fields (references come as id and name).
  • list_configuration_itemsList configuration itemsGETAgents: ask firstLists configuration items, 20 per page (per_page up to 100), with software, label, name, status, product by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.
  • update_configuration_itemUpdate configuration itemPATCHAgents: ask firstUpdates the fields you send on one configuration item (by id); a field left out keeps its value. Returns the updated configuration item.

Knowledge article, 4 operations

  • create_knowledge_articleCreate knowledge articlePOSTAgents: ask firstCreates a knowledge article in Xurrent (required: description, instructions, service_id, subject) and returns it with all its fields.
  • get_knowledge_articleGet knowledge articleGETAgents: ask firstReturns one knowledge article by id with all its fields (references come as id and name).
  • list_knowledge_articlesList knowledge articlesGETAgents: ask firstLists knowledge articles, 20 per page (per_page up to 100), with subject, status, service by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.
  • update_knowledge_articleUpdate knowledge articlePATCHAgents: ask firstUpdates the fields you send on one knowledge article (by id); a field left out keeps its value. Returns the updated knowledge article.

Organization, 4 operations

  • create_organizationCreate organizationPOSTAgents: ask firstCreates an organization in Xurrent (required: name) and returns it with all its fields.
  • get_organizationGet organizationGETAgents: ask firstReturns one organization by id with all its fields (references come as id and name).
  • list_organizationsList organizationsGETAgents: ask firstLists organizations, 20 per page (per_page up to 100), with name, parent, manager by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.
  • update_organizationUpdate organizationPATCHAgents: ask firstUpdates the fields you send on one organization (by id); a field left out keeps its value. Returns the updated organization.

Problem, 4 operations

  • create_problemCreate problemPOSTAgents: ask firstCreates a problem in Xurrent (required: impact, manager_id, service_id, subject) and returns it with all its fields.
  • get_problemGet problemGETAgents: ask firstReturns one problem by id with all its fields (references come as id and name).
  • list_problemsList problemsGETAgents: ask firstLists problems, 20 per page (per_page up to 100), with subject, impact, status, known_error, analysis_target_at by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.
  • update_problemUpdate problemPATCHAgents: ask firstUpdates the fields you send on one problem (by id); a field left out keeps its value. Returns the updated problem.

Problem task, 4 operations

  • create_problem_taskCreate problem taskPOSTAgents: ask firstCreates a problem task in Xurrent (required: problem_id, subject) and returns it with all its fields.
  • get_problem_taskGet problem taskGETAgents: ask firstReturns one problem task by id with all its fields (references come as id and name).
  • list_problem_tasksList problem tasksGETAgents: ask firstLists problem tasks, 20 per page (per_page up to 100), with subject, problem, problem_task_type, priority, status by default; filter on the documented fields, sort, and page with search_after from link.
  • update_problem_taskUpdate problem taskPATCHAgents: ask firstUpdates the fields you send on one problem task (by id); a field left out keeps its value. Returns the updated problem task.

Project, 4 operations

  • create_projectCreate projectPOSTAgents: ask firstCreates a project in Xurrent (required: customer_id, justification, manager_id, program, service_id, subject, time_zone, work_hours_id) and returns it with all its fields.
  • get_projectGet projectGETAgents: ask firstReturns one project by id with all its fields (references come as id and name).
  • list_projectsList projectsGETAgents: ask firstLists projects, 20 per page (per_page up to 100), with subject, manager, category, status, completion_target_at by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.
  • update_projectUpdate projectPATCHAgents: ask firstUpdates the fields you send on one project (by id); a field left out keeps its value. Returns the updated project.

Project task, 4 operations

  • create_project_taskCreate project taskPOSTAgents: ask firstCreates a project task in Xurrent (required: category, planned_duration, subject, template_id) and returns it with all its fields.
  • get_project_taskGet project taskGETAgents: ask firstReturns one project task by id with all its fields (references come as id and name).
  • list_project_tasksList project tasksGETAgents: ask firstLists project tasks, 20 per page (per_page up to 100), with subject, category, status, completion_target_at, finished_at by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.
  • update_project_taskUpdate project taskPATCHAgents: ask firstUpdates the fields you send on one project task (by id); a field left out keeps its value. Returns the updated project task.

Release, 4 operations

  • create_releaseCreate releasePOSTAgents: ask firstCreates a release in Xurrent (required: manager_id, subject) and returns it with all its fields.
  • get_releaseGet releaseGETAgents: ask firstReturns one release by id with all its fields (references come as id and name).
  • list_releasesList releasesGETAgents: ask firstLists releases, 20 per page (per_page up to 100), with subject, impact, status, completion_target_at, completed_at by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.
  • update_releaseUpdate releasePATCHAgents: ask firstUpdates the fields you send on one release (by id); a field left out keeps its value. Returns the updated release.

Risk, 4 operations

  • create_riskCreate riskPOSTAgents: ask firstCreates a risk in Xurrent (required: subject) and returns it with all its fields.
  • get_riskGet riskGETAgents: ask firstReturns one risk by id with all its fields (references come as id and name).
  • list_risksList risksGETAgents: ask firstLists risks, 20 per page (per_page up to 100), with subject, severity, status, mitigation_target_at, closed_at by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.
  • update_riskUpdate riskPATCHAgents: ask firstUpdates the fields you send on one risk (by id); a field left out keeps its value. Returns the updated risk.

Service, 4 operations

  • create_serviceCreate servicePOSTAgents: ask firstCreates a service in Xurrent (required: name, provider_id) and returns it with all its fields.
  • get_serviceGet serviceGETAgents: ask firstReturns one service by id with all its fields (references come as id and name).
  • list_servicesList servicesGETAgents: ask firstLists services, 20 per page (per_page up to 100), with name, provider, support_team by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.
  • update_serviceUpdate servicePATCHAgents: ask firstUpdates the fields you send on one service (by id); a field left out keeps its value. Returns the updated service.

Service instance, 4 operations

  • create_service_instanceCreate service instancePOSTAgents: ask firstCreates a service instance in Xurrent (required: name, service_id) and returns it with all its fields.
  • get_service_instanceGet service instanceGETAgents: ask firstReturns one service instance by id with all its fields (references come as id and name).
  • list_service_instancesList service instancesGETAgents: ask firstLists service instances, 20 per page (per_page up to 100), with name, status, service, support_team by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.
  • update_service_instanceUpdate service instancePATCHAgents: ask firstUpdates the fields you send on one service instance (by id); a field left out keeps its value. Returns the updated service instance.

Site, 4 operations

  • create_siteCreate sitePOSTAgents: ask firstCreates a site in Xurrent (required: name) and returns it with all its fields.
  • get_siteGet siteGETAgents: ask firstReturns one site by id with all its fields (references come as id and name).
  • list_sitesList sitesGETAgents: ask firstLists sites, 20 per page (per_page up to 100), with name by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.
  • update_siteUpdate sitePATCHAgents: ask firstUpdates the fields you send on one site (by id); a field left out keeps its value. Returns the updated site.

Time entry, 4 operations

  • create_time_entryCreate time entryPOSTAgents: ask firstCreates a time entry in Xurrent (required: date, person_id, time_spent) and returns it with all its fields.
  • get_time_entryGet time entryGETAgents: ask firstReturns one time entry by id with all its fields (references come as id and name). Returns personal data.
  • list_time_entriesList time entriesGETAgents: ask firstLists time entries (personal data), 20 per page (per_page up to 100), with date, time_spent, person, request, service, customer, organization by default; filter on the documented fields, sort, and page with search_after from link.
  • update_time_entryUpdate time entryPATCHAgents: ask firstUpdates the fields you send on one time entry (by id); a field left out keeps its value. Returns the updated time entry.

Workflow, 4 operations

  • create_workflowCreate workflowPOSTAgents: ask firstCreates a workflow in Xurrent (required: justification, service_id, subject, template_id, workflow_type) and returns it with all its fields.
  • get_workflowGet workflowGETAgents: ask firstReturns one workflow by id with all its fields (references come as id and name).
  • list_workflowsList workflowsGETAgents: ask firstLists workflows, 20 per page (per_page up to 100), with subject, manager, category, impact, status by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.
  • update_workflowUpdate workflowPATCHAgents: ask firstUpdates the fields you send on one workflow (by id); a field left out keeps its value. Returns the updated workflow.

Contract, 2 operations

  • get_contractGet contractGETAgents: ask firstReturns one contract by id with all its fields (references come as id and name).
  • list_contractsList contractsGETAgents: ask firstLists contracts, 20 per page (per_page up to 100), with name, category, status, supplier by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.

Request template, 2 operations

  • get_request_templateGet request templateGETAgents: ask firstReturns one request template by id with all its fields (references come as id and name).
  • list_request_templatesList request templatesGETAgents: ask firstLists request templates, 20 per page (per_page up to 100), with subject, category, impact, service by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.

Service level agreement, 2 operations

  • get_slaGet slaGETAgents: ask firstReturns one service level agreement by id with all its fields (references come as id and name).
  • list_slasList slasGETAgents: ask firstLists service level agreements, 20 per page (per_page up to 100), with service_offering, name, status by default; filter on the documented fields or a predefined state, sort, and page with search_after from link.

Enumeration, 1 operation

  • list_enumerationsList enumerationsGETAgents: ask firstReturns every Xurrent enumeration (such as request.status or task.category) with each value's id and label, to find the values a field accepts.

Task approval, 1 operation

  • list_task_approvalsList task approvalsGETAgents: ask firstLists the approvals of one approval task: approver, status, planned effort and timestamps, 20 per page.

Use Xurrent from Claude Code, Cursor or Codex

Connect Xurrent in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Xurrent operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Xurrent

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Xurrent once

    Add your Xurrent connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Xurrent integration FAQ

What can you do with the Xurrent integration?

LiveContext exposes 100 operations on Xurrent, covering note, person, request and task.

Popular integrations

Browse the whole catalog