Summary
The edit tool refuses an ambiguous match instead of picking one for you.
edit_gist_file takes old_string and new_string and stops when the match is not unique unless replace_all is passed, which is what makes it safe to point an agent at a long note. The server keeps its own cache of your gists, and refresh_gists is there because another client can change them behind its back. The default listing hides daily notes, prompts and archived gists, so something you cannot find in the list may still be reachable by id.
What it is
A server over your GitHub Gists — gist and file lifecycle, targeted edits and comment threads — in 16 tools.
What you get
- Gists created public or secret, fetched with their file contents, duplicated, redescribed and deleted by id
- File-level work inside a gist: add, rename, replace contents, delete
- A find-and-replace edit that requires old_string to identify one place uniquely and fails rather than guessing when it does not, unless replace_all is set
- Comment threads listed, added to, edited and deleted
- A listing that deliberately leaves out daily notes, prompts and archived gists, and a cache refresh for changes another client made underneath it
Requirements
GITHUB_TOKEN for the account whose gists you want reachable. MIT.
Setup effort
One command plus a key — npx -y gistpad-mcp, then supply credentials