LiveAgent MCP for AI. Get full visibility into customer support data, instantly.
Works with every AI agent you already use
…and any MCP-compatible client








How this MCP server connects to your AI agent
LiveAgent MCP gives your agent direct access to every facet of your customer support operations. Pull ticket history, review full conversation threads, and check call records—all without leaving your workflow.
It centralizes everything from company details to performance reports into a single conversational interface.
What AI agents can do with LiveAgent Automation
Get settings
Retrieves core account configuration parameters for LiveAgent.
List ticket history
Fetches the complete, paginated history of a specific support ticket.
List tickets
Retrieves a filtered list of open and closed tickets using advanced JSON filters.
You can list all active tickets or check the detailed history of any given ticket to understand the full scope of the issue.
Retrieve complete conversation threads, update statuses, and add internal notes directly into a client’s record.
Pull call records and view which phone numbers are configured in the system for immediate reference.
Get profiles for specific agents or pull detailed information about associated companies.
Pull time reports, list customer groups, and manage core account settings to understand overall performance.
Ask an AI about this
Waiting for input…
What AI agents can do with LiveAgent MCP Tools (16)
These tools allow you to interact directly with every core function of your LiveAgent support desk, from reading tickets to updating company profiles.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using LiveAgent on VinkiusGet Settings
Retrieves core account configuration parameters for LiveAgent.
List Ticket History
Fetches the complete, paginated history of a specific support ticket.
List Tickets
Retrieves a filtered list of open and closed tickets using advanced JSON filters.
List Time Reports
Gets aggregated time reports, useful for tracking agent productivity over set...
Update Conversation Status
Changes the current status of a customer conversation (e.g., Open to Pending).
Add Customer Fields
Allows you to add or modify custom data fields attached to a specific customer account.
Add Conversation Message
Adds an internal note or public message into an existing conversation thread for the team to see.
List Calls
Retrieves a paginated list of all call records associated with the account.
List Companies
Gets a simple list of every company linked to your LiveAgent instance.
List Conversations
Lists all customer conversations or tickets, supporting optional filtering...
List Customer Groups
Provides a list of defined customer groups used for segmentation and reporting.
Delete Conversation
Permanently deletes a specified conversation thread from the system.
Get Agent
Retrieves detailed profile information and authentication tokens for specific agents.
Get Company
Fetches all core details for a single company record.
Get Conversation
Retrieves the full, detailed contents of one specific conversation thread.
List Phone Numbers
Fetches a paginated list of all phone numbers configured within your account.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with LiveAgent, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by LiveAgent. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 16 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The constant context switch between support platforms kills productivity., Solved with Vinkius AI Gateway
Right now, solving a single customer issue requires logging into the ticketing system, checking the CRM for company details, then maybe switching to a separate call log dashboard. You're copying IDs from one tab and pasting them into another just to stitch together what happened.
With this MCP, you tell your agent what you need—say, 'What did John Smith talk about last week?' The system automatically checks the conversation history using `get_conversation`, cross-references his company details via `list_companies`, and pulls up relevant call logs. You get one complete answer.
Manage your entire support data lifecycle with LiveAgent MCP.
You don't have to manually check if a ticket is still open, or remember which notes were added weeks ago. You can ask the agent to list all tickets using `list_tickets` and then use `add_conversation_message` to update the record immediately after solving it.
The result is a verifiable, single source of truth for every customer interaction. The data flows instantly from discovery to resolution, without you ever leaving your chat window.
What your AI can actually do with this
Managing a modern helpdesk means juggling multiple screens: the ticketing system, the CRM, the call logs. This MCP connects all those pieces directly to your AI agent. Instead of searching through separate dashboards, you can ask your agent to list open tickets or pull up the full history for any customer conversation.
You can even make internal notes right within a thread using add_conversation_message. For developers, it's a huge win: instead of writing complex API calls just to check an account setting, you simply ask. Since Vinkius hosts this MCP, your agent gets access instantly, letting you manage customer support operations through natural conversation.
019ea5f6-42de-71fd-80ff-58a100a7fa8f Here's how it actually works
The bottom line is: you talk to your AI client, and it does the heavy lifting across your entire support stack.
First, you subscribe to the LiveAgent MCP on Vinkius and supply your specific LiveAgent Domain and API key.
Next, your AI client connects using those credentials. It authenticates with LiveAgent's system endpoints.
Finally, your agent can call any available tool—like listing tickets or retrieving conversation details—and you get the structured data back in a conversational format.
Who is this actually for?
This MCP is for anyone whose job requires constant context switching between support data sources. If you're tired of logging into three different dashboards just to get a full picture of a customer issue, this is built for you.
You use the agent to quickly pull up conversation history and company details right before a meeting, so you walk in fully informed.
You monitor ticket volumes or check list_time_reports without leaving your main workflow screen, getting an instant overview of agent performance.
You integrate support data into custom scripts or use the agent to debug customer issues by fetching specific account settings and ticket histories from the IDE.
What Changes When You Connect
You stop bouncing between tabs. By using get_conversation and list_tickets, you pull all necessary context—the issue, the history, and the conversation notes—into one chat window.
No more manual reporting. Instead of exporting data to Excel for analysis, ask your agent to run a report via list_time_reports and get the summary right away.
Better records mean better compliance. Need to check who called? Use list_calls or list_phone_numbers to verify contact details without logging into the phone system.
Always know the customer. You can instantly fetch company data using get_company and even add custom context fields via add_customer_fields during a live chat.
Faster resolution times are built in. When you get full conversation details with get_conversation, you cut down on back-and-forth questions and jump straight to solving the problem.
See it in action
Handling a complex billing dispute
A customer calls about a charge they don't recognize. Instead of searching three places, you ask your agent to pull up both the get_company details and any related tickets using list_tickets. This immediately shows if the issue was reported before or if there are recent call records in list_calls, allowing you to give a precise answer instantly.
Onboarding a new team member
A manager needs to audit agent activity. They use the MCP to run reports, checking both profile information using get_agent and overall performance metrics via list_time_reports. This gives them an objective view of who is handling what volume of work.
Closing out a critical support thread
The issue was resolved, but the record needs to be perfect. You use your agent to update the status using update_conversation_status, and then add a final internal summary note via add_conversation_message for future reference.
Preparing for a quarterly review
You need data on which customer segments are causing the most trouble. You ask your agent to list all customer groups using list_customer_groups, and then cross-reference that against ticket volume using list_conversations.
The honest tradeoffs
Treating it like a simple search bar
Typing 'Show me the billing issue for John Smith' and expecting a neat, formatted report. The agent needs specific instructions to pull data from multiple sources.
Ignoring status updates
Just reading old ticket history (list_ticket_history) without updating the record when the issue is resolved. This leaves the team confused about next steps.
Assuming data availability
Asking for a specific report or conversation detail without knowing if it exists or requires parameters. The agent needs to know which tool, like get_conversation or list_companies, is needed first.
Manual cross-referencing
Copying a customer ID from the ticket view and pasting it into the company CRM dashboard. This adds unnecessary clicks and potential for human error.
When It Fits, When It Doesn't
Use this MCP if your primary pain point is context switching across multiple internal systems to solve one customer problem. If you need to pull data that lives in tickets, calls, user profiles, or company records, this connector makes it accessible via conversation.
Don't use this if you only need to perform a single function—like just checking the current time or sending an email. For those limited tasks, a simple messaging tool works better. Also, remember that while tools like list_tickets and list_conversations give you lists, they don't solve the underlying process problem; they just provide the raw data for your agent to interpret.
Questions you might have
How do I check ticket history using LiveAgent MCP? +
You use the list_ticket_history tool. This function retrieves all paginated records associated with a specific ticket ID, letting you see every status change and note added over time.
Can I list customer groups with LiveAgent MCP? +
Yes, the list_customer_groups tool allows you to retrieve all defined customer segments. This is useful for running reports or targeting specific communication campaigns.
What if I need to check agent information? How do I use LiveAgent MCP? +
Use the get_agent tool. It retrieves detailed profiles, including current status and authentication tokens, so you can verify who is handling which account.
Does LiveAgent MCP let me update conversation statuses? +
Yes, you use the update_conversation_status tool. This changes the ticket's lifecycle state, ensuring your team knows if it’s pending a reply or fully closed.
What is the difference between list_tickets and list_conversations? +
Both list records, but list_tickets focuses on ticket status and history, while list_conversations provides a broader view of all communication threads, regardless of their current ticketing status.
We've already built the connector for LiveAgent. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 16 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.