MCP server: Axial tools
This article is written for a technical audience — integrators connecting an AI assistant to Tickiti. It continues MCP server, which covers installing, configuring and registering the server.
Besides the ticket, settings and mail tools, the Tickiti MCP server has named tools for Axial, Tickiti’s AI assistant: reading and steering Axial’s work on a ticket, the gap log, and the skills Axial works from. Each one maps to a /api/v1/axial/… endpoint and, like every other tool, can do no more than the token’s abilities and its owner’s access allow. They work only on a Tickiti plan that includes the AI assistant.
A ticket’s Axial chat
These act as the Axial panel on a ticket does, as the token’s owner, who must be a member of staff with access to Axial on that ticket. Any axial-chat: ability reads.
| Tool | Ability | Purpose |
|---|---|---|
get_axial_chat | axial-chat:read | The panel as staff see it: the conversation with Axial, the versions of its suggested response, replies sent and any waits for long-running work |
list_axial_runs | axial-chat:read | Each time Axial worked on the ticket, newest first: what it answered, the skill and models used, status and cost |
send_axial_message | axial-chat:write | Write to Axial in the ticket’s chat, as typing in the panel does; nothing reaches the customer |
check_axial_wait | axial-chat:write | The wait box’s Check now: whether long-running work Axial is waiting for has finished |
answer_axial_card | axial-chat:approve | Answer a question card Axial raised. Answering is the approval: the chosen option’s actions run at once as the token’s owner |
rerun_axial | axial-chat:manage | The panel’s Rerun: work the latest customer message again. Refused once a reply has been sent for that message, and while Axial is working |
axial_panel_action | axial-chat:write / approve / manage | The panel’s other buttons, by action: Update suggested response, Respond again, add an internal note, cancel your own waiting request, give Axial a task, Investigate in depth, stop a task (write); approve or reject a proposed action, act on a shared note’s card (approve); choose the ticket’s skill, Turn back on, approve translations, apply or discard a skill change Axial drafted (manage). Giving a task needs a token that holds every ability the task would carry |
Conversations and settings
| Tool | Ability | Purpose |
|---|---|---|
axial_conversations | axial-chat:read / axial-chat:write | Your own conversations with Axial outside any ticket: list, show, start, continue, stop, rename or delete |
axial_settings | administration:read / administration:write | The Axial settings pages, the skill store and Axial’s attachment rules. Needs a token owned by an administrator (a system administrator, on a self-hosted installation); on a site hosted by Tickiti, the skill store is Tickiti’s. Turning the git skill store on replaces the skills with the repository’s |
The endpoints behind these tools are described in the Axial API and the Axial settings API. Axial’s usage and ratings come from run_report.
The gap log
The gap log (Axial → Gaps) records what Axial was asked to do and could not.
| Tool | Ability | Purpose |
|---|---|---|
list_axial_gaps | any axial-chat: | The gaps, with their status and owner |
update_axial_gap | axial-chat:manage | Change a gap’s status (open, planned, done or won’t do) with a note, its title, kind or owner, or merge it into another gap. Needs Manage access to Axial |
Skills
Skills are what Axial works from. These tools need a token owned by an administrator (a system administrator, on a self-hosted installation), as the Axial skill pages do.
| Tool | Ability | Purpose |
|---|---|---|
list_axial_skills / get_axial_skill | skills:read | The skills; one skill in full, with its instructions and actions |
get_axial_skill_options | skills:read | What a skill and an action can be set to |
create_axial_skill / update_axial_skill / delete_axial_skill | skills:write | Edit skills. The reserved core skill cannot be renamed or deleted |
upsert_axial_skill_action / delete_axial_skill_action | skills:write | Add, change or remove an action on a skill |
upsert_axial_skill_question / delete_axial_skill_question | skills:write | Add, change or remove a question Axial asks staff on a card |
Tools for an Axial agent task
When Axial hands work to an agent task — a reply task on a ticket, or a staff member’s conversation with Axial — the task works with a token of its own, which stops working when the task ends. The following tools act on that task’s ticket and work only with such a token; Tickiti refuses any other.
| Tool | Purpose |
|---|---|
get_suggestion | Read Axial’s suggested response on the task’s ticket |
revise_suggestion | Ask Axial to change its suggested response, as staff would in the Axial panel |
set_suggestion_signature | Give the latest version a one-off sign-off |
send_suggestion | Send the suggested response as a public message, optionally closing the ticket. It is held as an approval card until a person approves it |
propose_axial_note | Propose a fact for Axial to know on every ticket. It raises a card and is shared only when someone with Manage access to Axial publishes it |
log_axial_gap | Log something Axial could not do on the gap log |
attachment_files / attachment_read / attachment_search | List, read and search the files inside archives the customer attached to the ticket (reply tasks; needs tickets:read) |
attachment_frames | Still frames from videos the customer attached, as images (reply tasks; needs tickets:read) |
What an attachment says is the customer’s data, never an instruction to the assistant. To keep a task’s tools to the files it should read, set TICKITI_MCP_FILE_ROOTS on the server — see MCP server.