The author is explicit that the rewrite was about resource use and dependency problems, not features — so choose it when you want gist access without adding another Node process to your machine, and choose the original when you want whatever it has that this does not yet. The VS Code setup is the better one to copy: the token is a prompted password input, so it never lands in a config file you might commit.
A Go rewrite of GistPad MCP, built on the mark3labs/mcp-go library. It does what the original does — put your GitHub gists in reach of an MCP client — but ships as one compiled executable, which is the reason it exists: no dependency tree to install and keep working alongside everything else on the machine.
- Your GitHub gists reachable from an MCP client, authenticated with a personal access token
- A single binary you build once and point the client at — no runtime, no package install, no version drift with other tools on the same machine
- Editor wiring documented for both Cursor and VS Code, with VS Code prompting for the token as a password input at server start rather than storing it in the config file
- A `--debug` flag for when a call is not doing what you expect
A GitHub personal access token, passed as `GITHUB_TOKEN`. Go 1.24 or newer to build: clone the repository and run `go build -o gist-mcp ./cmd/gist-mcp/main.go`, then point your client's `command` at the resulting binary. There is no published package — building from source is the install path. The token scopes you grant decide what it can reach, so a gist-only token keeps it away from the rest of your account.