Github · Developer

GITHUB_LIST_ISSUES

List issues in a GitHub repository accessible to the connected token. Returns { issues: [{ id, number, title, state, html_url, user, labels }] }.

Provider
Github
Access
Read
Category
Developer
Version
v1

Input schema

{
  "type": "object",
  "properties": {
    "owner": {
      "type": "string",
      "description": "Repository owner (user or org login)."
    },
    "repo": {
      "type": "string",
      "description": "Repository name."
    },
    "state": {
      "type": "string",
      "enum": [
        "open",
        "closed",
        "all"
      ],
      "description": "Issue state filter (default open)."
    },
    "perPage": {
      "type": "number",
      "description": "Max issues to return (default 30, max 100)."
    },
    "page": {
      "type": "number",
      "description": "Page number to return (default 1)."
    }
  },
  "required": [
    "owner",
    "repo"
  ],
  "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 github_list_issues with arguments matching the schema above.

CybrLink validates the input, injects the connected Github 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 github list issues?
Connect Github to CybrLink, then expose the `github_list_issues` tool to any MCP-capable agent (Claude, GPT, or a custom framework). The agent calls it with typed arguments; CybrLink injects the Github credential server-side and runs one scoped API call. List issues in a GitHub repository accessible to the connected token. Returns { issues: [{ id, number, title, state, html_url, user, labels }] }.
Does the AI model see my Github credentials when using GITHUB_LIST_ISSUES?
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 Github without the OAuth token or API key ever entering its context.