Connect Github Gists to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Manage your code snippets and configs directly through your AI agent.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

How Vinkius works: one connection, every tool, in any AI
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Complete set · 8 capabilities

The complete GitHub capability set.

These are the exact actions your AI can choose when you ask it to work with GitHub.

Capability set01 / 02

01-04

4 capabilities in this set.

Part of 8 available through GitHub.

  1. 01

    Fork gist

    This capability creates a copy of a Gist in your own account. Use it to modify someone else's code without changing the original.

  2. 02

    Create gist

    This capability publishes new Gists to GitHub. You can send one or multiple files and choose to keep them secret or make them public.

  3. 03

    Delete gist

    This capability permanently removes a Gist and all its files. It requires a token and you should confirm before your agent runs it.

  4. 04

    Get gist

    This capability fetches a specific Gist and its contents. Public Gists are accessible without a token, but private ones require authentication.

Capability set02 / 02

05-08

4 capabilities in this set.

Part of 8 available through GitHub.

  1. 05

    List user gists

    This capability retrieves a list of Gists belonging to a specific GitHub user. Providing a token allows your agent to see private Gists as well.

  2. 06

    Get gist file

    This capability reads a single file from a Gist as plain text. It handles large files by streaming them from their raw URL.

  3. 07

    List public gists

    This capability lets your agent browse recently updated public Gists across all of GitHub without needing any credentials.

  4. 08

    Update gist

    This capability modifies an existing Gist. You can use it to change the description, toggle visibility, or update file contents.

One connector, every AI

GitHub works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put GitHub to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

1030ms average. Fast in production.

GitHub is checked daily against the live service.

Daily averagePeak 1105ms
Sep 25Today
Fastest day
1007ms
Slowest day
1105ms
14-day trend
Slowing+10%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 8 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of GitHub, so you can see the experience inside your AI.

It does not authenticate your account with GitHub. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

GitHub Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_5xj49hpb9hCS2AB5WT3ylyHhX3oQwXbqr007WQSr/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — GitHub capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "github-gists-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_5xj49hpb9hCS2AB5WT3ylyHhX3oQwXbqr007WQSr/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? How to give Claude access to GitHub

See all the AI clients this connector works with ↑

Who it's for

Built for the work GitHub owners hand off.

This MCP is built for developers and engineers who use Gists to store small, reusable pieces of code and configuration.

  • 01

    Developers

    They hand off the task of organizing and updating code snippets and notes to their agent.

  • 02

    Platform Engineers

    They use the agent to programmatically surface shared configuration snippets or documentation.

  • 03

    Automation Builders

    They let their agent publish and distribute versioned scripts via Gists.

FAQ

Questions GitHub owners ask.

  • 01

    Do I need a GitHub token to use this MCP?

    No, you can use it keyless to read public Gists. You only need a token to access private Gists or to create, edit, and delete Gists.

  • 02

    What is the rate limit for keyless requests?

    Without a token, you are limited to about 60 requests per hour per IP. With a token, you get an authenticated budget of about 5000 requests per hour.

  • 03

    Can my agent create public Gists?

    Yes, when using the create capability, you can set the visibility to public.

  • 04

    How does the MCP handle large files?

    For files larger than 1 MB, the MCP streams the content directly from the raw GitHub URL to ensure your agent receives the full file.

  • 05

    Is deleting a Gist permanent?

    Yes, deleting a Gist is irreversible. The agent should confirm with you before executing a delete command.

  • 06

    Do I need a GitHub token to use this?

    No. Public Gists can be listed, read and opened as files without any credential. A token is only required for your private Gists and for write operations (create, update, fork, delete).

  • 07

    What permissions does the token need?

    Only the "gist" permission. a classic personal access token with gist scope, or a fine-grained token with access to Gists. No repo access is required. Create the token under Settings > Developer settings > Personal access tokens.

  • 08

    Can I read large Gist files in full?

    Yes. The Gist payload includes up to 1 MB of content per file; get_gist_file transparently downloads larger files in full from their raw URL. For Gists whose files exceed 10 MB, clone them with the git URL (git_pull_url) returned by get_gist.

  • 09

    How does rate limiting work?

    Keyless (public reads) is limited to about 60 requests/hour per IP; with a token the budget is about 5000 requests/hour. When a limit is hit the capability returns a clear error with the time to wait and when the budget resets, instead of failing silently.

Connect GitHub to Claude, Cursor, ChatGPT & more