What can you do with the Freshservice integration?

LiveContext exposes 17 operations on Freshservice, covering ticket, asset, change and requester. Common uses include auditing hardware inventory, provisioning users from an HR system and sending an automated acknowledgement.

LiveContext

All integrations

Freshservice integration

Freshservice ITSM API v2: create, update, search and close tickets, add public or private notes and replies, manage requesters and agents, browse the asset inventory and its types, handle changes and problems, and read service catalogue items. The account subdomain is part of the credential.

17 toolsBasic authAPI docs

Connect Freshservice How integrations work

Common Freshservice use cases

auditing hardware inventory
provisioning users from an HR system
sending an automated acknowledgement
summarising a ticket thread with an LLM
syncing the ticket queue into a dashboard
auto-closing tickets once the alert clears
showing the available services in a portal
removing tickets created by a misfiring alert
attaching automated diagnostics to an incident
resolving an agent id before assigning a ticket

What you can do with Freshservice

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.

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

Ticket, 5 operations

POSTcreate_ticket
Creates a Freshservice ticket with a subject, description and requester.
DELETEdelete_ticket
Moves a Freshservice ticket to the trash.
GETget_ticket
Retrieves one Freshservice ticket with its full description.
GETlist_tickets
Lists Freshservice tickets with a view filter and incremental updates.
PUTupdate_ticket
Updates a Freshservice ticket, including status, priority and assignment.

Asset, 2 operations

GETget_asset
Retrieves one Freshservice asset by its display id.
GETlist_assets
Lists Freshservice assets from the CMDB inventory.

Change, 2 operations

POSTcreate_change
Creates a Freshservice change record with a planned window.
GETlist_changes
Lists Freshservice change records with their risk and planned window.

Requester, 2 operations

POSTcreate_requester
Creates a Freshservice requester.
GETlist_requesters
Lists Freshservice requesters, filtered by email or name.

Agent, 1 operation

GETlist_agents
Lists Freshservice agents with their state and groups.

Asset type, 1 operation

GETlist_asset_types
Lists Freshservice asset types.

Conversation, 1 operation

GETlist_ticket_conversations
Lists the notes and replies on a Freshservice ticket.

Note, 1 operation

POSTadd_ticket_note
Adds an internal or public note to a Freshservice ticket.

Reply, 1 operation

POSTreply_to_ticket
Sends a customer-visible reply on a Freshservice ticket.

Service item, 1 operation

GETlist_service_items
Lists the Freshservice service catalogue items.

Use Freshservice from Claude Code, Cursor or Codex

Connect Freshservice in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Freshservice 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 Freshservice

Create your workspace
Sign up free. Nothing to install.
Connect Freshservice once
Add your Freshservice connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
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.

Freshservice integration FAQ

What can you do with the Freshservice integration?: LiveContext exposes 17 operations on Freshservice, covering ticket, asset, change and requester. Common uses include auditing hardware inventory, provisioning users from an HR system and sending an automated acknowledgement.