Jira · Productivity

JIRA_LIST_PROJECTS

List Jira projects (paginated). Returns { projects: [{ id, key, name, projectTypeKey }], total, isLast }.

Provider
Jira
Access
Read
Category
Productivity
Version
v1

Input schema

{
  "type": "object",
  "properties": {
    "maxResults": {
      "type": "number",
      "description": "Projects per page (default 25, max 50)."
    },
    "startAt": {
      "type": "number",
      "description": "0-based index of the first project to return (default 0)."
    }
  },
  "additionalProperties": false
}

How to call it

Expose this tool to any MCP-capable agent (Claude, GPT, or your own) through CybrLink's MCP server. The agent calls jira_list_projects with arguments matching the schema above.

CybrLink validates the input, injects the connected Jira credentials server-side, and runs a single scoped provider API call through the shared proxy — the same guarded path as the generic call_api tool. The raw secret never reaches the model, and the response is trimmed to just the fields the agent needs.

Frequently asked

How do I let an AI agent jira list projects?
Connect Jira to CybrLink, then expose the `jira_list_projects` tool to any MCP-capable agent (Claude, GPT, or a custom framework). The agent calls it with typed arguments; CybrLink injects the Jira credential server-side and runs one scoped API call. List Jira projects (paginated). Returns { projects: [{ id, key, name, projectTypeKey }], total, isLast }.
Does the AI model see my Jira credentials when using JIRA_LIST_PROJECTS?
No. CybrLink stores the credential in a token vault and injects it on the server for each call, so the model can read this data from Jira without the OAuth token or API key ever entering its context.