MCP Atlassian vs STEADYWRK Field Service Dispatch
A side-by-side look at the MCP Atlassian and STEADYWRK Field Service Dispatch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
STEADYWRK Field Service DispatchSupport & Service Management · Remote HTTP/SSEField service dispatch: instant quotes, tracked work orders, public evals. steadywrk.app43FairAuth: no auth requiredVerdict: choose MCP Atlassian for support & service management work as a local process; choose STEADYWRK Field Service Dispatch for support & service management over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
SChoose STEADYWRK Field Service Dispatch when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S STEADYWRK Field Service Dispatch | |
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 49/100 · Fair | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | JIRA_URLJIRA_USERNAMEJIRA_API_TOKENJIRA_PERSONAL_TOKENCONFLUENCE_URLCONFLUENCE_USERNAMECONFLUENCE_API_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6,035 | — |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCP Atlassian | View STEADYWRK Field Service Dispatch |
Tools & capabilities
MCP Atlassian tools
No tool names declared yet. Check the project README from the listing page.
STEADYWRK Field Service Dispatch 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 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"
}
}
}
}
STEADYWRK Field Service Dispatch
{
"mcpServers": {
"steadywrk-field-service-dispatch": {
"url": "https://steadywrk.app/developers/mcp"
}
}
}
Frequently asked questions
MCP Atlassian is categorized under Support & Service Management and uses a local stdio subprocess. STEADYWRK Field Service Dispatch belongs to Support & Service Management and uses a remote HTTP/SSE transport. Pick MCP Atlassian for support & service management work and STEADYWRK Field Service Dispatch 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 Atlassian is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. STEADYWRK Field Service Dispatch has no declared pricing — check the project's own site. Auth: no auth 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 sooperset-mcp-atlassian and steadywrk-field-service-dispatch as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Atlassian has a quality signal of 49/100 (Fair) with 4 views, 0 installs and 6,035 GitHub stars. STEADYWRK Field Service Dispatch has 43/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.