π An MCP server for managing your personal knowledge, daily notes, and re-usable prompts via GitHub Gists
Configuration
View docs{
"mcpServers": {
"lostintangent-gistpad-mcp": {
"command": "npx",
"args": [
"-y",
"gistpad-mcp"
],
"env": {
"GITHUB_TOKEN": "<YOUR_PAT>"
}
}
}
}GistPad MCP is a local MCP server that exposes your GitHub Gists as MCP endpoints, enabling you to manage and reuse your notes, daily entries, and reusable prompts from any MCP-enabled client. It integrates with the GistPad ecosystem to let you interact with gists through MCP tools and resources for efficient knowledge work.
You connect to the server from an MCP client by configuring an MCP server entry that runs the GistPad MCP CLI locally. Once connected, you can list, create, update, delete, and organize gists, read and manage gist files, and work with daily notes, starred/archived items, and reusable prompts depending on which features you enable. Your client can also subscribe to gist resources to receive updates when gists change.
Prerequisites: ensure you have a modern Node.js runtime installed. You will also need a GitHub access token with at least the gist scope for operations that require authentication.
Install and run the MCP-enabled CLI for GistPad as described below. You can run it locally via npx to start interacting with your gists through MCP.
The following configuration snippet shows how to add GistPad as an MCP server using a local, stdio-based setup. This runs the GistPad MCP handler via npx and passes your GitHub token securely at runtime.
{
"mcpServers": {
"gistpad": {
"command": "npx",
"args": ["-y", "gistpad-mcp"],
"env": {
"GITHUB_TOKEN": "<YOUR_PAT>"
}
}
}
}Keep your GitHub token secure. Use environment variable placeholders in examples and avoid exposing credentials in shared configurations. If you expose your token, revoke it and generate a new one with the minimum required scopes.
If you donβt see changes reflected in your MCP client, trigger a refresh of gists from the client or re-run the refresh_gists operation to ensure the local cache is up to date.
The server exposes gists as resources via the gist:/// URI scheme, enabling read access to gist data without executing commands. You can opt into additional resource views like archived, starred, and daily notes by enabling corresponding flags.
For convenience, you can enable optional tool groups such as daily notes, starred items, archived items, and prompts by passing the respective flags when launching the MCP server. When enabled, those tools become available alongside the core gist management features.
List all gists for the authenticated user, excluding daily notes and archived items.
Retrieve the contents of a gist by its ID.
Create a new gist with a description and initial file contents.
Delete a gist by its ID.
Update the description of a gist by ID.
Create a copy of an existing gist with all its files.
Reload your gist lists, ignoring cached data.
Update the contents of a specific file within a gist.
Add a new file to an existing gist.
Delete a file from a gist.
Rename an existing file within a gist.
Perform targeted find-and-replace edits within a gist file.
List all comments for a specified gist.
Add a new comment to a gist.
Update the content of an existing gist comment.
Delete a comment from a gist.
Get or create today's daily note (optional).
Update the content of todayβs daily note (optional).
List all daily notes (optional).
Get the contents of a specific daily note by date (optional).
Delete a specific daily note by date (optional).
List all gists you have starred (optional).
Star a specific gist by ID (optional).
Unstar a starred gist by ID (optional).
List all archived gists (optional).
Archive one of your gists (optional).
Unarchive an archived gist (optional).
List the prompts in your prompts collection (optional).
Add a new prompt to your prompts collection (optional).
Delete a prompt from your collection (optional).