MCP Server Atlassian Jira vs N8n MCP Community
A side-by-side look at the MCP Server Atlassian Jira and N8n MCP Community MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server Atlassian Jira for workplace & productivity work as a local process; choose N8n MCP Community for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Server Atlassian Jira when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
ATLASSIAN_SITE_NAME, ATLASSIAN_USER_EMAIL, ATLASSIAN_API_TOKEN. - You want tools like
jira_get, jira_post, jira_put.
Choose N8n MCP Community when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
N8N_API_URL, N8N_API_KEY. - You want tools like
n8n_workflows_list, n8n_workflows_get, n8n_workflows_create.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 65/100 · Great | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | Free | Free |
| Required env vars | ATLASSIAN_SITE_NAMEATLASSIAN_USER_EMAILATLASSIAN_API_TOKEN | N8N_API_URLN8N_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 77 | 1 |
| Directory activity | 5 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 5 | 44 |
| Full listing | View MCP Server Atlassian Jira | View N8n MCP Community |
Tools & capabilities
MCP Server Atlassian Jira tools 5
jira_getRead any Jira data. Returns TOON format by default (30-60% fewer tokens than JSON). **IMPORTANT - Cost Optimization:** - ALWAYS use `jq` param to filter response fields. Unfiltered responses are very expensive! - Use `maxResults` query param to restrict result count (e.g., `maxResults: "5"`) - If unsure about available fields, first fetch ONE item with `maxResults: "1"` and NO jq filter to explore the schema, then use jq in subsequent calls **Schema Discovery Pattern:** 1. First call: `path: "/rest/api/3/search/jql", queryParams: {"maxResults": "1", "jql": "project=PROJ"}` (no jq) - explore available fields 2. Then use: `jq: "issues[*].{key: key, summary: fields.summary, status: fields.status.name}"` - extract only what you need **Output format:** TOON (default, token-efficient) or JSON (`outputFormat: "json"`) **Common paths:** - `/rest/api/3/project` - list all projects - `/rest/api/3/project/{projectKeyOrId}` - get project details - `/rest/api/3/search/jql` - search issues with JQL (use `jql` query param). NOTE: `/rest/api/3/search` is deprecated! - `/rest/api/3/issue/{issueIdOrKey}` - get issue details - `/rest/api/3/issue/{issueIdOrKey}/comment` - list issue comments - `/rest/api/3/issue/{issueIdOrKey}/worklog` - list issue worklogs - `/rest/api/3/issue/{issueIdOrKey}/transitions` - get available transitions - `/rest/api/3/user/search` - search users (use `query` param) - `/rest/api/3/status` - list all statuses - `/rest/api/3/issuetype` - list issue types - `/rest/api/3/priority` - list priorities **JQ examples:** `issues[*].key`, `issues[0]`, `issues[*].{key: key, summary: fields.summary}` **Example JQL queries:** `project=PROJ`, `assignee=currentUser()`, `status="In Progress"`, `created >= -7d` API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/jira_postCreate Jira resources. Returns TOON format by default (token-efficient). **IMPORTANT - Cost Optimization:** - Use `jq` param to extract only needed fields from response (e.g., `jq: "{key: key, id: id}"`) - Unfiltered responses include all metadata and are expensive! **Output format:** TOON (default) or JSON (`outputFormat: "json"`) **Common operations:** 1. **Create issue:** `/rest/api/3/issue` body: `{"fields": {"project": {"key": "PROJ"}, "summary": "Issue title", "issuetype": {"name": "Task"}, "description": {"type": "doc", "version": 1, "content": [{"type": "paragraph", "content": [{"type": "text", "text": "Description"}]}]}}}` 2. **Add comment:** `/rest/api/3/issue/{issueIdOrKey}/comment` body: `{"body": {"type": "doc", "version": 1, "content": [{"type": "paragraph", "content": [{"type": "text", "text": "Comment text"}]}]}}` 3. **Add worklog:** `/rest/api/3/issue/{issueIdOrKey}/worklog` body: `{"timeSpentSeconds": 3600, "comment": {"type": "doc", "version": 1, "content": [{"type": "paragraph", "content": [{"type": "text", "text": "Work done"}]}]}}` 4. **Transition issue:** `/rest/api/3/issue/{issueIdOrKey}/transitions` body: `{"transition": {"id": "31"}}` 5. **Add attachment:** `/rest/api/3/issue/{issueIdOrKey}/attachments` Note: Requires multipart form data (complex - use Jira UI for attachments) API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/jira_putReplace Jira resources (full update). Returns TOON format by default. **IMPORTANT - Cost Optimization:** Use `jq` param to extract only needed fields from response **Output format:** TOON (default) or JSON (`outputFormat: "json"`) **Common operations:** 1. **Update issue (full):** `/rest/api/3/issue/{issueIdOrKey}` body: `{"fields": {"summary": "New title", "description": {...}, "assignee": {"accountId": "..."}}}` 2. **Update project:** `/rest/api/3/project/{projectIdOrKey}` body: `{"name": "New Project Name", "description": "Updated description"}` 3. **Set issue property:** `/rest/api/3/issue/{issueIdOrKey}/properties/{propertyKey}` body: `{"value": "property value"}` Note: PUT replaces the entire resource. For partial updates, prefer PATCH. API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/jira_patchPartially update Jira resources. Returns TOON format by default. **IMPORTANT - Cost Optimization:** Use `jq` param to filter response fields. **Output format:** TOON (default) or JSON (`outputFormat: "json"`) **Common operations:** 1. **Update issue fields:** `/rest/api/3/issue/{issueIdOrKey}` body: `{"fields": {"summary": "Updated title"}}` (only updates specified fields) 2. **Update comment:** `/rest/api/3/issue/{issueIdOrKey}/comment/{commentId}` body: `{"body": {"type": "doc", "version": 1, "content": [{"type": "paragraph", "content": [{"type": "text", "text": "Updated comment"}]}]}}` 3. **Update worklog:** `/rest/api/3/issue/{issueIdOrKey}/worklog/{worklogId}` body: `{"timeSpentSeconds": 7200}` Note: PATCH only updates the fields you specify, leaving others unchanged. API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/jira_deleteDelete Jira resources. Returns TOON format by default. **Output format:** TOON (default) or JSON (`outputFormat: "json"`) **Common operations:** 1. **Delete issue:** `/rest/api/3/issue/{issueIdOrKey}` Query param: `deleteSubtasks=true` to delete subtasks 2. **Delete comment:** `/rest/api/3/issue/{issueIdOrKey}/comment/{commentId}` 3. **Delete worklog:** `/rest/api/3/issue/{issueIdOrKey}/worklog/{worklogId}` 4. **Delete attachment:** `/rest/api/3/attachment/{attachmentId}` 5. **Remove watcher:** `/rest/api/3/issue/{issueIdOrKey}/watchers` Query param: `accountId={accountId}` Note: Most DELETE endpoints return 204 No Content on success. API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/
N8n MCP Community tools 44
n8n_workflows_listList one Public API page of workflows visible to the configured API key. Use n8n_search_workflows for substring matching or n8n_workflows_get for a known ID. Omit cursor for page one. active, tags, and name are combined upstream; keep those filters and excludePinnedData unchanged when passing nextCursor. limit sizes only that page, and the tool never auto-paginates. Requires workflow-list permission; returns projected workflows and nextCursor, never pin/static values.n8n_workflows_getGet one current workflow for inspection or reviewed editing. workflowId is the stable ID returned by n8n_workflows_list or create, not a workflow name or version ID. Use n8n_workflows_get_version for history. excludePinnedData changes only the upstream request and the pinDataPresent/staticDataPresent flags; pinned values are withheld whether true or false. Requires permission to read the target; returns structure, state, settings, and presence flags.n8n_workflows_createCreate and persist one workflow as an additive write without activating its triggers. name, nodes, and connections define a new record; nodes and connections must form one complete graph, while omitting settings uses an empty object. Optional pinData, staticData, description, and nodeGroups are forwarded only when supplied. Use n8n_workflows_update for an existing workflow and activate for triggers. Requires write or unsafe mode plus create permission; returns the validated projection without pin/static values.n8n_workflows_updateUpdate selected top-level fields through a non-atomic full PUT. workflowId selects the current record; copy expectedVersionId from its latest read, and supply at least one writable field. The version must match both pre-write reads. Omitted fields are preserved, but each supplied array or object replaces that whole field. Use n8n_update_node for one node property and n8n_workflows_update_tags for tags. Requires write/unsafe mode plus read and update permission; returns the confirmed projection.n8n_update_nodeUpdate one path on one node while preserving sibling data. workflowId selects the current workflow, nodeId selects exactly one node inside it, and path selects the mutable field whose contract validates value. Copy expectedVersionId from the latest workflow read and set acknowledgeNonAtomicRisk=true; both guards are required before the full PUT. Use n8n_workflows_update for top-level or multi-node edits. Requires write/unsafe mode plus read and update permission; returns the changed path and residual race risk.n8n_workflows_deletePermanently delete one workflow and its saved definition. workflowId must be the current stable ID from n8n_workflows_list or get; a name or version ID is not accepted. Use n8n_workflows_archive for reversible removal and n8n_workflows_get for inspection. This action has no rollback or transfer. Requires unsafe mode plus delete permission; returns the request-bound workflowId with deleted=true.n8n_workflows_activateActivate one workflow so production triggers can accept future events; this does not execute it now. workflowId must be the current stable ID from n8n_workflows_list or get, not a name or version ID. Review the workflow first; use n8n_workflows_deactivate to stop future triggers. Requires unsafe mode plus activation permission; returns target-validated active state metadata.n8n_workflows_deactivateDeactivate one workflow's future production triggers without deleting saved data or stopping runs already in progress. workflowId must be the current stable ID from n8n_workflows_list or get, not a name or version ID. Use n8n_workflows_activate to reverse the state or archive for lifecycle removal. Requires unsafe mode plus deactivation permission; returns target-validated inactive state metadata.n8n_workflows_get_versionGet one retained workflow snapshot. workflowId is the stable workflow ID; versionId is that workflow's separate retained-version ID. Do not swap them or pass a workflow name. Use n8n_workflows_get for current state or n8n_workflows_diff for comparison. Both returned IDs must match the selectors; a missing endpoint and a pruned version share an explicit ambiguous 404 outcome. Requires history-read permission; returns validated nodes and connections subject to retention.n8n_workflows_get_tagsList tags currently assigned to one workflow. workflowId selects the workflow from n8n_workflows_list or get; it is not a tag ID and this call does not list unassigned tags. Use it before n8n_workflows_update_tags when assignments must be preserved; use n8n_tags_list for all tags. The endpoint has no cursor, so the tool keeps at most 100 records and reports exact omissions. Requires assignment-read permission; returns validated tag metadata.n8n_workflows_update_tagsReplace one workflow's complete tag assignment; this is not a merge. workflowId selects the workflow, while every tagIds item must be a stable tag ID from n8n_tags_list or get; tag names are not accepted. tagIds is the whole desired set, so omitted IDs are removed and [] clears all tags. Use n8n_workflows_get_tags first to preserve assignments. Requires write/unsafe mode plus assignment permission; returns n8n's validated replacement.n8n_workflows_archiveArchive one workflow without deleting its saved definition. workflowId must be the current stable ID from n8n_workflows_list or get, not a name or version ID. Use this instead of delete for reversible removal; use deactivate only to stop triggers. The availability change can disrupt callers. Requires unsafe mode plus archive permission; returns target-validated metadata with isArchived=true.- +32 more on 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 Server Atlassian Jira
{
"mcpServers": {
"aashari-mcp-server-atlassian-jira": {
"command": "npx",
"args": [
"-y",
"@aashari/mcp-server-atlassian-jira"
],
"env": {
"ATLASSIAN_SITE_NAME": "YOUR_ATLASSIAN_SITE_NAME_HERE",
"ATLASSIAN_USER_EMAIL": "YOUR_ATLASSIAN_USER_EMAIL_HERE",
"ATLASSIAN_API_TOKEN": "YOUR_ATLASSIAN_API_TOKEN_HERE"
}
}
}
}
N8n MCP Community
{
"mcpServers": {
"drzamarian-n8n-mcp-community": {
"command": "npx",
"args": [
"--yes",
"n8n-mcp-community@latest"
],
"env": {
"N8N_API_URL": "YOUR_N8N_API_URL_HERE",
"N8N_API_KEY": "YOUR_N8N_API_KEY_HERE"
}
}
}
}
Frequently asked questions
MCP Server Atlassian Jira is categorized under Workplace & Productivity and uses a local stdio subprocess. N8n MCP Community belongs to Workplace & Productivity and uses a local stdio subprocess. Pick MCP Server Atlassian Jira for workplace & productivity work and N8n MCP Community for workplace & productivity.
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 Server Atlassian Jira is listed as free. Auth: api key required. N8n MCP Community is listed as free. 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 aashari-mcp-server-atlassian-jira and drzamarian-n8n-mcp-community as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server Atlassian Jira has a quality signal of 65/100 (Great) with 5 views, 0 installs and 77 GitHub stars. N8n MCP Community has 63/100 (Good) with 3 views, 0 installs and 1 GitHub stars.