Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JIRA_URLNoSingle instance: URL of the Jira site (alternative to JIRA_BASE_URL).
JIRA_EMAILNoSingle instance: account email (Cloud) or username (Data Center basic auth).
JIRA_BASE_URLNoSingle instance: base URL of the Jira site (alternative to JIRA_URL).
JIRA_MCP_HOMENoState directory (defaults to ~/.multiinstance-jira-mcp).
JIRA_API_TOKENNoSingle instance: API token, personal access token, or Data Center password.
JIRA_INSTANCESNoComma-separated list of instance names for multi-instance configuration. Also accepts JSON in the same format as `instances` in the config file.
JIRA_READ_ONLYNoGlobal read-only mode, disabling write tools.false
JIRA_MCP_CONFIGNoPath to the config file (defaults to <home>/config.json if present).
JIRA_INSTANCE_NAMENoOptional name for the single instance; defaults to "default".default
JIRA_MCP_LOG_LEVELNoLog level (e.g. info, debug).info
JIRA_BROWSER_CHANNELNoBrowser channel for Playwright (default: bundled Chromium, then Chrome, then Edge).
JIRA_DEFAULT_INSTANCENoInstance used as the fallback for routing when none is specified.
JIRA_KEEPALIVE_SECONDSNoKeep-alive interval in seconds for browser sessions (0 = off).300
JIRA_MAX_ATTACHMENT_BYTESNoMaximum attachment size in bytes (default 20 MiB).20971520
JIRA_LOGIN_TIMEOUT_SECONDSNoBrowser login timeout in seconds.300

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server connects to one or more Jira instances at the same time. No instances are configured yet: use jira_add_instance. Every tool accepts an optional 'instance'. Issue arguments also accept 'instance:KEY-1' or a full browse URL, which selects the instance automatically. When the user's intent spans several Jira sites, use jira_search / jira_list_projects with allInstances=true. If a tool reports a missing or expired browser session, call jira_login for that instance and ask the user to finish signing in. Always confirm with the user before deleting issues.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
jira_list_instancesA

List every configured Jira instance (name, URL, deployment, auth method, mapped projects, session state) and the default instance. Call this first when unsure which instance to target.

jira_whoamiB

Verify connectivity and credentials by calling /myself. Without arguments it checks every configured instance in parallel.

jira_loginA

Open a browser window so the user can sign in to a Jira instance that uses auth 'browser' (SSO/SAML/OIDC). Session cookies are stored per instance. If sign-in takes longer than waitSeconds, the window stays open and the login completes in the background — call jira_login again (or jira_whoami) to check.

jira_logoutA

Delete the stored browser-session cookies of an instance. With forgetBrowserProfile=true also wipes the dedicated browser profile, so the identity provider asks for credentials again.

jira_add_instanceA

Register an additional Jira instance for this session (kept in memory; add it to your MCP config to make it permanent). Auth is inferred: email+token → basic (Jira Cloud API token), token only → bearer (Data Center PAT), nothing → browser SSO. Note: a token passed here is visible to the assistant; prefer configuring secrets in the MCP config.

jira_remove_instanceB

Remove an instance from this session. Optionally also delete its stored browser session.

jira_set_default_instanceA

Choose the instance used when a call cannot be routed automatically. Omit name to clear it.

jira_searchA

Run a JQL query. Target one instance, a list of instances or all of them at once (allInstances=true) — results are grouped per instance and a failure on one instance does not hide the others.

jira_get_issueA

Read an issue: summary, status, people, description as text, subtasks, links and latest comments. Set raw=true for the full Jira JSON.

jira_create_issueB

Create an issue. The description accepts light Markdown (headings, lists, bold, code, links, code fences) and is converted to the format the instance expects. The instance is routed by project key mapping or the 'instance' argument.

jira_update_issueA

Update fields of an issue. Only the provided fields change. Use jira_transition_issue to change status and jira_assign_issue to change assignee.

jira_delete_issueB

Permanently delete an issue. Requires delete permission. Ask the user for confirmation first.

jira_assign_issueA

Assign an issue. user accepts 'me', an email/display name, a Cloud accountId or a Data Center username. Use 'none' to unassign.

jira_get_transitionsB

List the workflow transitions currently available for an issue.

jira_transition_issueA

Move an issue through its workflow. 'transition' may be a transition id, a transition name or the target status name.

jira_get_commentsB

Read the most recent comments of an issue as plain text.

jira_add_commentB

Add a comment to an issue (light Markdown supported).

jira_list_projectsB

List projects visible to the account. Supports several instances at once (instances / allInstances).

jira_list_boardsB

List Jira Software boards (Scrum/Kanban), optionally filtered by project or name.

jira_list_sprintsC

List sprints of a Scrum board.

jira_list_issue_typesA

List issue types, globally or those available in a project.

jira_list_statusesC

List workflow statuses, globally or per issue type for a project.

jira_search_usersA

Find users by name/email. With projectKey, only users assignable in that project are returned.

jira_add_attachmentA

Attach a file to an issue, either downloaded from a public URL or read from a local path on the machine running this server.

jira_copy_issueA

Copy an issue (summary, description, labels, optionally priority and comments) from one Jira instance to a project on another instance — or the same one. Adds cross-reference comments when linkBack is true.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 25 tools

Disambiguation4/5

Most tools map to a distinct resource+action, and instance-management tools (add/remove/set_default/login/logout) are clearly separable from issue operations. Minor overlap exists: jira_get_comments duplicates what jira_get_issue already returns, and jira_whoami partially overlaps jira_list_instances in surfacing instance/auth state.

Naming Consistency5/5

Every tool uses the jira_ prefix with snake_case verb_noun phrasing (get_issue, create_issue, list_projects, add_attachment, copy_issue). The only mild deviation is jira_whoami, which is a standard, well-understood identifier rather than an inconsistency.

Tool Count4/5

25 tools is at the heavy end but justified by covering multiple distinct areas: instance/auth management, issue CRUD, workflow transitions, and Jira Software metadata (boards, sprints, statuses, users). Nothing feels obviously redundant, though a few list_* tools could theoretically be consolidated.

Completeness4/5

Covers the core Jira lifecycle thoroughly: issue CRUD, transitions, assignment, comments, attachments, cross-instance copy, and metadata lookups. Gaps remain around comment update/delete, issue linking, worklogs, and attachment retrieval/removal, but these are minor for most agent workflows.

Maintenance

ActivityMaintained
ResponsivenessOutdated data