FreeScout MCP. Manage tickets and customers using natural conversation.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
FreeScout MCP connects your AI agent directly to your entire helpdesk instance. Use this tool to manage every aspect of customer communication, from listing full mailboxes and retrieving customer profiles to drafting replies and adding internal notes—all without leaving your chat window.
What your AI agents can do
Add note
Adds a private internal note to an existing conversation thread, visible only to your team.
Add reply
Sends a public reply directly to the customer within their active support thread.
List conversations
Provides a list of recent or filtered conversations within a specified mailbox.
List all mailboxes and retrieve specific mailbox details so you know exactly where a conversation lives.
Find existing customer profiles or create brand new ones using the agent.
Create, list, update, and delete entire conversations to track tickets from start to finish.
Send replies directly to customers or add private internal notes for your team's records.
List all available agents and retrieve detailed user information, helping assign tasks efficiently.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
FreeScout MCP: 16 Tools for Support Operations
These tools give your agent direct access to every function of the FreeScout helpdesk, covering everything from listing users to updating conversations.
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 FreeScout on Vinkius019e389badd note
Adds a private internal note to an existing conversation thread, visible only to your team.
019e389badd reply
Sends a public reply directly to the customer within their active support thread.
019e389blist conversations
Provides a list of recent or filtered conversations within a specified mailbox.
019e389bcreate conversation
Initiates and records an entirely new ticket or conversation in your helpdesk system.
019e389bcreate customer
Registers a brand new user account into the customer directory.
019e389blist customers
Retrieves a searchable directory list of all active customer accounts in the system.
019e389bdelete conversation
Permanently removes a conversation from your helpdesk records.
019e389bget conversation
Pulls all current details, history, and status information for a specific ticket ID.
019e389bget customer
Retrieves all stored profile data associated with a named customer account.
019e389bget mailbox
Pulls the current state and contents of an entire support inbox by name or ID.
019e389bget user
Retrieves profile details, status, and contact info for a specific agent user account.
019e389blist mailboxes
Lists every operational support inbox (e.g., 'Sales,' 'Billing') configured in your FreeScout setup.
019e389blist threads
Shows a summary of all message threads contained within one specific conversation ID.
019e389bupdate conversation
Changes the status, assignee, or priority of an existing conversation ticket.
019e389bupdate customer
Modifies specific details (like email address or phone) on an existing customer profile.
019e389blist users
Lists every active user or agent account, including their role and permissions.
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 FreeScout, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ 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 FreeScout. 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
Works with 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 server provides 16 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
The constant switch between your ticketing system and your agent workspace is exhausting.
Right now, if a customer messages you about an issue, you have to stop what you're doing. You open the helpdesk tab, search for their name, find the thread ID, click into it, read all the back-and-forth emails, and then switch tabs again to write your reply in your agent workspace. It takes three clicks just to gather context.
With this MCP, you don't leave the chat window. You tell your AI client to get the conversation history for that customer ID. Your agent pulls all the data—the full thread summary and the last message details—and presents it directly in our chat. It’s instant context, no tab switching required.
FreeScout MCP: Manage Tickets and Customers
Manual ticket management means constantly confirming the current owner of a ticket by manually checking the 'Assigned To' field. It also means having to update customer contact info across different sheets or CRMs.
Now, your agent manages this automatically. You can use `update_conversation` to reassign tickets and call `get_customer` to verify new details in one go. The system handles the backend updates; you just get confirmation back.
What you can do with this MCP connector
This MCP lets you talk shop with your FreeScout helpdesk using natural language. Instead of logging into the web portal, you tell your AI client exactly what needs doing: check a specific mailbox for new tickets, find out who a customer is, or draft a reply to them. You can list and inspect all incoming mailboxes, keeping track of where every request lands.
Need to talk to team members? Your agent can retrieve user details or even assign conversations by updating their status. When you're done with the ticket, you can create a new conversation from scratch or add an internal note for follow-up. Connecting FreeScout through Vinkius gives your AI client access to this entire catalog of customer service functions, letting you handle tickets and manage user data directly within your agent workspace.
019e389b-7f3c-7067-af47-a2b299b7fcc5 
How FreeScout MCP Works
- 1 Subscribe to this MCP on Vinkius and input your FreeScout API key and base URL.
- 2 Your AI agent uses natural language to identify the required action, such as listing all mailboxes or retrieving a customer's account details.
- 3 The tool executes the function call against your live FreeScout environment and passes back structured data that your agent then presents in plain English.
The bottom line is you control complex helpdesk actions by talking to the system, not by clicking buttons in a browser.
Who Is FreeScout MCP For?
Support Managers and Tier 2 Support Agents who spend too much time switching between internal dashboards and communication tools. If your job involves keeping track of ticket context across multiple systems, this is for you.
Drafting replies to customers based on history and using add_note so the next agent knows what was discussed.
Monitoring mailbox activity by calling list_conversations, then updating ticket ownership using update_conversation when a specialist takes over.
Integrating bug tracking into the support process by retrieving customer details via get_customer to link feedback records outside of FreeScout.
What Changes When You Connect
- Stop copy-pasting ticket data. You can pull full context by calling
get_conversationto see all messages, threads, and status changes in one go. - Never lose track of who did what. Use the agent to call
add_note, documenting internal thoughts or next steps without the customer ever seeing them. - Manage your entire team's workload instantly. You can use
list_usersand thenupdate_conversationto reassign a ticket from an overwhelmed colleague to the right specialist. - Keep customer data clean and current. If a user changes their email, you simply call
update_customerinstead of hunting for it in multiple tabs. - Start a conversation or manage mailboxes with precision. You can use
list_mailboxesfirst to confirm which support queue needs attention before callingcreate_conversation.
Real-World Use Cases
A customer asks about an old bug.
The agent calls get_customer first to verify the account. Then, they call list_threads on the ticket ID to pull the full history of communication regarding the issue before drafting a reply using add_reply.
A new ticket arrives in an unfamiliar queue.
The agent calls list_mailboxes to identify the correct department (e.g., 'Billing'). They then use get_mailbox for that specific inbox, find a new ticket ID, and call update_conversation immediately to assign it to the billing specialist.
A team member leaves suddenly.
The manager calls list_users to check agent roles. They then use get_user on the departing user's profile, and finally update all their assigned tickets via update_conversation to assign them to a backup.
The Tradeoffs
Treating it like a simple text chat
Asking your agent, 'What's wrong with this ticket?' and expecting a summary. The AI doesn't know which mailbox or customer you mean.
→
You have to be specific. First, call list_mailboxes to confirm the queue name. Then, use list_conversations on that exact mailbox ID, followed by get_conversation for the specific ticket.
Mixing up customer and user data
Assuming that every person who sends a message is stored in the main contact list. You'll get an error because they are separate records.
→
You must use list_customers or get_customer for client-facing contacts, and you need to use list_users or get_user only when talking about internal team members.
Updating a ticket without context
Calling update_conversation with just an ID. The system needs to know what you are updating (status, assignee, etc.) or it fails.
→
Always confirm the conversation details first using get_conversation. Then structure your update command: 'Update conversion X by setting status to Resolved and assigning it to Y.'
When It Fits, When It Doesn't
Use this MCP if you need an AI agent to act as a fully integrated support coordinator. That means you frequently need to perform multi-step tasks, like checking customer details (get_customer), retrieving the ticket history (list_threads), and then drafting a reply (add_reply). The core value is connecting data retrieval (GETs) with state manipulation (CREATE/UPDATE). Don't use this if your goal is just reading simple data; for that, standard API calls are fine. You don't need to call create_customer every time you write a reply—you must first confirm the customer exists using list_customers. This MCP handles the full lifecycle: discovery, context retrieval, and action.
Common Questions About FreeScout MCP
How do I list mailboxes with FreeScout MCP? +
You call list_mailboxes. This tool lists every support inbox configured in your system, letting you know exactly which queues (like 'Sales' or 'Support') are active.
Can I update a conversation using the FreeScout MCP? +
Yes. You use update_conversation to change ticket statuses, assignees, and priorities within the system.
What if I need customer details before replying? Use FreeScout MCP. +
You should call get_customer first. This pulls all current profile data for that person, so you can make sure your reply is accurate and uses up-to-date information.
How do I add private notes in FreeScout MCP? +
You use the add_note function. This writes a note visible only to your internal team, keeping it separate from the customer's view of the conversation.
How do I check if the FreeScout MCP connection is working correctly using the `list_users` tool? +
You run list_users to verify the integration. This immediately pulls a list of all active agents and team members, confirming your API key and network access are fully functional.
What is the best way to manage multiple customer records at once using FreeScout MCP? +
Use list_customers first. This allows you to pull a comprehensive roster of all client accounts without manually looking them up one by one, making bulk analysis easy.
When should I use the `delete_conversation` tool within FreeScout MCP? +
You use delete_conversation only when a ticket is confirmed resolved and needs to be removed from the active queue. This keeps your workspace clean and focused.
How do I pull the complete history of messages in FreeScout MCP? +
To get full context, run list_threads. This function retrieves every message sent within a conversation's timeline, ensuring you never miss background details when drafting a response.
How do I reply to a customer conversation using the AI? +
You can use the add_reply tool. Just provide the Conversation ID and the body of your message, and the agent will send it to the customer via FreeScout.
Can I update the status or assignee of a ticket? +
Yes! Use the update_conversation tool. You can change the status (active, pending, closed, spam) or provide an assignee_id to route the ticket to a specific team member.
Is it possible to add internal notes that the customer won't see? +
Absolutely. Use the add_note tool to post internal comments on a conversation. These are visible to your team in FreeScout but are never sent to the customer.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.