How to integrate Givebutter MCP with LangChain

This guide walks you through connecting Givebutter to LangChain using the Composio tool router. By the end, you'll have a working Givebutter agent that can create a new fundraising campaign for our school, list all recent payouts to our nonprofit account, get details for fund with id fund_abc123 through natural language commands. This guide will help you understand how to give your LangChain agent real control over a Givebutter account through Composio's Givebutter MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Givebutter logoGivebutter
Api Key

Givebutter is a fundraising platform with a free, open API for managing campaigns and donations. It helps organizations easily track giving, engage supporters, and streamline fundraising efforts.

58 Tools

Introduction

This guide walks you through connecting Givebutter to LangChain using the Composio tool router. By the end, you'll have a working Givebutter agent that can create a new fundraising campaign for our school, list all recent payouts to our nonprofit account, get details for fund with id fund_abc123 through natural language commands.

This guide will help you understand how to give your LangChain agent real control over a Givebutter account through Composio's Givebutter MCP server.

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

Also integrate Givebutter with

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Givebutter project to Composio
  • Create a Tool Router MCP session for Givebutter
  • Initialize an MCP client and retrieve Givebutter tools
  • Build a LangChain agent that can interact with Givebutter
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

What is the Givebutter MCP server, and what's possible with it?

The Givebutter MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Givebutter account. It provides structured and secure access to your fundraising platform, so your agent can perform actions like creating campaigns, tracking donations, managing contacts, and handling payouts on your behalf.

  • Campaign management and creation: Easily instruct your agent to start new fundraising campaigns, update campaign details, or remove old campaigns when needed.
  • Donation and payout tracking: Ask your agent to retrieve lists of payouts, monitor donation flows, and keep tabs on your fundraising progress in real time.
  • Contact and member administration: Let your agent add, archive, or delete contacts, and fetch lists of campaign members for smooth supporter management.
  • Fund and webhook operations: Direct your agent to get details about specific funds, create or remove webhooks for event notifications, and manage fundraising infrastructure automatically.
  • Automated data cleanup: Empower your agent to archive or delete obsolete contacts, funds, or webhooks, keeping your Givebutter account organized and up to date.

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 step10 STEPS
1

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • 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 @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Givebutter functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Givebutter tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['givebutter']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Givebutter tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Givebutter tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "givebutter-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Givebutter MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Givebutter tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Givebutter related question or task to the agent.\n");

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

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

Here's the complete code to get you started with Givebutter and LangChain:

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['givebutter']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "givebutter-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Givebutter related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

You've successfully built a LangChain agent that can interact with Givebutter through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
TOOLS

Supported Tools

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

Add Contact Tags

Tool to add tags to a contact by contact ID.

Add Household Contact

Tool to add a contact to a household.

Archive Contact

Tool to archive a contact by their ID.

Create Campaign

Tool to create a new campaign.

Create Campaign Ticket

Tool to create a campaign ticket for events or fundraisers.

Create Contact

Tool to create a new contact in Givebutter.

Create Contact Activity

Tool to create a contact activity (e.

Create Discount Code

Tool to create a discount code for a campaign.

Create Fund

Tool to create a new fund.

Create Household

Tool to create a new household in Givebutter.

Create Transaction

Tool to create a new transaction for a campaign.

Create Webhook

Tool to create a new webhook subscription.

Delete Campaign

Tool to delete a campaign by its ID.

Delete Contact Activity

Tool to delete a contact activity by contact ID and activity ID.

Delete Discount Code

Tool to delete a discount code from a campaign.

Delete Fund

Tool to delete a fund by its ID.

Delete Household

Tool to delete a household by its ID.

Delete Webhook

Tool to delete a webhook by its ID.

Get Campaign

Tool to retrieve details for a specific campaign by its ID or code.

Get Campaign Ticket

Tool to retrieve a specific campaign ticket by campaign ID and ticket ID.

Get Contact

Tool to retrieve details of a specific contact by ID.

Get Contact Activity

Tool to retrieve a specific contact activity by contact ID and activity ID.

Get Discount Code

Tool to retrieve details of a specific discount code for a campaign.

Get Fund

Tool to retrieve details of a specific fund by its ID.

Get Household

Tool to retrieve details of a specific household by its ID.

Get Members

Tool to retrieve a paginated list of members for a given campaign.

Get Payouts

Tool to retrieve a list of payouts associated with your account.

Get Plans

Tool to retrieve a list of plans associated with your account.

Get Teams

Tool to retrieve a list of teams for a specific campaign.

Get Tickets

Tool to retrieve a list of tickets.

Get Transactions

Tool to retrieve a list of transactions associated with your account.

Get Webhook

Tool to retrieve a specific webhook by its ID.

Get Webhook Activity

Tool to retrieve a specific webhook activity by its ID.

Get Webhooks

Tool to retrieve all webhooks configured for your account.

List Campaigns

Tool to retrieve a paginated list of campaigns for the authenticated account.

List Campaign Tickets

Tool to retrieve a list of all campaign tickets for a specific campaign.

List Contact Activities

Tool to retrieve all activities for a specific contact.

List Contacts

Tool to retrieve a paginated list of contacts from your Givebutter account.

List Discount Codes

Tool to list all discount codes for a campaign.

List Funds

Tool to list all funds in your Givebutter account.

List Household Contacts

Tool to retrieve all contacts associated with a household.

List Households

Tool to retrieve a list of all households in your account.

List Messages

Tool to retrieve a paginated list of messages.

List Pledges

Tool to retrieve a paginated list of all pledges.

List Webhook Activities

Tool to list all webhook activities for a specific webhook.

Remove Contact Tags

Tool to remove tags from a contact in Givebutter.

Restore Contact

Tool to restore a deleted contact by contact ID.

Sync Contact Tags

Tool to sync tags for a contact.

Update Campaign

Tool to update an existing campaign's details by its ID.

Update Campaign (PUT)

Tool to update a campaign using PUT method.

Update Contact

Tool to update an existing contact's details by contact ID.

Update Contact Activity

Tool to update a contact activity by contact ID and activity ID.

Update Contact (PUT)

Tool to update a contact using PUT method.

Update Discount Code

Tool to update an existing discount code for a campaign.

Update Fund

Tool to update a fund's details by its ID.

Update Household

Tool to update an existing household's details by its ID.

Update Webhook

Tool to update an existing webhook subscription's details.

Update Webhook (PUT)

Tool to update a webhook using PUT method (full replacement).

FAQ

Frequently asked questions

With a standalone Givebutter MCP server, the agents and LLMs can only access a fixed set of Givebutter tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Givebutter and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. LangChain 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 Givebutter tools.

Yes, absolutely. You can configure which Givebutter 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 Givebutter data and credentials are handled as safely as possible.

Start with Givebutter.It takes 30 seconds.

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

Start building