gistpad

GistPad MCP provides a server that integrates your GitHub Gists into MCP-enabled clients. It exposes a suite of tools to manage gists, their files, comments, and associated resources, along with optional prompts and daily notes. With this MCP, you can list, create, update, or delete gists, modify gist files and descriptions, comment on gists, and fetch summaries or specific content. It also exposes your gists as resources via the gist:/// URI scheme, enabling clients to interact with gists without executing tools. If you enable flags like --archived, --starred, or --daily, your resources will include archived or starred gists and daily notes, respectively, and the CLI will provide corresponding tools.

To use it, configure the MCP client to point at the gistpad-mcp CLI (as shown in the example config). Once running, you can issue commands to list gists, get contents, create or update files, add comments, and manage prompts. For example, you can ask your MCP client to list all gists, create a new gist with a description and initial files, or refresh the gist list after external edits so your client stays in sync.

Prerequisites:

• Node.js and npm installed on your system (Node.js 14+ recommended).
• A GitHub personal access token with the gist scope, stored as an environment variable (GITHUB_TOKEN) when running the server.

1. Install or verify Node.js and npm:

   • Visit https://nodejs.org and install the recommended LTS version.
   • Verify with: node -v and npm -v

2. Run the MCP server using npx (no global install required):

   • Create a config.json (or the MCP config file your environment expects) containing: { "mcpServers": { "gistpad": { "command": "npx", "args": ["-y", "gistpad-mcp"], "env": { "GITHUB_TOKEN": "<YOUR_PAT>" } } } }
   • Start the server with the appropriate runner in your environment (the npx command will fetch the gistpad-mcp package and start the MCP server).

3. Alternative: install globally and run directly

   • npm install -g gistpad-mcp
   • Run with your configured MCP env, using the same gistpad-mcp command and environment variables.

4. Verify operation

   • Ensure the server starts and exposes the configured endpoints to your MCP clients.
   • If you modify gists outside of MCP, use the refresh_gists tool to refresh the in-client cache.

Tips and common considerations:

• Environment variable: GITHUB_TOKEN must have gist scope for full access; never expose it in client-side code.
• The server caches gist lists and refreshes on changes or roughly hourly; use the refresh_gists tool if external edits occur and you don’t see updates yet.
• You can enable optional capabilities by including flags in your CLI invocation (e.g., --archived, --starred, --daily, --prompts, --markdown) to expose additional tools and resources.
• Resources are exposed via gist:/// URIs, and you can subscribe to changes if your MCP client supports resource subscriptions.
• For prompts, prompts are stored in a gist called 💬 Prompts and can include placeholders like {{argument}} for dynamic input.