How to integrate Loyverse MCP with Google ADK

This guide walks you through connecting Loyverse to Google ADK 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 Google ADK 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.

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 Google ADK 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 Google ADK 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

TL;DR

Here's what you'll learn:
  • Get a Loyverse account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Loyverse
  • Build an agent that connects to Loyverse through MCP
  • Interact with Loyverse using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

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 step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python
2

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.
3

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Loyverse via MCP
  • python-dotenv loads environment variables
4

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file
5

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management
6

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

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

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_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:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP
7

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["loyverse"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration
8

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Loyverse operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls
9

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

Here's the complete code to get you started with Loyverse and Google ADK:

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

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

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_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.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["loyverse"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Loyverse operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Loyverse with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Loyverse using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Loyverse tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

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.

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. Google ADK 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