Integration

NeetoDesk integration

NeetoDesk is a customer support help desk. List, filter (status, priority, tags, assignee, customer, custom field, date range) and read tickets, create and update tickets, read and post ticket comments (replies or internal notes) and drafts, upload attachments, manage customers, custom ticket fields and team members, and pull reports (ticket volume, daily time series, agent and team performance, customer satisfaction). Not exposed: the reserve-then-PUT attachment upload (it returns a signed storage URL; use upload_attachment instead), attachment download links, customers' phone numbers, team members' profile photos, and the extra to and cc recipients of a new ticket. Authentication: a workspace API key of type General (Admin panel, API keys) sent in the X-Api-Key header, plus your workspace subdomain; a key works only in its own workspace. Neeto publishes no numeric rate limit: going over it answers HTTP 429.

Connect NeetoDesk How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with NeetoDesk

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.

Field, 5 operations

create_fieldCreate fieldPOSTCreates a custom ticket field for real (text, number, date, checkbox or option list) that agents and customers then see on tickets. Returns the field with its id and option ids.
delete_fieldDelete fieldDELETEDeletes a custom ticket field for real, together with the values stored on every ticket. The field must first be made inactive with update_field.
get_fieldGet fieldGETReturns one custom ticket field by id: name, kind, state, required flags, display order, slug and options with their ids.
list_fieldsList fieldsGETLists the workspace's custom ticket fields in display order, with kind, state, required flags and options (id and label). Filter by state.
update_fieldUpdate fieldPATCHChanges a custom ticket field for real: name, state, required flags, order, slug, or its options (add, rename, remove). Only the fields sent change; the kind cannot change.

Team member, 5 operations

create_team_memberCreate team memberPOSTAdds people to the workspace for real by email with a role; send_invitation_email decides whether NeetoDesk emails them an invitation.
delete_team_memberDelete team memberDELETERemoves a team member from the workspace for real: they lose access to NeetoDesk.
get_team_memberGet team memberGETReturns one team member by id: email, names, time zone, workspace role and active flag.
list_team_membersList team membersGETLists the workspace's team members (id, email, names, role, time zone, active flag), 30 per page by default. Filter by email.
update_team_memberUpdate team memberPATCHChanges a team member's email, names, time zone or workspace role for real. Only the fields sent change; leave a field out to keep its current value.

Ticket, 5 operations

create_ticketCreate ticketPOSTCreates a ticket for real for a customer email, with subject and description. skip_notifications decides whether automation rules, their emails, webhooks and agent notifications fire.
get_ticketGet ticketGETReturns one ticket by id or number: subject, HTML description, status, priority, category, group, tags, assignee, customer and custom field values.
get_ticket_volume_reportGet ticket volume reportGETTicket counts per status for a time range, each with the previous period's count and the change percentage. Defaults to the last 30 days; each previous value covers the period of the same length just before.
list_ticketsList ticketsGETLists tickets newest first, 30 per page by default. Filter by status, priority, tags, assignee, customer, subject text, custom field, external_id or created date range.
update_ticketUpdate ticketPUTChanges a ticket for real (status, priority, assignee, group, category, fields, subject, tags). Only fields sent change; tags replaces all tags, add_tags/remove_tags keep the others.

Comment, 3 operations

create_commentCreate commentPOSTPosts a reply or internal note on a ticket for real. send_email true emails a reply to the customer and followers; mentions on a note email the mentioned users.
get_commentGet commentGETReturns one comment of a ticket by id: type (reply or note), HTML content, created time and mentions.
list_commentsList commentsGETLists a ticket's comments (replies and internal notes) with author, HTML content, attachment file names and mentions, 30 per page by default.

Customer, 3 operations

create_customerCreate customerPOSTCreates a customer record for real from one or more email addresses, with optional names, phones, links, language, time zone, notes and company. Returns the new customer and its id.
get_customerGet customerGETReturns one customer by id: name, primary and other emails, language, time zone, notes and company.
list_customersList customersGETLists the workspace's customers (id, name, emails, language, time zone, company), oldest first, 30 per page by default. Filter by exact email.

Agent, 1 operation

get_agent_performance_reportGet agent performance reportGETPer-agent performance for a time range (default last 30 days): first response time, resolution time, tickets assigned and closed, each against the previous period, plus totals.

Attachment, 1 operation

upload_attachmentUpload attachmentPOSTUploads one file (up to 50 MB by default) and returns its signed_id; pass that id in attachments on create_ticket, create_comment or create_draft_comment. Unattached uploads are cleaned up.

Draft, 1 operation

create_draft_commentCreate draft commentPOSTSaves a draft reply or note on a ticket, not sent to anyone; an agent sends it later from NeetoDesk. Passing author_email appends that user's stored signature.

Form, 1 operation

list_ticket_formsList ticket formsGETLists the enabled web forms customers use to raise tickets (id, title, slug), plus the name of the linked knowledge base. Disabled forms are left out.

Group, 1 operation

get_team_performance_reportGet team performance reportGETPer-team (group) performance for a time range (default last 30 days): first response time, resolution time, tickets assigned and closed, each against the previous period.

Survey, 1 operation

get_customer_satisfaction_reportGet customer satisfaction reportGETCustomer satisfaction survey results for a time range: each survey's question and the number of responses per rating choice. Defaults to the last 30 days; each previous value covers the period of the same length just before.

Ticket time series, 1 operation

get_ticket_time_series_reportGet ticket time series reportGETDaily counts of new and closed tickets over a time range, ready for charting: dates[] gives the days, data[].values the counts per series. Defaults to the last 30 days; each previous value covers the period of the same length just before.

Use NeetoDesk from Claude Code, Cursor or Codex

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

Create your workspace
Sign up free. Nothing to install.
Connect NeetoDesk once
Add your NeetoDesk 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.