mcpField
B
blink-github

blink-github

github.com/blink-newDevelopment438 installsUpdated 2w ago
Repository

About blink-github

blink-github is a skill for accessing GitHub through a workspace GitHub App installation in Blink. It supports repository operations and uses short-lived tokens minted server-side rather than storing personal access tokens on disk.

Key features

  1. 01View connected GitHub accounts
  2. 02Clone GitHub repositories
  3. 03Use the REST API for repository operations
  4. 04Authenticate with short-lived tokens

Use cases

  1. 01Inspect repositories and create issues
  2. 02Clone a repository for development
  3. 03Push code or create PRs from Blink Claw agents

MCP support

GitHub API requests can be made with the `blink_connector_exec` MCP tool.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/blink-new/blink-plugin --skill blink-github

After installing, type/blink-githubin Claude Code to confirm it loaded.

Details

From the project README

Blink GitHub

Full GitHub access backed by a workspace GitHub App installation. Tokens are short-lived (1h), minted just-in-time server-side — no personal access token, no gh auth login, no secrets on disk.

CLI

# Show all connected GitHub accounts (workspaces can link multiple)
blink github status

# Clone a repo (token is used for auth, stripped from .git/config after)
blink github clone owner/repo
blink github clone https://github.com/owner/repo.git --branch feat/x

# Print a short-lived token for scripting
blink github token --json | jq -r .token

# Multi-account: pick a specific installation
blink github clone owner/repo --account blink-new
blink github token --account my-employer-org

REST API (connector exec)

# List repos
blink connector exec github /user/repos GET

# Get a specific repo
blink connector exec github /repos/owner/repo GET

# Create an issue
blink connector exec github /repos/owner/repo/issues POST \
  '{"title":"Bug report","body":"Steps to reproduce..."}'

# List open PRs
blink connector exec github /repos/owner/repo/pulls GET '{"state":"open"}'

# CI status (last 5 runs)
blink connector exec github /repos/owner/repo/actions/runs GET '{"per_page":5}'

# Read a file (returns base64-encoded content)
blink connector exec github /repos/owner/repo/contents/README.md GET

MCP Tools

Use the blink_connector_exec tool with provider: "github":

{
  "tool": "blink_connector_exec",
  "provider": "github",
  "projectId": "proj_xxx",
  "endpoint": "/repos/owner/repo/issues",
  "httpMethod": "POST",
  "params": { "title": "Bug", "body": "Details..." }
}

Prerequisites

Connect GitHub once at blink.new/settings?tab=connectors.

The workspace links a GitHub App installation — not a personal OAuth token. This means:

  • Works on SSO/SAML-enforced orgs (no per-token SSO dance)
  • Short-lived 1h tokens — no long-lived secrets
  • Revoke by uninstalling the App; no keys to rotate manually
  • Multi-account: link your personal account + work orgs independently

On Blink Claw agents

git clone, git push, gh pr create work with zero setup — the Claw image ships a system-level git credential helper that mints tokens automatically. No gh auth login, no PAT.

Comments

Markdown supported