canonical: https://jentic.com/apis/atlassian.net/atlassian # Atlassian GetProjects The Jira Project Search API returns the Jira projects that the authenticated account can access on an Atlassian site, so an application can discover which projects are available before working with them. It exposes the Jira Cloud platform's paginated project search over a single read endpoint, authenticated with HTTP Basic credentials. Use it to enumerate accessible projects, not to read or change issues, boards, or other Jira data. ## For AI agents Search and list the Jira projects an account can access on an Atlassian site. Authenticates with HTTP Basic credentials. ## Scope Does not create issues, manage boards, or change project settings. Use for searching the Jira projects an account can access only. ## Capabilities - Search the Jira projects an account can access on a site - Enumerate available projects before working with their issues - Discover project availability for the authenticated Jira account ## Use cases ### Agent Project Discovery An AI agent connected through Jentic lists the Jira projects its account can access before it acts, so it chooses a real, permitted project instead of guessing a key. The search is read-only, which makes it a safe first step in any Jira workflow the agent runs through other APIs. Example prompt: List the Jira projects this account can access and return their names so I can pick one ### Project Availability Check A workflow confirms that a given project exists and is visible to the account before it tries to create or update work in it, avoiding failures against a project the account cannot see. The project search is the single source for that check. Example prompt: Search for a project by name and report whether the account can access it ### Project Inventory Sync A sync routine pulls the full set of projects an account can access so another system has an up-to-date inventory of Jira projects to reference. Because the endpoint is paginated, a sync can walk the whole result set. Example prompt: Retrieve every project the account can access and return the list for storage in another system ## Key resources - **Projects** — The Jira projects an account can access, returned by a paginated search ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 0 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 81 / 100 - AI-Readiness & Agent Experience: 8 / 100 - Agent Usability: 94 / 100 - Security: 10 / 100 - AI Discoverability: 0 / 100 - **View full report:** https://jentic.com/apis/atlassian.net/atlassian/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Jira Project Search API by hand means setting up HTTP Basic credentials for your Atlassian site and calling the paginated project search correctly. Through Jentic you install once, import it from the API Directory, store the credentials once, and your agent calls it. - **Permission scoping:** This API exposes a single read-only project search, so a rule can allow exactly that operation and nothing else. You choose the operations your agent may call, and with only project search available the agent can discover projects but cannot change anything. - **Credential handling:** Your Atlassian credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'list Jira projects', and Jentic returns the project-search operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Linear API** — Issue and project tracking for software teams with a fast API - **Trello API** — Kanban boards, cards, and lists from Atlassian - **Asana API** — Work management with tasks, projects, and portfolios ## FAQ ### Is there a Jira Project Search MCP server? You don't need an MCP server to give your agent the Jira Project Search API. Jentic connects it directly from the API Directory: import it, store your Atlassian credentials once, and your agent can list the accessible projects straight away, with no extra server to run and no tool definitions to load into the agent's context. ### Can I limit what my agent is allowed to do with the Jira Project Search API? Yes. This API has a single read-only project-search operation, so a rule can allow that one call and nothing else, which means the agent can discover projects but cannot read or modify any issue or board, and every call it makes is logged. ### What authentication does the Jira Project Search API use? The Jira Project Search API authenticates with HTTP Basic credentials for your Atlassian site, per its OpenAPI spec. Through Jentic the credentials are stored encrypted by your own instance and added to each request at call time, so they never appear in the agent's prompt or logs. ### Can I list all the projects on a Jira site with the Jira Project Search API? Yes. The project search returns the projects the authenticated account can access, so an agent can enumerate the available projects and pick one before working with its issues through other Jira APIs. The endpoint is read-only and changes nothing. ### What are the rate limits for the Jira Project Search API? The OpenAPI spec does not specify rate limits for the Jira Project Search API. Jira Cloud enforces its own platform rate limits; for current limits, see the Atlassian developer documentation at https://developer.atlassian.com. ### How do I list Jira projects with the Jira Project Search API through Jentic? Import this API from the Jentic API Directory, then have your agent issue a request such as 'list the Jira projects I can access'. Jentic matches the intent to the project-search operation and returns its input schema so the agent builds the correct request, with your stored Atlassian credentials injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.