Search Jira work items with JQL

Search Jira work items with JQL

Returns the Jira work items that match a JQL query, with the fields you ask for, one page at a time.

Note: Page with nextPageToken. The older /rest/api/3/search is deprecated and being removed; for a query too long for a URL, use POST /rest/api/3/search/jql.

Set up

Use the first option your agent supports.

MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

{ "mcpServers": { "atlassian": { "url": "https://mcp.atlassian.com/v2/mcp" } } }

Call the MCP tool searchJiraIssuesUsingJql.

Server URL: https://mcp.atlassian.com/v2/mcp

Note: Tools beyond the listed ones are found with discover and run with executeRead or executeWrite; some spend Rovo credits.

CLI (official)

Install the command and sign in with it, then confirm it runs.

brew tap atlassian/homebrew-acli && brew install acli
acli --version

Run acli jira workitem search.

Note: Sign in with acli jira auth login --web. The CLI covers Jira only.

API (official)

• Base URL: https://{site}.atlassian.net
• Endpoint: GET /rest/api/3/search/jql
• Auth: send the header Authorization: Basic $ATLASSIAN_API_KEY
• Get a key: https://id.atlassian.com/manage-profile/security/api-tokens
• Docs: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/

Note: {site} is your Atlassian site name, as in acme.atlassian.net. ATLASSIAN_API_KEY holds the base64 of <email>:<api token>, and Confluence paths start with /wiki.

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

Rules

• Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
• Never print API keys.