# MCP FreeScout [Health: Active]

**Category:** 🎧 Support & Service Management  
**Repository:** https://github.com/verygoodplugins/mcp-freescout  
**GitHub Stars:** 29  
**npm Downloads (last month):** 1173  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mcp-freescout

## Description
FreeScout ticket management with AI-powered analysis, search filters, and structured outputs.

## Tools
Capabilities this server exposes over MCP:

- **freescout_get_ticket** — Fetch and analyze a FreeScout ticket by ID or URL
- **freescout_analyze_ticket** — Analyze a FreeScout ticket to determine issue type, root cause, and suggested solution
- **freescout_add_note** — Add an internal note to a FreeScout ticket
- **freescout_update_ticket** — Update ticket status and/or assignment
- **freescout_create_draft_reply** — Create a draft reply in FreeScout that can be edited before sending
- **freescout_get_ticket_context** — Get ticket context and customer info to help draft personalized replies
- **freescout_search_tickets** — 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_mailboxes** — Get list of available mailboxes

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-freescout": {
    "command": "npx",
    "args": ["@verygoodplugins/mcp-freescout@latest"],
    "env": {
      "FREESCOUT_URL": "",
      "FREESCOUT_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `FREESCOUT_URL`, `FREESCOUT_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What MCP FreeScout MCP server does

MCP FreeScout MCP server gives an MCP-compatible client access to ticket and mailbox operations in a configured FreeScout instance. Agents can retrieve tickets by ID, number, or URL, including conversation threads, then inspect customer and ticket context for follow-up work.

The server also supports operational changes. An agent can add an internal note, change a ticket's status, assign it to a user, search across the FreeScout instance, or list available mailboxes. Status updates support active, pending, closed, and spam values.

Ticket analysis returns structured information about the customer, issue description, classification, code snippets or error messages, reproducibility, likely root cause, and whether the issue appears to be a bug, feature request, or third-party problem.

## How it works

The server runs as a stdio MCP process and communicates with the FreeScout instance configured through environment variables. Its tools accept structured inputs validated with Zod schemas, and analysis and write operations return structured content for more stable client-side handling.

A typical response workflow first calls `freescout_get_ticket_context` to gather customer and ticket details. The agent then composes a reply and calls `freescout_create_draft_reply`. The draft is stored in FreeScout for review and editing rather than being sent automatically. Markdown in the supplied reply is converted to HTML, including headings or emphasis, code, lists, paragraphs, and line breaks.

Search supports filter parameters and relative time values such as `7d` and `24h`. The runtime also retries transient failures with exponential backoff. Successful FreeScout update responses with HTTP 204 are accepted, and update results record the user ID that initiated the change.

## Setup and configuration

MCP FreeScout MCP server requires Node.js 24 or newer and a FreeScout instance with API access enabled. The recommended setup runs the published package with `npx` and supplies these environment variables:

- `FREESCOUT_URL`: URL of the FreeScout instance.
- `FREESCOUT_API_KEY`: API key used to access FreeScout.

Claude Desktop and Cursor can launch the server with `npx @verygoodplugins/mcp-freescout@latest`. The configuration passes the URL and API key in the client’s MCP server definition. A local alternative is to clone the repository, run `npm install`, build with `npm run build`, and launch `dist/index.js` with Node. `npm start` runs the server directly, while `npm run dev` enables development auto-reload.

## Tools and capabilities

Available tools include:

- `freescout_get_ticket`: Fetch ticket details and optionally conversation threads.
- `freescout_analyze_ticket`: Classify a ticket and assess its likely cause and solution.
- `freescout_add_note`: Add an internal team note.
- `freescout_update_ticket`: Change status and/or assignment.
- `freescout_create_draft_reply`: Save an editable, Markdown-to-HTML draft reply with optional recipient fields.
- `freescout_get_ticket_context`: Retrieve customer and ticket context for personalized replies.
- `freescout_search_tickets`: Search tickets using the available filters.
- `freescout_get_mailboxes`: List FreeScout mailboxes.

## Limitations and notes

The process communicates only with the FreeScout instance specified in its environment. Draft replies are saved for review; the provided tool does not send the customer message directly. When recipient fields are omitted, existing conversation recipients are preserved when FreeScout exposes them; passing an empty list clears the corresponding recipient field. The v3 runtime serves both the 2025 legacy handshake and the 2026 stdio protocol from the same server factory.

_Full upstream README: https://allmcps.com/mcp/mcp-freescout/readme_