Jira MCP vs Swsd
A side-by-side look at the Jira MCP and Swsd MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Jira MCP for support & service management work over a hosted endpoint; choose Swsd 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 Jira MCP when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
ATLASSIAN_HOST, ATLASSIAN_EMAIL, ATLASSIAN_TOKEN, ENABLED_TOOLS. - You want tools like
jira_get_issue, jira_create_issue, jira_create_child_issue.
Choose Swsd when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SWSD_TOKEN, SWSD_BASE_URL, SWSD_PROFILE.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 57/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | ATLASSIAN_HOSTATLASSIAN_EMAILATLASSIAN_TOKENENABLED_TOOLS | SWSD_TOKENSWSD_BASE_URLSWSD_PROFILE |
| Verified owner | Community listing | Community listing |
| GitHub stars | 97 | 4 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 21 | Not listed |
| Full listing | View Jira MCP | View Swsd |
Tools & capabilities
Jira MCP tools 21
jira_get_issueRetrieve detailed information about a specific issue including status, assignee, description, subtasks, and available transitionsjira_create_issueCreate a new issue with specified details (returns key, ID, and URL)jira_create_child_issueCreate a child issue (sub-task) linked to a parent issuejira_update_issueModify an existing issue's details (supports partial updates)jira_list_issue_typesList all available issue types in a project with their IDs, names, and descriptionsjira_search_issueSearch for issues using JQL (Jira Query Language) with customizable fields and expand optionsjira_list_sprintsList all active and future sprints for a specific board or projectjira_get_sprintRetrieve detailed information about a specific sprint by its IDjira_get_active_sprintGet the currently active sprint for a given board or projectjira_search_sprint_by_nameSearch for sprints by name with exact or partial matchingjira_list_statusesRetrieve all available issue status IDs and their names for a projectjira_transition_issueTransition an issue through its workflow using a valid transition ID- +9 more on the listing page
Swsd 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.
Jira MCP
{
"mcpServers": {
"nguyenvanduocit-jira-mcp": {
"url": "http://localhost:3000/mcp"
}
}
}
Swsd
{
"mcpServers": {
"swsd": {
"command": "npx",
"args": [
"-y",
"swsd-mcp"
],
"env": {
"SWSD_TOKEN": "YOUR_SWSD_TOKEN_HERE",
"SWSD_BASE_URL": "YOUR_SWSD_BASE_URL_HERE",
"SWSD_PROFILE": "YOUR_SWSD_PROFILE_HERE"
}
}
}
}
Frequently asked questions
Jira MCP is categorized under Support & Service Management and uses a remote HTTP/SSE transport. Swsd belongs to Support & Service Management and uses a local stdio subprocess. Pick Jira MCP for support & service management work and Swsd 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.
Jira MCP is listed as free. Auth: api key required. Swsd has no declared pricing — check the project's own site. 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 nguyenvanduocit-jira-mcp and swsd as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Jira MCP has a quality signal of 57/100 (Good) with 3 views, 0 installs and 97 GitHub stars. Swsd has 45/100 (Fair) with 0 views, 0 installs and 4 GitHub stars.