FreeScout MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FREESCOUT_URL | Yes | Your FreeScout instance URL | |
| FREESCOUT_API_KEY | Yes | FreeScout API key | |
| FREESCOUT_DEFAULT_USER_ID | No | Default user ID for assignments | 1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| freescout_get_ticketB | Fetch and analyze a FreeScout ticket by ID or URL |
| freescout_analyze_ticketA | Analyze a FreeScout ticket to determine issue type, root cause, and suggested solution |
| freescout_add_noteB | Add an internal note to a FreeScout ticket |
| freescout_update_ticketC | Update ticket status and/or assignment |
| freescout_create_draft_replyB | Create a draft reply in FreeScout that can be edited before sending |
| freescout_get_ticket_contextB | Get ticket context and customer info to help draft personalized replies |
| freescout_search_ticketsA | Search for FreeScout tickets with explicit filter parameters. Text search is subject-only (FreeScout has no message-body full-text search): use subject (or its alias textSearch) to match the conversation subject, customerEmail to filter by the customer, and number to look up a single ticket. Use assignee: "unassigned" for unassigned tickets, or assignee: number for a specific user. Supports relative time filters like "7d", "24h". Use includeLastMessage: true to get a preview of the most recent message for each ticket. |
| freescout_get_mailboxesA | Get list of available mailboxes |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools map to single distinct actions, but get_ticket, analyze_ticket, and get_ticket_context all center on reading/understanding a single ticket. The get_ticket description's 'Fetch and analyze' wording blurs its boundary with analyze_ticket, so descriptions must be read closely to avoid misselection.
All tools use the freescout_ prefix with a clear verb_noun structure: get_ticket, add_note, update_ticket, create_draft_reply, search_tickets, get_mailboxes. The verbs and nouns are consistent and predictable, with no mixed casing or irregular naming patterns.
Eight tools is an appropriate size for a helpdesk assistant server. Each tool covers a distinct stage of the ticket workflow without ballooning into unnecessary operations or feeling too thin for the intended scope.
The set covers lookup, search, analysis, status/assignment updates, internal notes, context gathering, and draft replies, which is enough for common support ticket workflows. Obvious gaps like sending replies directly or deleting tickets are absent, but those are reasonable boundary choices for an assistant that drafts rather than sends.