# Reported issues for MCP FreeScout

Pod holds 6 of 6 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [MCP FreeScout](/mcp/mcp-freescout).

## Most discussed

### feat: add FreeScout tag support to MCP tools and docs

### Problem

Please add or restore FreeScout tag support in the official `mcp-freescout` server and document it in the README / published package docs.

FreeScout’s official API already supports tag operations, including:

- `GET /api/tags` for listing global tags or tags on a conversation
- `PUT /api/conversations/{conversationId}/tags` for replacing a conversation’s full tag list
- `tag` as a conversation search filter

The Tags module docs also describe tags as a core way to categorize conver

[Read the thread](https://github.com/verygoodplugins/mcp-freescout/issues/84) · 2026-08-17 · open · external user · 0 comments

### freescout_update_ticket reports isError on every successful update (204 No Content)

## Problem

`PUT /api/conversations/{id}` answers `204 No Content` with an empty body, while `FreeScoutAPI.request` always calls `response.json()`. The parse throws, so `freescout_update_ticket` returns an error even though the update was applied:

```json
{"content":[{"type":"text","text":"Unexpected end of JSON input"}],"isError":true}
```

Every successful status or assignment change looks like a failure to the client, which is worse than a plain error: an assistant driving the tool will norm

[Read the thread](https://github.com/verygoodplugins/mcp-freescout/issues/76) · 2026-08-13 · closed · outside contributor · 1 comment

### Tools declaring outputSchema are unusable in Claude Code (draft-07 rejected)

## Problem

Four tools cannot be called at all from Claude Code. The client rejects them before the request reaches the server:

```
Error: Tool "freescout_create_draft_reply" has an invalid outputSchema:
JSON Schema declares an unsupported dialect ("$schema": "http://json-schema.org/draft-07/schema#").
The default validator supports JSON Schema 2020-12 only.
```

Affected tools, i.e. every tool that still declares `outputSchema` in `dist/index.js` (v2.1.1):

- `freescout_create_draft_reply`
- `

[Read the thread](https://github.com/verygoodplugins/mcp-freescout/issues/73) · 2026-08-13 · closed · outside contributor · 1 comment

### Feature request: support userId parameter in freescout_update_ticket

**Summary**
The freescout_update_ticket tool does not currently support specifying which user performs the status change. When a status
update is triggered via the tool, FreeScout logs the action under a default user rather than the intended agent, the activity log shows something like "User X marked as Active" instead of the agent who actually performed the action.

**Expected behavior**
An optional userId parameter in freescout_update_ticket would allow the status change to be attributed to th

[Read the thread](https://github.com/verygoodplugins/mcp-freescout/issues/48) · 2026-04-24 · closed · external user · 4 comments

### Feature request: support to, cc and bcc fields in freescout_create_draft_reply

First of all, great work on this MCP, it integrates perfectly with FreeScout and has become an essential part of my workflow with AI agents.

Currently, freescout_create_draft_reply does not expose any parameters to control the recipients of the draft reply. The draft is created with only the primary customer email as the recipient, ignoring any CC addresses present in the original conversation thread.

This means that when I use an AI agent to prepare draft replies, I have to manually fix the r

[Read the thread](https://github.com/verygoodplugins/mcp-freescout/issues/30) · 2026-04-22 · closed · external user · 2 comments

### Windows Readme instruction compatibility

Windows can convert forward slash `/` to a backslash `\` in config parsing. 
The package name @verygoodplugins/mcp-freescout becomes @verygoodplugins\mcp-freescout which npm rejects.
I've noticed other MCP servers use this Claude config approach to avoid this:
```
"freescout": {
  "command": "npx",
  "args": [
    "-y",
    "@verygoodplugins/mcp-freescout@latest"
  ],
  "env": {
    "FREESCOUT_API_KEY": "your-key",
    "FREESCOUT_URL": "your-url"
  }
}

```

I can confirm the current config brea

[Read the thread](https://github.com/verygoodplugins/mcp-freescout/issues/5) · 2025-12-18 · closed · external user · 1 comment

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/verygoodplugins/mcp-freescout/issues).