add_gist_comment
Add a comment to a gist
LABSCO 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
USE CASES
01
Keeping a running note up to date
Find the gist in the listing, read the file you are changing, and replace the exact string — the edit fails rather than guessing when that string appears more than once.
02
Turning a snippet into something you can send someone
Create the gist public or secret, add the extra files it needs, and give it a description that will still make sense when it turns up in the listing months later.
03
Answering the feedback someone left on a gist
Read the thread, reply in place, and correct your own comment rather than posting a second one underneath it.
04
Reorganising files inside a gist that grew
Rename files into something consistent, drop the ones that no longer belong, and refresh the server's cache so changes made from another client are visible.
16 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
add_gist_file
Add a new file to a gist
create_gist
Create a new GitHub Gist
delete_gist
Delete a GitHub Gist by ID
delete_gist_comment
Delete a comment from a gist
delete_gist_file
Delete a file from a gist
duplicate_gist
Create a copy of an existing gist
edit_gist_comment
Update the content of an existing gist comment
edit_gist_file
Edit a file in a gist using find-and-replace. More efficient than update_gist_file for targeted changes. The old_string must uniquely identify the text to replace - if multiple matches exist, the edit will fail unless replace_all is true.
get_gist
Get the full contents of a GitHub Gist by ID (including file contents).
list_gist_comments
List all comments on a gist
list_gists
List all of your GitHub Gists (excluding daily notes, prompts, and archived gists)
refresh_gists
Refresh the server's cache of gists, to ensure it picks up any changes made by external clients.
rename_gist_file
Rename a file in a gist
update_gist_description
Update a GitHub Gist's description
update_gist_file
Update the content of a file in a gist
BEFORE YOU INSTALL
What to know first
Tools you get
16 tools when we connected; the project documents 30. Four tool sets are off by default: --daily adds five daily-note tools, while --starred, --archived and --prompts add three each. The prompt tools are named add_gist_prompt and delete_gist_prompt, not add_prompt and delete_prompt.
Requires
- npx on PATH
- GITHUB_TOKEN in your environment
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y gistpad-mcpMCP Clients
VS Code
Install the GistPad extension from https://aka.ms/gistpad, reload VS Code, open the GistPad tab and sign in with your GitHub account
Claude Desktop, Other MCP clients
JSON
{
"mcpServers": {
"gistpad": {
"command": "npx",
"args": [
"-y",
"gistpad-mcp"
],
"env": {
"GITHUB_TOKEN": "<YOUR_PAT>"
}
}
}
}Other MCP clients — all toolsets
OTHER MCP CLIENTS — ALL TOOLSETS · JSON
{
"mcpServers": {
"gistpad": {
"command": "npx",
"args": [
"-y",
"gistpad-mcp",
"--daily",
"--starred",
"--archived",
"--prompts"
],
"env": {
"GITHUB_TOKEN": "<YOUR_PAT>"
}
}
}
}
