Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

GitHub Issues Planning (BYOK) — connector documentation

  • MCP endpoint: https://byok-github-issues-planning.connectorbay.com/mcp
  • REST API: POST https://byok-github-issues-planning.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-github-issues-planning.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own GitHub Issues Planning GitHub personal access token (classic with repo scope, or fine-grained with issues read permission), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-github-issues-planning.connectorbay.com/health · Tool schemas: https://byok-github-issues-planning.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-github-issues-planning · agent@connectorbay.com

What GitHub Issues Planning (BYOK) is for

GitHub Issues Planning (BYOK) lets an AI assistant read your own GitHub Issues Planning data through the GitHub Issues Planning API with a key you supply (GitHub personal access token (classic with repo scope, or fine-grained with issues read permission)). Read-only: 12 tools (list_repo_labels, list_repo_milestones, get_milestone, list_assignees, get_issue, list_issue_comments, list_repo_issue_comments, list_issue_events, list_issue_labels, list_my_assigned_issues, list_org_issues, list_pull_request_reviews). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.github.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by GitHub Issues Planning. GitHub Issues Planning and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "What labels does octocat/hello-world use?"
  • "What milestones are open in octocat/hello-world?"
  • "How far along is milestone 1 of octocat/hello-world?"
  • "Who can be assigned issues in octocat/hello-world?"
  • "Show issue 42 in octocat/hello-world."
  • "What was said on issue 42?"

What it does

  • list_repo_labels: List the labels defined in a repository with colour and description.
  • list_repo_milestones: List the milestones of a repository with progress counts and due dates.
  • get_milestone: Get one milestone by number with its open and closed issue counts and due date.
  • list_assignees: List the users who can be assigned to issues in a repository.
  • get_issue: Get one issue or pull request by number with its body, labels, assignees and milestone.
  • list_issue_comments: List the comments on one issue or pull request.
  • list_repo_issue_comments: List recent issue and pull request comments across a whole repository.
  • list_issue_events: List the events on an issue (labeled, assigned, closed, referenced and so on) with actor and time.
  • list_issue_labels: List the labels currently on one issue or pull request.
  • list_my_assigned_issues: List issues across all repositories the token owner can see, filtered by assigned, created, mentioned or subscribed.
  • list_org_issues: List issues across an organization's repositories that match the filter for the token owner.
  • list_pull_request_reviews: List the reviews on a pull request with reviewer, state and time.

BYOK key

You bring your own GitHub Issues Planning GitHub personal access token (classic with repo scope, or fine-grained with issues read permission) (https://github.com/settings/tokens). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.github.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the GitHub Issues Planning API (api.github.com) with a BYOK key; documentation: https://docs.github.com/en/rest/issues. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by GitHub Issues Planning. GitHub Issues Planning and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your GitHub Issues Planning account.

Built for: Worldwide. Languages: English.