How to integrate Loyverse MCP with LangChain

This guide walks you through connecting Loyverse to LangChain using the Composio tool router. By the end, you'll have a working Loyverse agent that can add a new supplier for fresh produce, remove unused category from your inventory, fetch details for a specific employee through natural language commands. This guide will help you understand how to give your LangChain agent real control over a Loyverse account through Composio's Loyverse MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Loyverse logoLoyverse
Api Key

Loyverse is a point-of-sale (POS) platform for small businesses, offering tools for sales, inventory, and customer loyalty. It helps streamline retail operations and boost customer engagement.

58 Tools

Introduction

This guide walks you through connecting Loyverse to LangChain using the Composio tool router. By the end, you'll have a working Loyverse agent that can add a new supplier for fresh produce, remove unused category from your inventory, fetch details for a specific employee through natural language commands.

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

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

Also integrate Loyverse with

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

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

The Loyverse MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Loyverse account. It provides structured and secure access to your retail management data, so your agent can perform actions like managing inventory categories, handling suppliers, retrieving employee info, and accessing payment types on your behalf.

  • Supplier management and automation: Easily create or delete suppliers, streamlining your purchase and vendor workflows without logging into Loyverse manually.
  • Category organization and clean-up: Fetch details of specific inventory categories or remove deprecated ones to keep your product catalog organized and up-to-date.
  • Employee and merchant insights: Retrieve detailed information about employees and your merchant account to support HR, payroll, or business analysis tasks.
  • Discount and payment method lookup: Instantly access details for discounts and payment types, making it simple to verify offers or payment options during sales operations.
  • Authentication and security integration: Fetch OpenID Connect details and JWKS keys, allowing your agent to manage secure authentication and integration workflows.

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 Loyverse 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 Loyverse 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: ['loyverse']
    }
);

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

Configure the agent with the MCP URL

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

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

Create or Update Category

Tool to create a new category or update an existing one.

Create or Update Customer

Tool to create a new customer or update an existing one in Loyverse.

Create or Update Discount

Tool to create or update a single discount.

Create or Update Item

Tool to create a new item or update an existing one in Loyverse inventory.

Create or Update Modifier

Tool to create or update a single modifier with options.

Create or Update POS Device

Tool to create a new POS device or update an existing one.

Create or Update Supplier

Tool to create a new supplier or update an existing one in Loyverse.

Create or Update Tax

Tool to create or update a single tax.

Create or Update Variant

Tool to create or update a single item variant in Loyverse.

Create or Update Webhook

Tool to create a new webhook subscription or update an existing one in Loyverse.

Create Receipt

Tool to create a sales receipt with line items and payments.

Create Refund

Tool to create a refund receipt for a sales receipt.

Delete Category

Tool to delete a single category by ID.

Delete Customer

Tool to delete a single customer by their ID.

Delete Discount

Tool to delete a single discount by ID.

Delete Item

Tool to delete a single item by ID.

Delete Item Image

Tool to delete a single image from an item.

Delete Modifier

Tool to delete a single modifier by its ID.

Delete POS Device

Tool to delete a single POS device by its ID.

Delete Supplier

Tool to delete a specific supplier by ID.

Delete Tax

Tool to delete a single tax by its ID.

Delete Variant

Tool to delete a single item variant by its ID.

Delete Webhook

Tool to delete a single webhook by its ID.

Get Category

Tool to get a single category by ID.

Get Customer

Tool to get a single customer by their ID.

Get Discount

Tool to get a single discount by ID.

Get Employee

Tool to get a single employee by ID.

Get Item

Tool to get a single item by ID including all its variants.

Get JWKS

Tool to fetch JSON Web Key Set for OpenID Connect.

Get Merchant Info

Tool to get merchant information.

Get Modifier

Tool to get a single modifier by ID.

Get OpenID Connect Discovery Document

Tool to retrieve the OpenID Connect discovery document.

Get Payment Type

Tool to get a single payment type by its ID.

Get POS Device

Tool to retrieve details of a specific POS device by its ID.

Get Receipt

Tool to retrieve a single receipt by its receipt number.

Get Store

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

Get Supplier

Tool to get a single supplier by their ID.

Get Tax

Tool to get a single tax by ID.

Get Variant

Tool to get a single item variant by its ID.

Get Webhook

Tool to get a single webhook by its ID.

List Categories

Tool to list categories with optional filtering and pagination.

List Customers

Tool to get a list of customers.

List Discounts

Tool to list discounts.

List Employees (Advanced)

Tool to get a list of employees with advanced filtering options.

List Inventory

Retrieves inventory levels for item variants across stores in the Loyverse system.

List Items

Retrieves a paginated list of items (products) from the Loyverse inventory.

List Modifiers (Enhanced)

Tool to get a list of modifiers sorted by created_at in descending order.

List Payment Types

Tool to list payment types.

List POS Devices

Tool to get a list of POS devices sorted by creation date in descending order.

List Receipts

Tool to retrieve a list of receipts.

List Shifts

Tool to list shifts.

List Stores

Tool to get a list of stores sorted by creation date (newest first).

List Suppliers

Tool to retrieve a list of suppliers.

List Taxes

Tool to get a list of taxes sorted by creation date (newest first).

List Variants

Tool to get a list of item variants sorted by creation date (newest first).

List Webhooks

Tool to list webhooks.

Update Inventory

Tool to batch update inventory levels for item variants at specific stores.

Upload Item Image

Tool to upload a single image for an item.

FRAMEWORKS

How to build Loyverse MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Loyverse MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Loyverse MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Loyverse MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Loyverse MCP with Claude Cowork

Codex logo

Codex

Use Loyverse MCP with Codex

OpenClaw logo

OpenClaw

Use Loyverse MCP with OpenClaw

Hermes logo

Hermes

Use Loyverse MCP with Hermes

CLI logo

CLI

Use Loyverse MCP with CLI

Google ADK logo

Google ADK

Use Loyverse MCP with Google ADK

Vercel AI SDK logo

Vercel AI SDK

Use Loyverse MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Loyverse MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Loyverse MCP with LlamaIndex

CrewAI logo

CrewAI

Use Loyverse MCP with CrewAI

FAQ

Frequently asked questions

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

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

Start with Loyverse.It takes 30 seconds.

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

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

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
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
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
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
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
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
Jerome Leclanche
Co-Founder, Ingram Technologies