How to integrate Api bible MCP with LangChain

This guide walks you through connecting Api bible to LangChain 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 LangChain 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.

Get started for free Get a demo

Api bible

Api Key

API.Bible is a developer platform for Scripture content and passage search. Easily integrate Bible verses and translations into your apps or chatbots.

19 Tools

Managed auth

Connect Api bible without auth hassles

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

Try for free

Introduction

This guide will help you understand how to give your LangChain 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 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
Connect your Api bible project to Composio
Create a Tool Router MCP session for Api bible
Initialize an MCP client and retrieve Api bible tools
Build a LangChain agent that can interact with Api bible
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 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.

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

Step by step10 STEPS

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

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

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

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

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 Api bible functionality through MCP

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 Api bible tools
Validating that COMPOSIO_USER_ID is also set before proceeding

Create a Tool Router session

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

const url = session.mcp.url;

What's happening:

We're creating a Tool Router session that gives your agent access to Api bible 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 Api bible tools as needed

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "api_bible-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 Api bible MCP server via HTTP
The client is configured with a name and the URL from our Tool Router session
getTools() retrieves all available Api bible tools that the agent can use
We're creating a LangChain agent using the GPT-5 model

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 Api bible 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

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 Api bible 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: ['api_bible']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "api_bible-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 Api bible 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 Api bible 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 Api bible action and event your agent gets out of the box.

Get All Books

Retrieve all books for a specific Bible version.

Get Audio Bible by ID

Tool to retrieve details of a specific audio Bible by its ID.

Get Audio Book

Tool to retrieve a single audio Book object for a given audio Bible ID and book ID.

Get Audio Chapter

Tool to retrieve a single audio chapter with mp3 resource URL.

Get Bible by ID

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

Get Book

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

Get Chapter

Retrieve a complete chapter with all verses from a Bible version.

Get Passage

Retrieve a Bible passage by ID.

Get Section

Retrieve detailed content for a Bible section by ID.

Get Sections

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

Get Supported Bible Versions

Retrieve a list of available Bible versions (translations) from API.

Get Verse

Retrieve a specific Bible verse by ID.

List Audio Bibles

Tool to retrieve an array of audio Bible objects authorized for the current API Key.

List Audio Books

Tool to retrieve all books for a specific audio Bible version.

List Audio Chapters

Tool to retrieve a list of audio chapters for a specific book in an audio Bible version.

List Chapters

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

List Chapter Sections

Tool to retrieve an array of section objects for a specific chapter in a Bible version.

List Verses

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

Search Bible Verses

Search for Bible verses containing specified keywords or passage references.

FRAMEWORKS

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

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

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

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.

Certifier

Api Key

Certifier is a platform for creating, managing, and issuing digital certificates and credentials. Organizations use it to automate and secure the entire credentialing process.

FAQ

Frequently asked questions

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.

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 Api bible tools.

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.

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.

Start with Api bible.It takes 30 seconds.

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

Start building

Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREE BOOK A DEMO

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

Harsha Gaddipati

Co-founder, Slashy

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's immensely helped keep new users on the platform.

Abhi Arya

Co-founder, Opennote

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

Nirman Dave

CEO, Zams

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

Ryan Yu

Founder, Extra Thursday

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

Tomisin Jenrola

Founder & CEO, SwarmZero

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.

Jerome Leclanche

Co-Founder, Ingram Technologies

How to integrate Api bible MCP with LangChain

Connect Api bible without auth hassles

Introduction

Also integrate Api bible with

TL;DR

What is LangChain?

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

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

Initialize Composio client

Create a Tool Router session

Configure the agent with the MCP URL

Set up interactive chat interface

Run the application

Complete Code

Conclusion

Supported Tools

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

Vercel AI SDK

Mastra AI

LlamaIndex

CrewAI

Explore Other Toolkits

Canvas

Accredible certificates

Blackboard

Certifier

Frequently asked questions

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

Can I use Tool Router MCP with LangChain?+

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

How safe is my data with Composio Tool Router?+

Start with Api bible.It takes 30 seconds.

Teams ship real agents on Composio