Log inSubmit server
MCP FreeScout logo

MCP FreeScout

Connects AI agents to FreeScout for ticket retrieval, analysis, search, updates, notes, and draft replies.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP FreeScout

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-freescout": {
      "command": "npx",
      "args": [
        "@verygoodplugins/mcp-freescout@latest"
      ],
      "env": {
        "FREESCOUT_URL": "YOUR_VALUE_HERE",
        "FREESCOUT_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 8 tools correctly (2d ago).

Overview

MCP FreeScout MCP server connects AI agents to a FreeScout helpdesk over the MCP stdio protocol. It supports ticket retrieval, issue analysis, filtered search, mailbox listing, internal notes, status or assignment changes, and draft replies. Draft content can use Markdown, which the server converts to HTML before saving it in FreeScout. Reach for it when support teams need agent-assisted triage and response drafting while keeping final customer communication in FreeScout.

Use cases

  • Analyze incoming tickets for issue type and root cause
  • Search FreeScout tickets using filters and relative dates
  • Draft personalized customer replies for review
  • Update ticket status and assignment
  • Add internal notes for support teams

Key features

  • Ticket retrieval with conversation threads
  • Issue classification and root-cause analysis
  • Filtered ticket search with relative time values
  • Internal notes, status updates, and assignment changes
  • Draft replies with Markdown-to-HTML conversion
  • Structured outputs with retry handling

Tools8

What MCP FreeScout lets your agent do. Expand a tool for its parameters.

Verified live~1.2k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 45d

What it can do

From the 8 tools this server returned when we ran it.

Makes network requests · 1Read-only tools · 8
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age445 days
Maintainers2

Observed 2026-10-21 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · @verygoodplugins/mcp-freescout@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars29Stargazers on the source repository.
npm downloads1.2kPackage downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed8Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP FreeScout works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP FreeScout

MCP FreeScout is an MCP server that connects AI agents to a FreeScout helpdesk through stdio. Its main tools fetch, analyze, search, update, and add notes to tickets, create draft replies, retrieve ticket context, and list mailboxes. It uses FreeScout URL and API key environment settings to reach the configured instance.

Install it with Node.js 24 or newer by configuring your MCP client to run `npx @verygoodplugins/mcp-freescout@latest`. Provide `FREESCOUT_URL` and `FREESCOUT_API_KEY` in the server environment. You can also clone the repository, install dependencies, build it, and run the generated `dist/index.js` file.

Yes, MCP FreeScout works with Cursor through its MCP settings. Add the server command and package arguments to Cursor’s settings or `~/.cursor/mcp.json`, then provide the FreeScout URL and API key as environment variables.

No, it creates a draft reply rather than sending one automatically. The agent saves generated content to FreeScout, where a user can review and edit it before sending. Markdown in the draft is converted to HTML for display.

It needs a FreeScout instance with API access enabled, its URL, and an API key. Set `FREESCOUT_URL` and `FREESCOUT_API_KEY` in the MCP client configuration used to launch the stdio process.

Related MCP servers

All in Support & Service Management All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP FreeScout AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-freescout?style=directory)](https://allmcps.com/mcp/mcp-freescout)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-freescout"><img src="https://allmcps.com/api/badge/mcp-freescout?style=directory" alt="MCP FreeScout on AllMCPs" /></a>