Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

Add a Jira instance at runtime

jira_add_instance

Register an additional Jira instance in memory for the current session and infer authentication from supplied credentials, enabling routing to multiple Jira sites.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "url": "<url>"
    },
    "name": "jira_add_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesBase URL, e.g. https://acme.atlassian.net or https://jira.corp.local/jira
authNo
nameYesShort unique name, e.g. 'work' or 'client-a'.
emailNoAccount email (Cloud) or username (Data Center basic auth).
tokenNoAPI token (Cloud) or personal access token (Data Center).
replaceNoOverwrite an existing instance with the same name.
projectsNoProject keys hosted on this instance (enables routing).
readOnlyNo
apiVersionNo
deploymentNo
descriptionNo
makeDefaultNo
defaultProjectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare non-read-only, non-destructive, open-world; the description adds genuinely new behavior: state is in-memory only, expires with the session, and secret material passed as a token is exposed to the assistant. It omits what happens on a name collision without replace, which is the main remaining behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, front-loaded with the operation and scope, then persistence semantics, then auth inference, then the security caveat. No filler and nothing repeated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-parameter session-mutating tool with no output schema, the description covers the two hardest concepts (auth inference and persistence) well. It still leaves roughly half the parameters unexplained and never states the failure mode when a name already exists, so an agent could call it without understanding conflict handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 46% across 13 parameters, so the description must compensate. It does add real meaning for the auth-related fields (email+token → basic, token only → bearer, nothing → browser SSO), but leaves projects, readOnly, apiVersion, deployment, makeDefault, defaultProject, and replace entirely to the terse schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Register an additional Jira instance for this session" gives a specific verb (register), resource (Jira instance), and scope (this session), which inherently separates it from jira_list_instances, jira_remove_instance, and jira_set_default_instance. An agent can identify the operation without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It distinguishes the runtime path from the permanent path ("add it to your MCP config to make it permanent") and steers away from passing secrets at runtime. It does not explicitly address when to prefer this over jira_login for an already-registered instance, so the routing guidance is clear but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.