# How to integrate Gist MCP with Claude Code ```json { "title": "How to integrate Gist MCP with Claude Code", "toolkit": "Gist", "toolkit_slug": "gist", "framework": "Claude Code", "framework_slug": "claude-code", "url": "https://composio.dev/toolkits/gist/framework/claude-code", "markdown_url": "https://composio.dev/toolkits/gist/framework/claude-code.md", "updated_at": "2026-05-12T10:13:01.353Z" } ``` ## Introduction Manage your Gist directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: - Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach - Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control ## Also integrate Gist with - [OpenAI Agents SDK](https://composio.dev/toolkits/gist/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/gist/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/gist/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/gist/framework/codex) - [OpenClaw](https://composio.dev/toolkits/gist/framework/openclaw) - [Hermes](https://composio.dev/toolkits/gist/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/gist/framework/cli) - [Google ADK](https://composio.dev/toolkits/gist/framework/google-adk) - [LangChain](https://composio.dev/toolkits/gist/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/gist/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/gist/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/gist/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/gist/framework/crew-ai) ## TL;DR - Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles. - Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling. - Handling Large tool responses out of LLM context to minimize context rot. - Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need. ## Connect Gist to Claude Code ### Connecting Gist to Claude Code using Composio 1. Add the Composio MCP to Claude ```bash claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp ``` ## What is Claude Code? Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working. Key features include: - Terminal-Native Experience: Work with Claude directly in your command line without switching contexts - MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities - Project Context: Claude understands your project structure and can read, write, and modify files - Interactive Development: Ask questions, debug code, and get help in real-time while coding - Multi-Platform: Works on macOS, Linux, WSL, and Windows ## What is the Gist MCP server, and what's possible with it? The Gist MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your GitHub Gist account. It provides structured and secure access to your gists, so your agent can create, manage, comment on, and organize code snippets and notes on your behalf. - Gist creation and management: Quickly ask your agent to create new public or private gists, update existing ones, or fetch details for any gist you own or have access to. - Commenting and collaboration: Let your agent add, list, retrieve, or delete comments on your gists to streamline discussion and feedback without manual effort. - Revision history and tracking: Effortlessly review a gist's revision history, retrieve specific past versions, and understand changes over time. - Star and fork management: Direct your agent to list your starred gists, check if you've starred a gist, or see all forks of a particular gist to keep track of popularity and collaboration. - Personalized gist organization: Have your agent list all your gists or your starred gists, making it easy to find, organize, and revisit important code snippets and notes. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `GIST_CHECK_GIST_STAR` | Check Gist Star | Check if the authenticated user has starred a specific gist. Returns True if the gist is starred, False if not starred or if the gist doesn't exist. This is a read-only, idempotent operation that requires authentication but no special permissions. | | `GIST_CREATE_GIST` | Create Gist | Tool to create a new gist with one or more files. Use when you need to create a code snippet or text file to share. Note: Do not name your files 'gistfile' with a numerical suffix. | | `GIST_CREATE_GIST_COMMENT` | Create Gist Comment | Tool to create a comment on a gist. Use when you need to add a comment to an existing gist. | | `GIST_DELETE_GIST` | Delete Gist | Tool to delete a gist. Use when you have a gist_id and want to permanently remove that gist. Example prompt: "Delete gist 'aa5a315d61ae9438b18d'". | | `GIST_DELETE_GIST_COMMENT` | Delete Gist Comment | Tool to delete a comment on a gist. Use when you have both the gist_id and comment_id and want to remove that comment. Example prompt: "Delete comment 42 from gist 'aa5a315d61ae9438b18d'". | | `GIST_FORK_GIST` | Fork Gist | Tool to fork a gist. Use when you need to create a copy of an existing gist under your own account. | | `GIST_GET_GIST` | Get Gist | Tool to retrieve a specific gist by its ID. Use when you have a gist_id and need complete gist details. | | `GIST_GET_GIST_COMMENT` | Get Gist Comment | Tool to get a specific comment on a gist. Use when you need to retrieve details of a particular comment given gist_id and comment_id. | | `GIST_GET_GIST_REVISION` | Get Gist Revision | Tool to retrieve a specific gist revision. Use when you need details of a past state for an existing gist by commit SHA. | | `GIST_LIST_GIST_COMMENTS` | List Gist Comments | Tool to list comments on a gist. Use after confirming the gist_id to retrieve comments for a specific gist. Example: 'List comments for gist abc123'. | | `GIST_LIST_GIST_COMMITS` | List Gist Commits | Tool to list the commit history of a gist. Use after you have the gist ID to review its revisions. | | `GIST_LIST_GIST_FORKS` | List Gist Forks | Tool to list forks of a gist. Use after obtaining a gist_id to retrieve all forks for the gist. | | `GIST_LIST_GISTS` | List Gists | Tool to list the authenticated user's gists or all public gists if called anonymously. Use after setting a valid GitHub token in headers. | | `GIST_LIST_PUBLIC_GISTS` | List Public Gists | Tool to list public gists sorted by most recently updated. Use when you need to discover recent public gists. Note: with pagination, you can fetch up to 3000 gists. | | `GIST_LIST_STARRED_GISTS` | List Starred Gists | Tool to list the authenticated user's starred gists. Use when you need to retrieve all gists the user has starred. | | `GIST_LIST_USER_GISTS` | List User Gists | Tool to list public gists for a specified GitHub user. Use when you have a username and need their gists. | | `GIST_STAR_GIST` | Star a Gist | Star a GitHub gist. This operation is idempotent and will succeed even if the gist is already starred. | | `GIST_UNSTAR_GIST` | Unstar a Gist | Unstar a GitHub gist. This operation is idempotent and will succeed even if the gist is not currently starred. | | `GIST_UPDATE_GIST` | Update Gist | Tool to update a gist's description and files. Use when you need to modify gist content, rename files, or delete files from a gist. | | `GIST_UPDATE_GIST_COMMENT` | Update Gist Comment | Tool to update a Gist comment. Updates an existing comment on a gist. You must be the author of the comment to update it. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Gist MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Gist account. It provides structured and secure access so Claude can perform Gist operations on your behalf. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before starting, make sure you have: - Claude Pro, Max, or API billing enabled Anthropic account - Composio API Key - A Gist account - Basic knowledge of Python or TypeScript ### 1. Install Claude Code To install Claude Code, use one of the following methods based on your operating system: ```bash # macOS, Linux, WSL curl -fsSL https://claude.ai/install.sh | bash # Windows PowerShell irm https://claude.ai/install.ps1 | iex # Windows CMD curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd ``` ### 2. Set up Claude Code Open a terminal, go to your project folder, and start Claude Code: - Claude Code will open in your terminal - Follow the prompts to sign in with your Anthropic account - Complete the authentication flow - Once authenticated, you can start using Claude Code ```bash cd your-project-folder claude ``` ### 3. Set up environment variables Create a .env file in your project root with the following variables: - COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code)) - USER_ID identifies the user for session management (use any unique identifier) ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here ``` ### 4. Install Composio library No description provided. ```python pip install composio-core python-dotenv ``` ```typescript npm install @composio/core dotenv ``` ### 5. Generate Composio MCP URL No description provided. ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["gist"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http gist-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; const { COMPOSIO_API_KEY, USER_ID } = process.env; if (!COMPOSIO_API_KEY || !USER_ID) { throw new Error('COMPOSIO_API_KEY and USER_ID required in .env'); } const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['gist'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http gist-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ### 6. Run the script and copy the MCP URL No description provided. ```python python generate_mcp_url.py ``` ```typescript node --loader ts-node/esm generate_mcp_url.ts # or if using tsx tsx generate_mcp_url.ts ``` ### 7. Add Gist MCP to Claude Code In your terminal, add the MCP server using the command from the previous step. The command format is: - claude mcp add registers a new MCP server with Claude Code - --transport http specifies that this is an HTTP-based MCP server - The server name (gist-composio) is how you'll reference it - The URL points to your Composio Tool Router session - --headers includes your Composio API key for authentication After running the command, close the current Claude Code session and start a new one for the changes to take effect. ```bash claude mcp add --transport http gist-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY" # Then restart Claude Code exit claude ``` ### 8. Verify the installation Check that your Gist MCP server is properly configured. - This command lists all MCP servers registered with Claude Code - You should see your gist-composio entry in the list - This confirms that Claude Code can now access Gist tools If everything is wired up, you should see your gist-composio entry listed: ```bash claude mcp list ``` ### 9. Authenticate Gist The first time you try to use Gist tools, you'll be prompted to authenticate. - Claude Code will detect that you need to authenticate with Gist - It will show you an authentication link - Open the link in your browser (or copy/paste it) - Complete the Gist authorization flow - Return to the terminal and start using Gist through Claude Code Once authenticated, you can ask Claude Code to perform Gist operations in natural language. For example: - "List all my public and private gists" - "Show comments for gist with ID abc123" - "Check if I starred gist aa5a315d61ae9438b18d" ## Complete Code ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["gist"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http gist-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; const { COMPOSIO_API_KEY, USER_ID } = process.env; if (!COMPOSIO_API_KEY || !USER_ID) { throw new Error('COMPOSIO_API_KEY and USER_ID required in .env'); } const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['gist'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http gist-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ## Conclusion You've successfully integrated Gist with Claude Code using Composio's MCP server. Now you can interact with Gist directly from your terminal using natural language commands. Key features of this setup: - Terminal-native experience without switching contexts - Natural language commands for Gist operations - Secure authentication through Composio's managed MCP - Tool Router for dynamic tool discovery and execution Next steps: - Try asking Claude Code to perform various Gist operations - Add more toolkits to your Tool Router session for multi-app workflows - Integrate this setup into your development workflow for increased productivity You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities. ## How to build Gist MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/gist/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/gist/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/gist/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/gist/framework/codex) - [OpenClaw](https://composio.dev/toolkits/gist/framework/openclaw) - [Hermes](https://composio.dev/toolkits/gist/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/gist/framework/cli) - [Google ADK](https://composio.dev/toolkits/gist/framework/google-adk) - [LangChain](https://composio.dev/toolkits/gist/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/gist/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/gist/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/gist/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/gist/framework/crew-ai) ## Related Toolkits - [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure. - [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms. - [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place. - [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences. - [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses. - [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure. - [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure. - [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction. - [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting. - [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache. - [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence. - [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place. - [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines. - [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure. - [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code. - [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows. - [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights. - [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews. - [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease. - [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Gist MCP? With a standalone Gist MCP server, the agents and LLMs can only access a fixed set of Gist tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Gist and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Claude Code? Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Gist tools. ### Can I manage the permissions and scopes for Gist while using Tool Router? Yes, absolutely. You can configure which Gist scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do. ### How safe is my data with Composio Tool Router? All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Gist data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) ยท [Composio docs](https://docs.composio.dev/llms.txt)