Api bible with AutoGen

How to integrate Api bible MCP with Autogen

Trusted by

GET STARTED FOR FREE GET A DEMO

30 min · no commitment · see it on your stack

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

Connect Api bible 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 Api bible to AutoGen using the Composio tool router. By the end, you'll have a working Api bible agent that can list all books in the old testament, find verses about forgiveness in niv, get section breakdown for genesis in esv through natural language commands.

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

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

Also integrate Api bible with

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

TL;DR

Here's what you'll learn:

Get and set up your OpenAI and Composio API keys
Install the required dependencies for Autogen and Composio
Initialize Composio and create a Tool Router session for Api bible
Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams
Configure an Autogen AssistantAgent that can call Api bible tools
Run a live chat loop where you ask the agent to perform Api bible operations

What is AutoGen?

Autogen is a framework for building multi-agent conversational AI systems from Microsoft. It enables you to create agents that can collaborate, use tools, and maintain complex workflows.

Key features include:

Multi-Agent Systems: Build collaborative agent workflows
MCP Workbench: Native support for Model Context Protocol tools
Streaming HTTP: Connect to external services through streamable HTTP
AssistantAgent: Pre-built agent class for tool-using assistants

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

The Api bible MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Api bible account. It provides structured and secure access to Scripture content, so your agent can perform actions like searching verses, retrieving books, exploring Bible versions, and fetching specific sections or metadata on your behalf.

Comprehensive verse search: Instantly ask your agent to find Bible verses containing specific words or topics across supported translations.
Explore all books of the Bible: Retrieve a full catalog of every biblical book, making it easy to browse or reference any part of Scripture.
List and select Bible translations: Have your agent list all available Bible versions so you can choose the translation that fits your needs.
Detailed section and passage retrieval: Fetch detailed content for any section or passage once you know the Bible and book IDs—perfect for study or quotation.
Access Bible version metadata: Get in-depth metadata about any specific Bible edition, including language, abbreviation, and publisher details.

Supported Tools & Triggers

Tools

Get All BooksRetrieve all books for a specific Bible version.

Get Audio Bible by IDTool to retrieve details of a specific audio Bible by its ID.

Get Audio BookTool to retrieve a single audio Book object for a given audio Bible ID and book ID.

Get Audio ChapterTool to retrieve a single audio chapter with mp3 resource URL.

Get Bible by IDTool to retrieve details of a specific Bible version by its ID.

Get BookTool to retrieve a single Book object for a given Bible version and book ID.

Get ChapterRetrieve a complete chapter with all verses from a Bible version.

Get PassageRetrieve a Bible passage by ID.

Get SectionRetrieve detailed content for a Bible section by ID.

Get SectionsTool to retrieve a list of sections for a specific book in a Bible version.

Get Supported Bible VersionsRetrieve a list of available Bible versions (translations) from API.

Get VerseRetrieve a specific Bible verse by ID.

List Audio BiblesTool to retrieve an array of audio Bible objects authorized for the current API Key.

List Audio BooksTool to retrieve all books for a specific audio Bible version.

List Audio ChaptersTool to retrieve a list of audio chapters for a specific book in an audio Bible version.

List ChaptersTool to retrieve an array of Chapter objects for a given Bible version and book.

List Chapter SectionsTool to retrieve an array of section objects for a specific chapter in a Bible version.

List VersesTool to retrieve an array of verses for a specific chapter in a Bible version.

Search Bible VersesSearch for Bible verses containing specified keywords or passage references.

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

You will need:

A Composio API key
An OpenAI API key (used by Autogen's OpenAIChatCompletionClient)
A Api bible account you can connect to Composio
Some basic familiarity with Autogen and Python async

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.

Install dependencies

bash

pip install composio python-dotenv
pip install autogen-agentchat autogen-ext-openai autogen-ext-tools

Install Composio, Autogen extensions, and dotenv.

What's happening:

composio connects your agent to Api bible via MCP
autogen-agentchat provides the AssistantAgent class
autogen-ext-openai provides the OpenAI model client
autogen-ext-tools provides MCP workbench support

Set up environment variables

bash

COMPOSIO_API_KEY=your-composio-api-key
OPENAI_API_KEY=your-openai-api-key
USER_ID=your-user-identifier@example.com

Create a .env file in your project folder.

What's happening:

COMPOSIO_API_KEY is required to talk to Composio
OPENAI_API_KEY is used by Autogen's OpenAI client
USER_ID is how Composio identifies which user's Api bible connections to use

Import dependencies and create Tool Router session

python

import asyncio
import os
from dotenv import load_dotenv
from composio import Composio

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams

load_dotenv()

async def main():
    # Initialize Composio and create a Api bible session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["api_bible"]
    )
    url = session.mcp.url

What's happening:

load_dotenv() reads your .env file
Composio(api_key=...) initializes the SDK
create(...) creates a Tool Router session that exposes Api bible tools
session.mcp.url is the MCP endpoint that Autogen will connect to

Configure MCP parameters for Autogen

python

# Configure MCP server parameters for Streamable HTTP
server_params = StreamableHttpServerParams(
    url=url,
    timeout=30.0,
    sse_read_timeout=300.0,
    terminate_on_close=True,
    headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
)

Autogen expects parameters describing how to talk to the MCP server. That is what StreamableHttpServerParams is for.

What's happening:

url points to the Tool Router MCP endpoint from Composio
timeout is the HTTP timeout for requests
sse_read_timeout controls how long to wait when streaming responses
terminate_on_close=True cleans up the MCP server process when the workbench is closed

Create the model client and agent

python

# Create model client
model_client = OpenAIChatCompletionClient(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY")
)

# Use McpWorkbench as context manager
async with McpWorkbench(server_params) as workbench:
    # Create Api bible assistant agent with MCP tools
    agent = AssistantAgent(
        name="api_bible_assistant",
        description="An AI assistant that helps with Api bible operations.",
        model_client=model_client,
        workbench=workbench,
        model_client_stream=True,
        max_tool_iterations=10
    )

What's happening:

OpenAIChatCompletionClient wraps the OpenAI model for Autogen
McpWorkbench connects the agent to the MCP tools
AssistantAgent is configured with the Api bible tools from the workbench

Run the interactive chat loop

python

print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Api bible related question or task to the agent.\n")

# Conversation loop
while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    print("\nAgent is thinking...\n")

    # Run the agent with streaming
    try:
        response_text = ""
        async for message in agent.run_stream(task=user_input):
            if hasattr(message, "content") and message.content:
                response_text = message.content

        # Print the final response
        if response_text:
            print(f"Agent: {response_text}\n")
        else:
            print("Agent: I encountered an issue processing your request.\n")

    except Exception as e:
        print(f"Agent: Sorry, I encountered an error: {str(e)}\n")

What's happening:

The script prompts you in a loop with You:
Autogen passes your input to the model, which decides which Api bible tools to call via MCP
agent.run_stream(...) yields streaming messages as the agent thinks and calls tools
Typing exit, quit, or bye ends the loop

Complete Code

Here's the complete code to get you started with Api bible and AutoGen:

python

import asyncio
import os
from dotenv import load_dotenv
from composio import Composio

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams

load_dotenv()

async def main():
    # Initialize Composio and create a Api bible session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["api_bible"]
    )
    url = session.mcp.url

    # Configure MCP server parameters for Streamable HTTP
    server_params = StreamableHttpServerParams(
        url=url,
        timeout=30.0,
        sse_read_timeout=300.0,
        terminate_on_close=True,
        headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
    )

    # Create model client
    model_client = OpenAIChatCompletionClient(
        model="gpt-5",
        api_key=os.getenv("OPENAI_API_KEY")
    )

    # Use McpWorkbench as context manager
    async with McpWorkbench(server_params) as workbench:
        # Create Api bible assistant agent with MCP tools
        agent = AssistantAgent(
            name="api_bible_assistant",
            description="An AI assistant that helps with Api bible operations.",
            model_client=model_client,
            workbench=workbench,
            model_client_stream=True,
            max_tool_iterations=10
        )

        print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
        print("Ask any Api bible related question or task to the agent.\n")

        # Conversation loop
        while True:
            user_input = input("You: ").strip()

            if user_input.lower() in ['exit', 'quit', 'bye']:
                print("\nGoodbye!")
                break

            if not user_input:
                continue

            print("\nAgent is thinking...\n")

            # Run the agent with streaming
            try:
                response_text = ""
                async for message in agent.run_stream(task=user_input):
                    if hasattr(message, 'content') and message.content:
                        response_text = message.content

                # Print the final response
                if response_text:
                    print(f"Agent: {response_text}\n")
                else:
                    print("Agent: I encountered an issue processing your request.\n")

            except Exception as e:
                print(f"Agent: Sorry, I encountered an error: {str(e)}\n")

if __name__ == "__main__":
    asyncio.run(main())

Conclusion

You now have an Autogen assistant wired into Api bible through Composio's Tool Router and MCP. From here you can:

Add more toolkits to the toolkits list, for example notion or hubspot
Refine the agent description to point it at specific workflows
Wrap this script behind a UI, Slack bot, or internal tool

Once the pattern is clear for Api bible, you can reuse the same structure for other MCP-enabled apps with minimal code changes.

How to build Api bible MCP Agent with another framework

OpenAI Agents SDK

Use Api bible MCP with OpenAI Agents SDK

Claude Agent SDK

Use Api bible MCP with Claude Agent SDK

Claude Code

Use Api bible MCP with Claude Code

Claude Cowork

Use Api bible MCP with Claude Cowork

Codex

Use Api bible MCP with Codex

OpenClaw

Use Api bible MCP with OpenClaw

Hermes

Use Api bible MCP with Hermes

CLI

Use Api bible MCP with CLI

Google ADK

Use Api bible MCP with Google ADK

LangChain

Use Api bible MCP with LangChain

Vercel AI SDK

Use Api bible MCP with Vercel AI SDK

Mastra AI

Use Api bible MCP with Mastra AI

LlamaIndex

Use Api bible MCP with LlamaIndex

CrewAI

Use Api bible MCP with CrewAI

Explore Other Toolkits

Canvas

Oauth2Api Key

Canvas is a learning management system for online courses, assignments, grading, and collaboration. It's trusted by educators and students to streamline virtual classrooms and enhance digital learning.

Accredible certificates

Api Key

Accredible Certificates is a platform for creating and managing digital certificates, badges, and blockchain credentials. It streamlines issuing, tracking, and verifying professional achievements for organizations of any size.

Blackboard

Oauth2

Blackboard is a digital learning platform for higher education and schools, offering tools to manage courses, track engagement, and deliver interactive content. It helps institutions improve student outcomes through actionable analytics and in-app guidance.

TOOLKIT MARKETPLACE

FAQ

What are the differences in Tool Router MCP and Api bible MCP?

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

Can I use Tool Router MCP with Autogen?

Yes, you can. Autogen 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 Api bible tools.

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

Yes, absolutely. You can configure which Api bible 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 Api bible 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 Api bible MCP with Autogen

Table of Contents

Connect Api bible without Auth hassles

Introduction

Also integrate Api bible with

TL;DR

What is AutoGen?

What is the Api bible 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 and Composio

Install dependencies

Set up environment variables

Import dependencies and create Tool Router session

Configure MCP parameters for Autogen

Create the model client and agent

Run the interactive chat loop

Complete Code

Conclusion

How to build Api bible 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

LlamaIndex

CrewAI

Explore Other Toolkits

Canvas

Accredible certificates

Blackboard

FAQ

What are the differences in Tool Router MCP and Api bible MCP?

Can I use Tool Router MCP with Autogen?

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

How safe is my data with Composio Tool Router?

Used by agents from

Never worry about agent reliability