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

GitHub Repo Insights (BYOK) — connector documentation

  • MCP endpoint: https://byok-github-repo-insights.connectorbay.com/mcp
  • REST API: POST https://byok-github-repo-insights.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-github-repo-insights.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own GitHub Repo Insights GitHub personal access token (repo scope; traffic data needs push access to the repository), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-github-repo-insights.connectorbay.com/health · Tool schemas: https://byok-github-repo-insights.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-github-repo-insights · agent@connectorbay.com

What GitHub Repo Insights (BYOK) is for

GitHub Repo Insights (BYOK) lets an AI assistant read your own GitHub Repo Insights data through the GitHub Repo Insights API with a key you supply (GitHub personal access token (repo scope; traffic data needs push access to the repository)). Read-only: 12 tools (get_traffic_views, get_traffic_clones, list_top_referrers, list_top_paths, get_commit_activity, get_weekly_participation, get_code_frequency, get_contributor_stats, list_contributors, get_languages, get_community_profile, get_topics). 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 Repo Insights. GitHub Repo Insights 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:

  • "How many people viewed octocat/Hello-World in the last two weeks?"
  • "How often was octocat/Hello-World cloned in the last two weeks?"
  • "Where do visitors of octocat/Hello-World come from?"
  • "Which pages of octocat/Hello-World are viewed most?"
  • "How active was development on octocat/Hello-World over the past year?"
  • "How many commits did octocat make compared with everyone on Hello-World each week?"

What it does

  • get_traffic_views: Get a repository's page views for the last 14 days with total and unique visitors per day or week (needs push access).
  • get_traffic_clones: Get a repository's clone counts for the last 14 days with total and unique cloners per day or week (needs push access).
  • list_top_referrers: List the top 10 sites sending traffic to a repository in the last 14 days (needs push access).
  • list_top_paths: List the top 10 pages of a repository by views in the last 14 days (needs push access).
  • get_commit_activity: Get commits per day of week for each of the last 52 weeks of a repository. Statistics are computed on demand: the first call can answer empty while GitHub builds them, so retry shortly.
  • get_weekly_participation: Get weekly commit counts for the last 52 weeks, for all contributors and for the owner alone. Statistics are computed on demand: the first call can answer empty while GitHub builds them, so retry shortly.
  • get_code_frequency: Get weekly additions and deletions of lines of code; each row is [week start, additions, deletions]. Statistics are computed on demand: the first call can answer empty while GitHub builds them, so retry shortly.
  • get_contributor_stats: Get every contributor's total commits and weekly additions, deletions and commits. Statistics are computed on demand: the first call can answer empty while GitHub builds them, so retry shortly.
  • list_contributors: List the people who contributed to a repository ranked by number of contributions.
  • get_languages: Get the programming languages used in a repository as bytes of code per language.
  • get_community_profile: Get a repository's community health score and which standard files (README, license, contributing guide, code of conduct) exist.
  • get_topics: Get the topics (tags) set on a repository.

BYOK key

You bring your own GitHub Repo Insights GitHub personal access token (repo scope; traffic data needs push access to the repository) (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 Repo Insights API (api.github.com) with a BYOK key; documentation: https://docs.github.com/en/rest/metrics. 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 Repo Insights. GitHub Repo Insights 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 Repo Insights account.

Built for: Worldwide. Languages: English.