Raisely with LlamaIndex

How to integrate Raisely MCP with LlamaIndex

Trusted by

GET STARTED FOR FREE GET A DEMO

30 min · no commitment · see it on your stack

Introduction Also integrate Raisely with TL;DR What is LlamaIndex What is the Raisely MCP server Supported Tools & Triggers Creating MCP Server - Stand-alone vs Composio SDK Step-by-step Guide Complete Code Conclusion How to build Raisely MCP Agent with another framework Explore Other Toolkits FAQ

Connect Raisely without Auth hassles

We manage OAuth, API Key, token refresh, and scopes, you just build.

Try for Free

Introduction

This guide walks you through connecting Raisely to LlamaIndex using the Composio tool router. By the end, you'll have a working Raisely agent that can list all active fundraising campaigns, show all fundraising profiles for a campaign, retrieve recent posts from our raisely site through natural language commands.

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

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

Also integrate Raisely with

OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK Mastra AI CrewAI

TL;DR

Here's what you'll learn:

Set your OpenAI and Composio API keys
Install LlamaIndex and Composio packages
Create a Composio Tool Router session for Raisely
Connect LlamaIndex to the Raisely MCP server
Build a Raisely-powered agent using LlamaIndex
Interact with Raisely through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

ReAct Agent: Reasoning and acting pattern for tool-using agents
MCP Tools: Native support for Model Context Protocol
Context Management: Maintain conversation context across interactions
Async Support: Built for async/await patterns

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

The Raisely MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Raisely account. It provides structured and secure access to your fundraising campaigns, so your agent can perform actions like listing campaigns, managing profiles, retrieving fundraising posts, and overseeing users or webhook subscriptions on your behalf.

Campaign discovery and management: Instantly fetch and list all your Raisely campaigns, making it easy to organize or review ongoing fundraising efforts.
Profile and supporter insights: Retrieve detailed fundraising profiles within any campaign, or list all supporter profiles to track progress and engagement.
Posts and communications access: Pull all posts published on the Raisely platform, allowing your agent to keep you updated or summarize campaign communications.
User administration: Get a comprehensive list of users on your platform or drill into user-specific fundraising profiles, streamlining supporter management.
Webhook and event monitoring: View all configured webhook subscriptions and available event types, helping you automate notifications and stay on top of campaign activity.

Supported Tools & Triggers

Tools

Check Profile URL AvailabilityTool to verify if a profile URL is available for a given campaign and get suggestions if unavailable.

Check User RegistrationTool to check if a user is already registered to a campaign with a specific email address.

Create CampaignTool to create a new campaign in Raisely.

Create Offline DonationTool to record an offline donation in Raisely.

Create Exercise LogTool to create a new exercise log in Raisely.

Create InteractionTool to create a new interaction in Raisely.

Create PostCreate a new post in Raisely.

Create Promo CodeTool to create a new promo code in Raisely.

Create WebhookTool to add a new webhook to your Raisely account.

Delete Exercise LogTool to delete an exercise log from Raisely.

Delete InteractionTool to delete an existing custom interaction from Raisely.

Delete Raisely PostTool to delete a post from the Raisely platform.

Delete ProfileTool to archive a profile in Raisely.

Delete Raisely WebhookTool to delete a webhook from the Raisely platform.

Retrieve Raisely API Documentation SummaryRetrieve a summary of the Raisely API documentation including metadata and sample endpoints.

Authenticate TokenAuthenticate a token to confirm it's valid and check the logged-in user.

Get Available EventsTool to retrieve a list of available Raisely webhook events.

Get CampaignTool to retrieve a specific campaign from Raisely.

Get Campaign ProfileTool to retrieve the campaign profile for a Raisely campaign.

Get campaignsTool to retrieve a paginated list of campaigns from Raisely.

List Campaign ProfilesList all fundraising profiles in a Raisely campaign.

Get Exercise LogRetrieve a specific exercise log by UUID from the Raisely platform.

Get InteractionTool to retrieve a specific interaction from Raisely by its UUID.

Get PostTool to retrieve a specific post from the Raisely fundraising platform.

Get ProfileRetrieves a specific fundraising profile from Raisely by UUID or path.

Raisely Get ProfilesRetrieves a paginated list of fundraising profiles for a Raisely campaign.

Get UserTool to retrieve a specific user from Raisely by UUID.

Get User ProfilesTool to retrieve all profiles associated with a specific user.

Get UsersRetrieve a paginated list of users from the Raisely platform.

List Campaign DonationsTool to retrieve donations from a specific campaign in Raisely.

List Campaign ProductsRetrieves all products available in a Raisely campaign.

List Campaign SubscriptionsList all subscriptions for a specific Raisely campaign.

Raisely List DonationsRetrieve donations from Raisely.

Raisely List Exercise LogsRetrieve exercise logs from Raisely.

List Interaction CategoriesTool to retrieve all interaction categories in the organisation from Raisely.

List InteractionsTool to retrieve all interactions from Raisely.

List OrdersTool to retrieve all orders in a campaign from Raisely.

List PostsTool to retrieve a list of posts you've previously created on Raisely.

List Profile DonationsRetrieves a paginated list of donations for a specific fundraising profile from Raisely.

List Profile MembersRetrieves a paginated list of all members belonging to a team profile in Raisely.

List Profile PostsList all posts created by a specific profile in Raisely.

List Promo CodesTool to retrieve all promo codes in a campaign from Raisely.

List SegmentsTool to retrieve all segments from Raisely.

Raisely List Subscriptions 2Tool to retrieve subscriptions from Raisely.

List TagsTool to retrieve the list of tags from Raisely.

List User DonationsRetrieves a paginated list of donations for a specific user from Raisely.

List User InteractionsRetrieves all interactions for a given user from Raisely.

Raisely List User SubscriptionsRetrieve subscriptions for a specific user from Raisely.

List WebhooksTool to retrieve the list of webhooks configured for a campaign.

Move DonationTool to move a donation to a different profile in Raisely.

Logout from RaiselyTool to invalidate the current user's token and log out.

Create UserCreate a new user in Raisely.

Update CampaignTool to update an existing campaign in Raisely.

Update Campaign ConfigTool to update a specific configuration attribute for a campaign in Raisely.

Update Exercise LogUpdate an existing exercise log in Raisely.

Update PostTool to update a specified post in Raisely.

Update ProfileUpdates a specific profile in Raisely.

Update UserTool to update a specified user in Raisely.

Update WebhookTool to update a specified webhook in Raisely.

Upload Campaign MediaTool to upload one or more files to a campaign's media library in Raisely.

Upsert UserTool to upsert a user record in Raisely, optionally tagging and creating an interaction.

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:

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

Step-by-step Guide

Prerequisites

Before you begin, make sure you have:

Python 3.8/Node 16 or higher installed
A Composio account with the API key
An OpenAI API key
A Raisely account and project
Basic familiarity with async Python/Typescript

Getting API Keys for OpenAI, Composio, and Raisely

OpenAI API key (OPENAI_API_KEY)

Go to the OpenAI dashboard
Create an API key if you don't have one
Assign it to OPENAI_API_KEY in .env

Composio API key and user ID

Log into the Composio dashboard
Copy your API key from Settings
- Use this as COMPOSIO_API_KEY
Pick a stable user identifier (email or ID)
- Use this as COMPOSIO_USER_ID

Installing dependencies

pip install composio-llamaindex llama-index llama-index-llms-openai llama-index-tools-mcp python-dotenv

Create a new Python project and install the necessary dependencies:

composio-llamaindex: Composio's LlamaIndex integration
llama-index: Core LlamaIndex framework
llama-index-llms-openai: OpenAI LLM integration
llama-index-tools-mcp: MCP client for LlamaIndex
python-dotenv: Environment variable management

Set environment variables

bash

OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

Authenticate with OpenAI's GPT-5 model
Connect to Composio's Tool Router
Identify your Composio user session for Raisely access

Import modules

import asyncio
import os
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

Create a new file called raisely_llamaindex_agent.py and import the required modules:

Key imports:

asyncio: For async/await support
Composio: Main client for Composio services
LlamaIndexProvider: Adapts Composio tools for LlamaIndex
ReActAgent: LlamaIndex's reasoning and action agent
BasicMCPClient: Connects to MCP endpoints
McpToolSpec: Converts MCP tools to LlamaIndex format

Load environment variables and initialize Composio

OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_API_KEY is not set in the environment")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment")

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

Create a Tool Router session and build the agent function

async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["raisely"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")

    description = "An agent that uses Composio Tool Router MCP tools to perform Raisely actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Raisely actions.
    """
    return ReActAgent(tools=tools, llm=llm, description=description, system_prompt=system_prompt, verbose=True)

What's happening here:

We create a Composio client using your API key and configure it with the LlamaIndex provider
We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, raisely)
The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
LlamaIndex will connect to this endpoint to dynamically discover and use the available Raisely tools.
The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.

Create an interactive chat loop

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

What's happening here:

We're creating a direct terminal interface to chat with your Raisely database
The LLM's responses are streamed to the CLI for faster interaction.
The agent uses context to maintain conversation history
You can type 'quit' or 'exit' to stop the chat loop gracefully
Agent responses and any errors are displayed in a clear, readable format

Define the main entry point

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")

What's happening here:

We're orchestrating the entire application flow
The agent gets built with proper error handling
Then we kick off the interactive chat loop so you can start talking to Raisely

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Raisely, then start asking questions.

Complete Code

Here's the complete code to get you started with Raisely and LlamaIndex:

import asyncio
import os
import signal
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_API_KEY is not set")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")

async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["raisely"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")
    description = "An agent that uses Composio Tool Router MCP tools to perform Raisely actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Raisely actions.
    """
    return ReActAgent(
        tools=tools,
        llm=llm,
        description=description,
        system_prompt=system_prompt,
        verbose=True,
    );

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")

Conclusion

You've successfully connected Raisely to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:

Tool Router dynamically exposes Raisely tools through an MCP endpoint
LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
The agent becomes more capable without increasing prompt size
Async Python provides clean, efficient execution of agent workflows

You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.

How to build Raisely MCP Agent with another framework

OpenAI Agents SDK

Use Raisely MCP with OpenAI Agents SDK

Claude Agent SDK

Use Raisely MCP with Claude Agent SDK

Claude Code

Use Raisely MCP with Claude Code

Claude Cowork

Use Raisely MCP with Claude Cowork

Codex

Use Raisely MCP with Codex

OpenClaw

Use Raisely MCP with OpenClaw

Hermes

Use Raisely MCP with Hermes

CLI

Use Raisely MCP with CLI

Google ADK

Use Raisely MCP with Google ADK

LangChain

Use Raisely MCP with LangChain

Vercel AI SDK

Use Raisely MCP with Vercel AI SDK

Mastra AI

Use Raisely MCP with Mastra AI

CrewAI

Use Raisely MCP with CrewAI

Explore Other Toolkits

Gmail

Oauth2

Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable.

Google Calendar

Oauth2

Google Calendar is a time management service for scheduling meetings, events, and reminders. It streamlines personal and team organization with integrated notifications and sharing options.

Google Drive

Oauth2

Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices.

TOOLKIT MARKETPLACE

FAQ

What are the differences in Tool Router MCP and Raisely MCP?

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

Can I use Tool Router MCP with LlamaIndex?

Yes, you can. LlamaIndex 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 Raisely tools.

Can I manage the permissions and scopes for Raisely while using Tool Router?

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

Used by agents from

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for free Get a demo↗

Harsha GaddipatiCo-founder, Slashy

Karan skipped his own birthday party to fix our critical issue. It was 10 pm and he diverted his Waymo to help us instead. This really sets the bar, shows you the commitment you need to have when users rely on your software.

Abhi AryaCo-founder, Opennote

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it has immensely helped in keeping new users on the platform.

Nirman DaveCEO, Zams

We chose Composio over Pipedream because it delivered depth where it mattered. It supported niche tools and tricky edge cases that other platforms simply ignored. Giving us confidence to scale without compromising.

Ryan YuFounder, Extra Thursday

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down in the complexities of managing agent auth would have been a death sentence for Extra Thursday.

Tomisin JenrolaFounder & CEO, SwarmZero

Before partnering with Composio, adding tool integrations was a slow, resource-intensive process. Each integration could take weeks or months of engineering time, and maintaining them meant constantly keeping up with API changes.

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

How to integrate Raisely MCP with LlamaIndex

Table of Contents

Connect Raisely without Auth hassles

Introduction

Also integrate Raisely with

TL;DR

What is LlamaIndex?

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

Supported Tools & Triggers

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

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI, Composio, and Raisely

Installing dependencies

Set environment variables

Import modules

Load environment variables and initialize Composio

Create a Tool Router session and build the agent function

Create an interactive chat loop

Define the main entry point

Run the agent

Complete Code

Conclusion

How to build Raisely MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

Mastra AI

CrewAI

Explore Other Toolkits

Gmail

Google Calendar

Google Drive

FAQ

What are the differences in Tool Router MCP and Raisely MCP?

Can I use Tool Router MCP with LlamaIndex?

Can I manage the permissions and scopes for Raisely while using Tool Router?

How safe is my data with Composio Tool Router?

Used by agents from

Never worry about agent reliability