Jira (user passthrough)

Note: this connector has no hand-written README yet. Only the auto-generated reference below is available. See the connector's manifest at connectors/identos.jira-user/connector.v1.json for the source.

Manifest reference

• ID: identos.jira-user
• Version: 1.0.0
• Resource type: urn:connector:identos:jira-user

Supported auth modes

Type	Details
idp_passthrough	requires IdP atlassian; setup fields: site, cloudid

Setup fields

ID	Label	Default	Secret?	Notes
site	Atlassian site	—	no	placeholder: acme / The subdomain of your Atlassian cloud URL (e.g. 'acme' for acme.atlassian.net). Used in resource IDs and to locate the cloud ID.
cloudid	Atlassian cloud ID	—	no	placeholder: 11223344-5566-7788-9900-aabbccddeeff / UUID identifying your Atlassian site. Get from https://{site}.atlassian.net/_edge/tenant_info (the cloudId field). Required because Atlassian Cloud OAuth tokens route through https://api.atlassian.com/ex/jira/\{cloudid\}/, not the site URL directly.

Scopes

Scope
jira:issues:read
jira:issues:write
jira:projects:read

Routes

Method	Pattern	Scope	Resource template
GET	/rest/api/3/search/jql	jira:issues:read	—
GET	/rest/api/3/issue/{issue_key}	jira:issues:read	jira://{{site}}/issues/{{issue_key}}
GET	/rest/api/3/issue/{issue_key}/transitions	jira:issues:read	jira://{{site}}/issues/{{issue_key}}
POST	/rest/api/3/issue	jira:issues:write	—
PUT	/rest/api/3/issue/{issue_key}	jira:issues:write	jira://{{site}}/issues/{{issue_key}}
POST	/rest/api/3/issue/{issue_key}/transitions	jira:issues:write	jira://{{site}}/issues/{{issue_key}}
GET	/rest/api/3/project/search	jira:projects:read	—

MCP tools

Name	Scope	Description
search_issues	jira:issues:read	Search Jira issues using JQL (Jira Query Language). Returns {issues, nextPageToken, isLast} — pass nextPageToken back to fetch the next page (the legacy startAt/total response shape was retired by Atlassian on 2025-05-01).
get_issue	jira:issues:read	Get a single Jira issue by its key (e.g. ACME-123). STRONGLY recommend passing fields — Atlassian's default response includes 100+ custom-field entries (most null) and runs ~10 KB per issue. A typical agent request only needs a handful: try "summary,status,priority,assignee,reporter,description,issuetype,labels,created,updated". Description bodies come back as ADF (Atlassian Document Format) JSON, not plain text.
get_transitions	jira:issues:read	List the workflow transitions currently available on a Jira issue. Each entry carries an id (string) you pass to transition_issue. Transition IDs and labels vary per project workflow — "Done" might be "31" in one project, "41" or "61" in another — so always discover via this tool before calling transition_issue instead of guessing.
create_issue	jira:issues:write	Create a new Jira issue. IMPORTANT: Atlassian Cloud's REST API v3 requires the description field (if present) to be an Atlassian Document Format (ADF) JSON object, NOT a plain string — passing plain text returns HTTP 400 with no useful error. If you don't need a description, omit it entirely (the example below shows the minimal valid shape). If you DO need one, wrap your text in ADF as shown in the second example.
update_issue	jira:issues:write	Update fields on an existing Jira issue. Same ADF caveat as create_issue: any description you pass must be an ADF doc, not a plain string, or Atlassian returns HTTP 400.
transition_issue	jira:issues:write	Transition a Jira issue through a workflow (e.g. Open → In Progress → Done). Discover valid transition IDs first via get_transitions — IDs are workflow-specific and don't match across projects.
list_projects	jira:projects:read	List Jira projects the caller can see. Paginated — returns {values, startAt, maxResults, total, isLast}. Pass query to filter by substring (matches project name + key); pass maxResults to bound the response size (Atlassian default is 50, max 50 server-side). The legacy unpaginated /rest/api/3/project endpoint was retired in favour of this one and would overflow MCP tool-result limits at any non-trivial org size.