MCP FreeScout vs MCP Atlassian
A side-by-side look at the MCP FreeScout and MCP Atlassian MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP FreeScout for support & service management work as a local process; choose MCP Atlassian for support & service management as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP FreeScout when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
FREESCOUT_URL, FREESCOUT_API_KEY. - You want tools like
freescout_get_ticket, freescout_analyze_ticket, freescout_add_note.
Choose MCP Atlassian when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
JIRA_URL, JIRA_USERNAME, JIRA_API_TOKEN, JIRA_PERSONAL_TOKEN, CONFLUENCE_URL, CONFLUENCE_USERNAME, CONFLUENCE_API_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 65/100 · Great | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | FREESCOUT_URLFREESCOUT_API_KEY | JIRA_URLJIRA_USERNAMEJIRA_API_TOKENJIRA_PERSONAL_TOKENCONFLUENCE_URLCONFLUENCE_USERNAMECONFLUENCE_API_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 29 | 6,030 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 8 | Not listed |
| Full listing | View MCP FreeScout | View MCP Atlassian |
Tools & capabilities
MCP FreeScout tools 8
freescout_get_ticketFetch and analyze a FreeScout ticket by ID or URLfreescout_analyze_ticketAnalyze a FreeScout ticket to determine issue type, root cause, and suggested solutionfreescout_add_noteAdd an internal note to a FreeScout ticketfreescout_update_ticketUpdate ticket status and/or assignmentfreescout_create_draft_replyCreate a draft reply in FreeScout that can be edited before sendingfreescout_get_ticket_contextGet ticket context and customer info to help draft personalized repliesfreescout_search_ticketsSearch 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_mailboxesGet list of available mailboxes
MCP Atlassian tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP FreeScout
{
"mcpServers": {
"mcp-freescout": {
"command": "npx",
"args": [
"@verygoodplugins/mcp-freescout@latest"
],
"env": {
"FREESCOUT_URL": "YOUR_FREESCOUT_URL_HERE",
"FREESCOUT_API_KEY": "YOUR_FREESCOUT_API_KEY_HERE"
}
}
}
}
MCP Atlassian
{
"mcpServers": {
"sooperset-mcp-atlassian": {
"command": "uvx",
"args": [
"mcp-atlassian"
],
"env": {
"JIRA_URL": "YOUR_JIRA_URL_HERE",
"JIRA_USERNAME": "YOUR_JIRA_USERNAME_HERE",
"JIRA_API_TOKEN": "YOUR_JIRA_API_TOKEN_HERE",
"JIRA_PERSONAL_TOKEN": "YOUR_JIRA_PERSONAL_TOKEN_HERE",
"CONFLUENCE_URL": "YOUR_CONFLUENCE_URL_HERE",
"CONFLUENCE_USERNAME": "YOUR_CONFLUENCE_USERNAME_HERE",
"CONFLUENCE_API_TOKEN": "YOUR_CONFLUENCE_API_TOKEN_HERE"
}
}
}
}
Frequently asked questions
MCP FreeScout is categorized under Support & Service Management and uses a local stdio subprocess. MCP Atlassian belongs to Support & Service Management and uses a local stdio subprocess. Pick MCP FreeScout for support & service management work and MCP Atlassian for support & service management.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP FreeScout has no declared pricing — check the project's own site. MCP Atlassian is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-freescout and sooperset-mcp-atlassian as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP FreeScout has a quality signal of 65/100 (Great) with 1 views, 0 installs and 29 GitHub stars. MCP Atlassian has 48/100 (Fair) with 2 views, 0 installs and 6,030 GitHub stars.