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 conversations.
Proposed solution
Proposed MCP tools
freescout_list_tags
List all FreeScout tags, or list tags currently applied to a specific ticket/conversation.
Suggested parameters:
ticket optional: ticket ID, ticket number, or FreeScout URL
page optional
pageSize optional, max 100
freescout_update_ticket_tags
Add, remove, replace, or clear tags for a ticket/conversation.
Suggested parameters:
ticket required
tags required array of tag names
mode required: add, remove, or replace
Implementation note: FreeScout’s API replaces the full tag list, so add and remove should first read existing tags, merge/remove locally, then send the resulting full list. replace should send exactly the supplied list, and replace with [] should clear all tags.
Why this matters
Tags are a common FreeScout workflow for triage, escalation, reporting, automation, and custom folders. Without MCP tag support, agents can fetch and update tickets but cannot perform a major part of day-to-day support organization.
References
- FreeScout API docs include a
Tags section with list/update endpoints.
- FreeScout’s Tags module describes tags as a way to categorize conversations.
- A prior fork implementation exists in
Nels2/mcp-freescout around freescout_list_tags and freescout_update_ticket_tags, though it may need to be adapted to the current v3 MCP runtime.
Alternatives considered
No response
Additional context
No response
Problem
Please add or restore FreeScout tag support in the official
mcp-freescoutserver and document it in the README / published package docs.FreeScout’s official API already supports tag operations, including:
GET /api/tagsfor listing global tags or tags on a conversationPUT /api/conversations/{conversationId}/tagsfor replacing a conversation’s full tag listtagas a conversation search filterThe Tags module docs also describe tags as a core way to categorize conversations.
Proposed solution
Proposed MCP tools
freescout_list_tagsList all FreeScout tags, or list tags currently applied to a specific ticket/conversation.
Suggested parameters:
ticketoptional: ticket ID, ticket number, or FreeScout URLpageoptionalpageSizeoptional, max 100freescout_update_ticket_tagsAdd, remove, replace, or clear tags for a ticket/conversation.
Suggested parameters:
ticketrequiredtagsrequired array of tag namesmoderequired:add,remove, orreplaceImplementation note: FreeScout’s API replaces the full tag list, so
addandremoveshould first read existing tags, merge/remove locally, then send the resulting full list.replaceshould send exactly the supplied list, andreplacewith[]should clear all tags.Why this matters
Tags are a common FreeScout workflow for triage, escalation, reporting, automation, and custom folders. Without MCP tag support, agents can fetch and update tickets but cannot perform a major part of day-to-day support organization.
References
Tagssection with list/update endpoints.Nels2/mcp-freescoutaroundfreescout_list_tagsandfreescout_update_ticket_tags, though it may need to be adapted to the current v3 MCP runtime.Alternatives considered
No response
Additional context
No response