Integration

Merge Ticketing integration

Merge Ticketing is Merge's unified API for ticketing and project management tools: one call shape reads and writes whichever system (Jira, Zendesk, Linear, Asana, ServiceNow, GitHub Issues and others) a Merge Linked Account connects. List and read tickets, comments, attachments (and download their files), collections (projects, boards, lists), accounts, contacts, teams, roles, tags, users and who can view a ticket or collection; create tickets, comments, contacts and attachments, update tickets, and read which fields a write needs for the connected system. Comments and tickets reach real people through the ticketing system. Not exposed: the live ticket search (undocumented answer), the deprecated Project model (use collections, whose type can be PROJECT), raw third-party records and unmapped remote fields, passthrough requests and Linked Account, key, webhook, field mapping, scope and sync administration. Calls go to Merge's US region (api.merge.dev). Authentication is a Merge API key (Authorization: Bearer) plus one Linked Account's account token (X-Account-Token), so one connection reads one ticketing account.

Connect Merge Ticketing How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Merge Ticketing.Built from the 36 Merge Ticketing tools below, on the connection you add once.

What you can do with Merge Ticketing

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.

Post, 4 operations

get_attachment_create_metadataGet attachment create metadataGETReturns the request schema the connected ticketing system accepts to create an attachment: fields, required ones and integration-specific parameters. Call it before the write.
get_comment_create_metadataGet comment create metadataGETReturns the request schema the connected ticketing system accepts to create a comment: fields, required ones and integration-specific parameters. Call it before the write.
get_contact_create_metadataGet contact create metadataGETReturns the request schema the connected ticketing system accepts to create a contact: fields, required ones and integration-specific parameters. Call it before the write.
get_ticket_create_metadataGet ticket create metadataGETReturns the request schema the connected ticketing system accepts to create a ticket: fields, required ones and integration-specific parameters. Call it before the write.

Ticket, 4 operations

create_ticketCreate ticketPOSTCreates a ticket in the connected ticketing system, which may notify its assignees. Call get_ticket_create_metadata first: required fields vary by system.
get_ticketGet ticketGETReturns a `Ticket` object with the given `id`.
list_ticketsList ticketsGETReturns a list of `Ticket` objects.
update_ticketUpdate ticketPATCHUpdates a ticket in the connected ticketing system with the fields sent in model. Call get_ticket_update_metadata first to see which fields this system lets you change.

Attachment, 3 operations

create_attachmentCreate attachmentPOSTAttaches a file to a ticket in the connected ticketing system from the file's URL (file_url); both file_name and file_url must include the file extension.
get_attachmentGet attachmentGETReturns an `Attachment` object with the given `id`.
list_attachmentsList attachmentsGETReturns a list of `Attachment` objects.

Comment, 3 operations

create_commentCreate commentPOSTAdds a comment to a ticket in the connected ticketing system. Unless is_private is true, the system may show or send it to the people on the ticket. Call get_comment_create_metadata first.
get_commentGet commentGETReturns a `Comment` object with the given `id`.
list_commentsList commentsGETReturns a list of `Comment` objects.

Contact, 3 operations

create_contactCreate contactPOSTCreates a contact (a customer, lead or external user a ticket can be linked to) in the connected ticketing system. Call get_contact_create_metadata first: required fields vary by system.
get_contactGet contactGETReturns a `Contact` object with the given `id`.
list_contactsList contactsGETReturns a list of `Contact` objects.

Account, 2 operations

get_accountGet accountGETReturns an `Account` object with the given `id`.
list_accountsList accountsGETReturns a list of `Account` objects.

Collection, 2 operations

get_collectionGet collectionGETReturns a `Collection` object with the given `id`.
list_collectionsList collectionsGETReturns a list of `Collection` objects.

Role, 2 operations

get_roleGet roleGETReturns a `Role` object with the given `id`.
list_rolesList rolesGETReturns a list of `Role` objects.

Tag, 2 operations

get_tagGet tagGETReturns a `Tag` object with the given `id`.
list_tagsList tagsGETReturns a list of `Tag` objects.

Team, 2 operations

get_teamGet teamGETReturns a `Team` object with the given `id`.
list_teamsList teamsGETReturns a list of `Team` objects.

User, 2 operations

get_userGet userGETReturns a `User` object with the given `id`.
list_usersList usersGETReturns a list of `User` objects.

Viewer, 2 operations

list_collection_viewersList collection viewersGETReturns a list of `Viewer` objects that point to a User id or Team id that is either an assignee or viewer on a `Collection` with the given id. [Learn more.](https://help.merge.dev/en/articles/10333658-ticketing-access-control-list-acls)
list_ticket_viewersList ticket viewersGETReturns a list of `Viewer` objects that point to a User id or Team id that is either an assignee or viewer on a `Ticket` with the given id. [Learn more.](https://help.merge.dev/en/articles/10333658-ticketing-access-control-list-acls)

Account detail, 1 operation

get_account_detailsGet account detailsGETReturns the Linked Account behind the connection: integration name and slug, category, status, end user organization and email, and account type.

Available action, 1 operation

get_available_actionsGet available actionsGETReturns the integration behind the Linked Account and, per Common Model, the operations it supports (FETCH, CREATE...), the fields it fills and the parameters a create must send.

Download, 1 operation

download_attachmentDownload attachmentGETDownloads the file of a ticket attachment and stores it as a file.

Patch, 1 operation

get_ticket_update_metadataGet ticket update metadataGETReturns the request schema the connected ticketing system accepts to update a ticket: fields, required ones and integration-specific parameters. Call it before the write.

Sync status, 1 operation

get_sync_statusGet sync statusGETReturns the sync state of each Common Model for the Linked Account: last and next sync start, last result and finish time. Data read through the other tools is as fresh as the last sync.

Use Merge Ticketing from Claude Code, Cursor or Codex

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

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