An MCP (Model Context Protocol) server for FreeScout helpdesk ticket management. This server provides tools to interact with FreeScout tickets, analyze issues, and manage customer responses.
Features
🎫 Ticket Management: Fetch, analyze, and update FreeScout tickets
MCP server for FreeScout ticket management and workflow automation
2026-11-16
星數
—
工具
—
可用率
—
🔍 Intelligent Analysis: Automatically analyze tickets to determine issue type, root cause, and solutions
💬 Draft Responses: Generate customer replies based on ticket analysis
📊 Advanced Search: First-class filter parameters with relative time support ("7d", "24h")
🔒 Type Safety: Full Zod schema validation with structured outputs
🔁 Reliability: Automatic retry logic with exponential backoff for transient failures
⚡ Protocol-ready stdio: A fresh buildServer factory serves both 2025-era and 2026 MCP stdio clients
v3 runtime
Requires Node.js 24 or newer.
Uses @modelcontextprotocol/server 2.x with Zod 4 input schemas.
Serves both the 2025 legacy handshake and the 2026 stdio protocol from the same server factory.
Delivers structuredContent for stable analysis and write-operation results without declaring output schemas.
Accepts FreeScout's successful 204 No Content update responses and records the user ID that initiated a ticket update.
Installation
Prerequisites
Node.js 24 or higher
FreeScout instance with API access enabled
Quick Start (Recommended)
The easiest way to use this MCP server is with npx:
With Claude Desktop
Add this to your Claude Desktop settings (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
Example: Fetching a FreeScout ticket with conversation threads
freescout_analyze_ticket
Analyze a ticket to determine issue type, root cause, and suggested solutions.
Parameters:
ticket (required): Ticket ID, number, or FreeScout URL
Natural Language Examples:
"Analyze ticket #12345"
"What kind of issue is ticket 34811?"
"Can you analyze this ticket and tell me if it's a bug?"
"Examine ticket #12345 and determine the root cause"
"Is this ticket a bug or feature request?"
Returns:
Customer information
Issue description and classification
Code snippets and error messages
Reproducibility status
Root cause analysis
Bug vs feature request vs third-party issue determination
Example: Intelligent ticket analysis with issue classification
freescout_add_note
Add an internal note to a ticket for team communication.
Parameters:
ticket (required): Ticket ID, number, or FreeScout URL
note (required): The note content
userId (optional): User ID for the note (defaults to env setting)
Natural Language Examples:
"Add a note to ticket #12345 saying 'Reproduced on staging'"
"Leave an internal note on this ticket"
"Add a team note: 'Customer confirmed fix works'"
"Note on ticket 34811: 'Escalating to development team'"
"Add internal documentation to this ticket"
freescout_update_ticket
Update ticket status and/or assignment.
Parameters:
ticket (required): Ticket ID, number, or FreeScout URL
status (optional): New status ('active', 'pending', 'closed', 'spam')
assignTo (optional): User ID to assign the ticket to
Natural Language Examples:
"Close ticket #12345"
"Mark ticket 34811 as pending"
"Assign this ticket to user ID 2"
"Set ticket status to active"
"Update ticket #12345 status to closed and assign to user 1"
freescout_create_draft_reply
Create a draft reply in FreeScout that can be edited before sending. This tool lets the LLM generate the reply content and saves it directly to FreeScout as a draft. Automatically converts Markdown formatting to HTML for proper display in FreeScout.
Parameters:
ticket (required): Ticket ID, number, or FreeScout URL
replyText (required): The draft reply content (generated by the LLM, supports Markdown formatting)
userId (optional): User ID creating the draft (defaults to env setting)
to (optional): List of TO recipients. Omit to preserve existing recipients; pass [] to clear.
cc (optional): List of CC recipients. Omit to preserve existing recipients; pass [] to clear.
bcc (optional): List of BCC recipients. Omit to preserve existing recipients; pass [] to clear.
Natural Language Examples:
"Create a draft reply for ticket #12345"
"Draft a customer response for this ticket"
"Generate and save a draft reply explaining the fix"
"Write a draft response to the customer for ticket 34811"
"Create a draft reply thanking the customer and explaining the solution"
If recipient fields are omitted, the server preserves the current conversation recipients from FreeScout when available. If FreeScout does not expose existing to recipients on the conversation, its normal default customer recipient behavior is preserved.
Get a list of all available mailboxes in your FreeScout instance.
Parameters:
None
Natural Language Examples:
"Show me all available mailboxes"
"List the mailboxes in FreeScout"
"What mailboxes are configured?"
"Get mailbox information"
Workflow Examples
Basic Ticket Analysis
// Analyze a ticket to understand the issue
await mcp.callTool('freescout_analyze_ticket', {
ticket: '12345',
});
Complete Ticket Response Workflow
// 1. Analyze the ticket to understand the issue
const analysis = await mcp.callTool('freescout_analyze_ticket', {
ticket: '12345',
});
// 2. Get ticket context for personalized reply
const context = await mcp.callTool('freescout_get_ticket_context', {
ticket: '12345',
});
// 3. Create a draft reply directly in FreeScout
await mcp.callTool('freescout_create_draft_reply', {
ticket: '12345',
replyText: `Hi ${context.customer.name},
Thank you for reaching out! Based on my analysis, I can see that ${analysis.issueDescription}.
Here's what I found:
1. **Issue Type**: ${analysis.isBug ? 'Bug' : 'Configuration/Feature Request'}
2. **Root Cause**: ${analysis.rootCause || 'Under investigation'}
I'll look into this and get back to you shortly with a solution.
Best regards,
[Your name]`,
cc: ['[email protected]'],
});
// 4. Update ticket status and assignment
await mcp.callTool('freescout_update_ticket', {
ticket: '12345',
status: 'active',
assignTo: 1,
});
// 5. Add an internal note with findings
await mcp.callTool('freescout_add_note', {
ticket: '12345',
note: `Analysis complete:
- Is Bug: ${analysis.isBug}
- Third-party Issue: ${analysis.isThirdPartyIssue}
- Root Cause: ${analysis.rootCause}`,
});
Draft Reply Workflow
// 1. Get ticket context for personalized reply
const context = await mcp.callTool('freescout_get_ticket_context', {
ticket: '34811',
});
// 2. Create draft reply in FreeScout (LLM crafts the content)
await mcp.callTool('freescout_create_draft_reply', {
ticket: '34811',
replyText: `Hi ${context.customer.name},
Thank you for reporting the HighLevel OAuth authorization issue! Your experience with the EngageBay LiveChat plugin conflict has been really valuable.
Based on what we learned from your case, I've added a new plugin conflict detection system to WP Fusion. In the next update (v3.46.7), users will see:
🔍 **Plugin Conflict Detection**
- Automatic detection of known conflicting plugins
- Warning messages before HighLevel authorization
- Clear guidance when conflicts are detected
This should prevent the confusion you experienced and help other users avoid similar issues.
The update should be available within the next few weeks. Thanks for your patience and for helping us improve the plugin!
Best regards,
Jack`,
to: ['[email protected]'],
cc: ['[email protected]'],
});
// The draft is now saved in FreeScout and can be reviewed/edited before sending
Handling Non-Bug Issues
// For third-party issues or feature requests
const reply = await mcp.callTool('freescout_create_draft_reply', {
ticket: '12345',
replyText: 'This is a limitation of the Elementor plugin that we cannot override.',
});
Architecture
Components
FreeScout API Client (freescout-api.ts)
Handles all API communication with FreeScout
Manages authentication and request formatting
Provides ticket parsing utilities
Ticket Analyzer (ticket-analyzer.ts)
Intelligent ticket content analysis
Issue classification (bug vs feature vs configuration)
Code snippet and error extraction
Root cause determination
MCP Server (index.ts)
Tool registration and request handling
Fresh server factory for each stdio connection
Response formatting and error handling
Data Flow
MCP client (2025 or 2026) → stdio entry → buildServer → FreeScout API
↓
Ticket analysis
↓
Response to client
Development
Running in Development Mode
npm run dev
Running Tests
npm test
Linting
npm run lint
Building for Production
npm run build
Configuration
Required Environment Variables
Variable
Description
Example
FREESCOUT_URL
Your FreeScout instance URL
https://support.example.com
FREESCOUT_API_KEY
FreeScout API key
your-api-key-here
Optional Environment Variables
Variable
Description
Default
FREESCOUT_DEFAULT_USER_ID
Default user ID for assignments
1
Advanced Configuration Example
For more control, you can specify additional environment variables: