How to integrate OneSimpleAPI MCP with LangChain

This guide walks you through connecting OneSimpleAPI to LangChain using the Composio tool router. By the end, you'll have a working OneSimpleAPI agent that can create qr codes, generate pdfs, capture screenshots, convert currencies, and create short urls through natural language commands. This guide will help you understand how to give your LangChain agent real control over a OneSimpleAPI account through Composio's OneSimpleAPI MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

OneSimpleAPI logoOneSimpleAPI
Api Key

OneSimpleAPI is a utility API platform for web content, images, PDFs, QR codes, URL tools, validation, exchange rates, and file management. It gives developers one simple API key for many common backend tasks.

15 Tools

Introduction

This guide walks you through connecting OneSimpleAPI to LangChain using the Composio tool router. By the end, you'll have a working OneSimpleAPI agent that can create qr codes, generate pdfs, capture screenshots, convert currencies, and create short urls through natural language commands.

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

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

Also integrate OneSimpleAPI with

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your OneSimpleAPI project to Composio
  • Create a Tool Router MCP session for OneSimpleAPI
  • Initialize an MCP client and retrieve OneSimpleAPI tools
  • Build a LangChain agent that can interact with OneSimpleAPI
  • 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 OneSimpleAPI MCP server, and what's possible with it?

The OneSimpleAPI MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your OneSimpleAPI account. It provides structured and secure access to web, image, document, URL, validation, currency, and file utilities, so your agent can capture webpages, transform images, generate PDFs and QR codes, manage short links, and validate content on your behalf.

  • Web captures and PDF creation: Have your agent capture screenshots of webpages or raw HTML, or turn that content into hosted PDF files.
  • Image inspection and transformation: Let the agent inspect image dimensions and metadata, then resize, crop, rotate, flip, filter, add borders, or optimize images.
  • QR codes and short links: Direct your agent to generate hosted QR codes, create configurable short links, expand shortened links, and review link click statistics.
  • Content and data checks: Instruct your agent to analyze text readability and sentiment, validate email addresses, convert colors, and inspect image details.
  • Currency, pricing, and file management: Have your agent convert currencies, calculate localized pricing discounts, list generated files, and delete files you no longer need.

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 OneSimpleAPI 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 OneSimpleAPI 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: ['onesimpleapi']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to OneSimpleAPI 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 OneSimpleAPI tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "onesimpleapi-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 OneSimpleAPI MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available OneSimpleAPI 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 OneSimpleAPI 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 OneSimpleAPI 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: ['onesimpleapi']
        }
    );

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

Analyze Readability

Analyze text for readability, grade level, reading time, difficult-word counts, and sentiment.

Calculate PPP Discount

Calculate a purchasing-power-parity discount and localized price between an origin and a destination country.

Capture Screenshot

Capture a webpage URL or raw HTML as a hosted screenshot and return its URL and rendering metadata.

Convert Currency

Convert an amount between supported currencies and return the converted value and exchange rate.

Create Short URL

Create a OneSimpleAPI short URL with optional one-time-use, redirect, query-forwarding, and active-date controls.

Delete File

Delete a generated OneSimpleAPI file by its hosted URL and return the updated file record.

Expand Short URL

Resolve a shortened URL and return its final URL, redirect count, and redirect trace.

Generate or Convert Color

Generate a deterministic color palette from text or convert a supplied color into HEX, RGB, HSL, and related palette values.

Generate PDF

Generate a PDF from either a webpage URL or raw HTML and return the hosted PDF URL and page metadata.

Generate QR Code

Generate a hosted PNG or SVG QR code for a message and return its URL.

Get Image Information

Extract dimensions, image metadata, EXIF camera fields, and available GPS details from an image URL.

List Files

Return one page of generated files owned by the connected account, optionally filtered by live or deleted status.

List Short URLs

Return one page of OneSimpleAPI short URLs and their click statistics.

Transform Image

Resize, crop, rotate, flip, filter, border, optimize, and host an image, returning the generated image URL and metadata.

Validate Email

Validate an email address and assess its domain, MX records, deliverability, disposability, role status, and registration safety.

FAQ

Frequently asked questions

With a standalone OneSimpleAPI MCP server, the agents and LLMs can only access a fixed set of OneSimpleAPI tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from OneSimpleAPI 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 OneSimpleAPI tools.

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

Start with OneSimpleAPI.It takes 30 seconds.

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

Start building