SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Gist MCP with Claude Agent SDK

Connect Claude Agent SDK to Gist MCP. List all your public and private gists, show comments for gist with id abc123, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Gist logoGist
Api Key

GitHub Gist is a service for sharing code snippets and notes. It makes it easy to collaborate and organize your code or text, publicly or privately.

20 Tools

Introduction

This guide walks you through connecting Gist to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Gist agent that can create and update gists, fork and star snippets, comment on gists, and browse revision history through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Gist account through Composio's Gist MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Gist with

Claude CodeClaude CoworkOpenAI Agents SDKGrok BotCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Gist
  • Configure an AI agent that can use Gist as a tool
  • Run a live chat session where you can ask the agent to perform Gist operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Gist account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Gist functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  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 composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Gist
  const session = await composio.create(USER_ID, {
    toolkits: ['gist'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Gist
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Gist tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Gist
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Gist and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  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 composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['gist']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Gist tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Gist through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

Every Gist action and event your agent gets out of the box.

Check Gist Star

Check if the authenticated user has starred a specific gist.

Create Gist

Tool to create a new gist with one or more files.

Create Gist Comment

Tool to create a comment on a gist.

Delete Gist

Delete a gist by ID.

Delete Gist Comment

Delete a gist comment by gist ID and comment ID.

Fork Gist

Tool to fork a gist.

Get Gist

Retrieve a gist by ID, including its file metadata and available contents.

Get Gist Comment

Tool to get a specific comment on a gist.

Get Gist Revision

Tool to retrieve a specific gist revision.

List Gist Comments

Tool to list comments on a gist.

List Gist Commits

Tool to list the commit history of a gist.

List Gist Forks

List a page of forks for a gist by ID, with optional pagination.

List Gists

List the authenticated user's gists, with optional update-time filtering and pagination.

List Public Gists

Tool to list public gists sorted by most recently updated.

List Starred Gists

List a page of the authenticated user's starred gists, optionally filtered by update time.

List User Gists

Tool to list public gists for a specified GitHub user.

Star a Gist

Star a GitHub gist.

Unstar a Gist

Unstar a GitHub gist.

Update Gist

Tool to update a gist's description and files.

Update Gist Comment

Tool to update a Gist comment.

FRAMEWORKS

How to build Gist MCP Agent with another framework

Claude Code logo

Claude Code

Use Gist MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Gist MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Gist MCP with OpenAI Agents SDK

Grok Bot logo

Grok Bot

Use Gist MCP with Grok Bot

Codex logo

Codex

Use Gist MCP with Codex

OpenClaw logo

OpenClaw

Use Gist MCP with OpenClaw

Hermes logo

Hermes

Use Gist MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Gist MCP with Atomic Agent

Google ADK logo

Google ADK

Use Gist MCP with Google ADK

LangChain logo

LangChain

Use Gist MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Gist MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Gist MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Gist MCP with LlamaIndex

CrewAI logo

CrewAI

Use Gist MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Gist MCP with Pydantic AI

AutoGen logo

AutoGen

Use Gist MCP with AutoGen

FAQ

Frequently asked questions

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.

Yes, you can. Claude Agent SDK 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.

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.

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.

Start with Gist.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Gist tool your agent needs.Free to start.

Start building