# How to integrate Loyverse MCP with CrewAI

```json
{
  "title": "How to integrate Loyverse MCP with CrewAI",
  "toolkit": "Loyverse",
  "toolkit_slug": "loyverse",
  "framework": "CrewAI",
  "framework_slug": "crew-ai",
  "url": "https://composio.dev/toolkits/loyverse/framework/crew-ai",
  "markdown_url": "https://composio.dev/toolkits/loyverse/framework/crew-ai.md",
  "updated_at": "2026-05-12T10:18:01.247Z"
}
```

## Introduction

This guide walks you through connecting Loyverse to CrewAI 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 CrewAI 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 SDK](https://composio.dev/toolkits/loyverse/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/loyverse/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/loyverse/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/loyverse/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/loyverse/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/loyverse/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/loyverse/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/loyverse/framework/cli)
- [Google ADK](https://composio.dev/toolkits/loyverse/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/loyverse/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/loyverse/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/loyverse/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/loyverse/framework/llama-index)

## TL;DR

Here's what you'll learn:
- Get a Composio API key and configure your Loyverse connection
- Set up CrewAI with an MCP enabled agent
- Create a Tool Router session or standalone MCP server for Loyverse
- Build a conversational loop where your agent can execute Loyverse operations

## What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.
Key features include:
- Agent Roles: Define specialized agents with specific goals and backstories
- Task Management: Create tasks with clear descriptions and expected outputs
- Crew Orchestration: Combine agents and tasks into collaborative workflows
- MCP Integration: Connect to external tools through Model Context Protocol

## 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.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `LOYVERSE_CREATE_OR_UPDATE_CATEGORY` | Create or Update Category | Tool to create a new category or update an existing one. If the ID field is provided, the category will be updated; otherwise, a new category is created. |
| `LOYVERSE_CREATE_OR_UPDATE_CUSTOMER` | Create or Update Customer | Tool to create a new customer or update an existing one in Loyverse. Use when you need to add customer records or modify customer information. If the 'id' field is provided, it will update the existing customer; otherwise, it creates a new customer. |
| `LOYVERSE_CREATE_OR_UPDATE_DISCOUNT` | Create or Update Discount | Tool to create or update a single discount. Use when creating new discounts or modifying existing ones. Supports FIXED_PERCENT (percentage-based), FIXED_AMOUNT (fixed amount), and VARIABLE discount types. |
| `LOYVERSE_CREATE_OR_UPDATE_ITEM` | Create or Update Item | Tool to create a new item or update an existing one in Loyverse inventory. Include the item ID to update an existing item, or omit it to create a new one. |
| `LOYVERSE_CREATE_OR_UPDATE_MODIFIER` | Create or Update Modifier | Tool to create or update a single modifier with options. If an ID is included in the request, it will update the existing modifier; otherwise, it creates a new one. |
| `LOYVERSE_CREATE_OR_UPDATE_POS_DEVICE` | Create or Update POS Device | Tool to create a new POS device or update an existing one. If the request includes an ID, it updates the device; otherwise, it creates a new one. |
| `LOYVERSE_CREATE_OR_UPDATE_SUPPLIER` | Create or Update Supplier | Tool to create a new supplier or update an existing one in Loyverse. Use when you need to register suppliers before purchases or modify supplier information. If the 'id' field is provided, it will update the existing supplier; otherwise, it creates a new supplier. |
| `LOYVERSE_CREATE_OR_UPDATE_TAX` | Create or Update Tax | Tool to create or update a single tax. If the ID field is provided, the tax will be updated; otherwise, a new tax is created. Use when setting up tax rates for stores. |
| `LOYVERSE_CREATE_OR_UPDATE_VARIANT` | Create or Update Variant | Tool to create or update a single item variant in Loyverse. Use when you need to add product variations (like size, color) or modify existing variant details. If variant_id is provided, it updates the existing variant; otherwise, it creates a new one. Note: The parent item must have option names defined before variants can be created. |
| `LOYVERSE_CREATE_OR_UPDATE_WEBHOOK` | Create or Update Webhook | Tool to create a new webhook subscription or update an existing one in Loyverse. Use when you need to subscribe to events like items.update, inventory.update, receipts.create, customers.update, or shifts.create. If the 'id' field is provided, it will update the existing webhook; otherwise, it creates a new webhook. |
| `LOYVERSE_CREATE_RECEIPT` | Create Receipt | Tool to create a sales receipt with line items and payments. Use when you need to record a sale transaction in Loyverse. |
| `LOYVERSE_CREATE_REFUND` | Create Refund | Tool to create a refund receipt for a sales receipt. Use when you need to process a refund for items from a previous sale. Only supports refunds for receipts paid by a single payment method (not integrated payments). |
| `LOYVERSE_DELETE_CATEGORY` | Delete Category | Tool to delete a single category by ID. Use when you need to remove an unused or deprecated category. |
| `LOYVERSE_DELETE_CUSTOMER` | Delete Customer | Tool to delete a single customer by their ID. Use after confirming the customer ID to remove an existing customer. |
| `LOYVERSE_DELETE_DISCOUNT` | Delete Discount | Tool to delete a single discount by ID. Use after confirming the discount ID to remove an existing discount. |
| `LOYVERSE_DELETE_ITEM` | Delete Item | Tool to delete a single item by ID. Use when you need to remove an item from the inventory. |
| `LOYVERSE_DELETE_ITEM_IMAGE` | Delete Item Image | Tool to delete a single image from an item. Use when you need to remove the image associated with a specific item. |
| `LOYVERSE_DELETE_MODIFIER` | Delete Modifier | Tool to delete a single modifier by its ID. Use when you need to remove an existing modifier. |
| `LOYVERSE_DELETE_POS_DEVICE` | Delete POS Device | Tool to delete a single POS device by its ID. Use when you need to remove a POS device from the system. |
| `LOYVERSE_DELETE_SUPPLIER` | Delete Supplier | Tool to delete a specific supplier by ID. Use after confirming the supplier ID to remove an existing supplier. |
| `LOYVERSE_DELETE_TAX` | Delete Tax | Tool to delete a single tax by its ID. Use when you need to remove an existing tax configuration. |
| `LOYVERSE_DELETE_VARIANT` | Delete Variant | Tool to delete a single item variant by its ID. Use after confirming the variant ID to remove an existing variant. |
| `LOYVERSE_DELETE_WEBHOOK` | Delete Webhook | Tool to delete a single webhook by its ID. Use when you need to remove a webhook configuration. |
| `LOYVERSE_GET_CATEGORY` | Get Category | Tool to get a single category by ID. Use when you need to fetch details of an existing category in Loyverse. |
| `LOYVERSE_GET_CUSTOMER` | Get Customer | Tool to get a single customer by their ID. Use when you need to fetch details of a specific customer. |
| `LOYVERSE_GET_DISCOUNT` | Get Discount | Tool to get a single discount by ID. Use after confirming the discount ID to retrieve its details. |
| `LOYVERSE_GET_EMPLOYEE` | Get Employee | Tool to get a single employee by ID. Use after confirming the employee ID to fetch its details. |
| `LOYVERSE_GET_ITEM` | Get Item | Tool to get a single item by ID including all its variants. Use when you need detailed information about a specific item from the Loyverse inventory. |
| `LOYVERSE_GET_JWKS` | Get JWKS | Tool to fetch JSON Web Key Set for OpenID Connect. Use when verifying Loyverse ID token signatures. |
| `LOYVERSE_GET_MERCHANT_INFO` | Get Merchant Info | Tool to get merchant information. Use after authenticating to retrieve merchant account details. |
| `LOYVERSE_GET_MODIFIER` | Get Modifier | Tool to get a single modifier by ID. Use when you need to fetch details of an existing modifier in Loyverse. |
| `LOYVERSE_GET_OPEN_ID_CONFIGURATION` | Get OpenID Connect Discovery Document | Tool to retrieve the OpenID Connect discovery document. Use when integrating authentication and need endpoints and supported features. |
| `LOYVERSE_GET_PAYMENT_TYPE` | Get Payment Type | Tool to get a single payment type by its ID. Use when you need to fetch full details of a specific payment method before processing a transaction. |
| `LOYVERSE_GET_POS_DEVICE` | Get POS Device | Tool to retrieve details of a specific POS device by its ID. Use when you need POS device metadata after obtaining the device ID. |
| `LOYVERSE_GET_RECEIPT` | Get Receipt | Tool to retrieve a single receipt by its receipt number. Use when you need detailed information about a specific receipt including line items, payments, and totals. |
| `LOYVERSE_GET_STORE` | Get Store | Tool to retrieve details of a specific store by its ID. Use when you need store metadata (address, contact) after obtaining the store ID. |
| `LOYVERSE_GET_SUPPLIER` | Get Supplier | Tool to get a single supplier by their ID. Use when you need to fetch details of a specific supplier in Loyverse. |
| `LOYVERSE_GET_TAX` | Get Tax | Tool to get a single tax by ID. Use when you need to retrieve details of a specific tax configuration in Loyverse. |
| `LOYVERSE_GET_VARIANT` | Get Variant | Tool to get a single item variant by its ID. Use when you need detailed information about a specific variant from the Loyverse inventory. |
| `LOYVERSE_GET_WEBHOOK` | Get Webhook | Tool to get a single webhook by its ID. Use when you need to retrieve details of a specific webhook configuration. |
| `LOYVERSE_LIST_CATEGORIES` | List Categories | Tool to list categories with optional filtering and pagination. |
| `LOYVERSE_LIST_CUSTOMERS` | List Customers | Tool to get a list of customers. Use when you need paginated customer lists with optional filters. |
| `LOYVERSE_LIST_DISCOUNTS` | List Discounts | Tool to list discounts. Use when fetching a paginated set of discounts for display or sync. |
| `LOYVERSE_LIST_EMPLOYEES2` | List Employees (Advanced) | Tool to get a list of employees with advanced filtering options. Use when you need to filter employees by creation/update dates or view deleted employees. |
| `LOYVERSE_LIST_INVENTORY` | List Inventory | Retrieves inventory levels for item variants across stores in the Loyverse system. Use this to track stock quantities for specific variants at different store locations. Filter by store IDs, variant IDs, or date range to narrow results. |
| `LOYVERSE_LIST_ITEMS` | List Items | Retrieves a paginated list of items (products) from the Loyverse inventory. Items are sorted by creation date in descending order (newest first). Use filters to narrow results by category, date range, or specific item IDs. |
| `LOYVERSE_LIST_MODIFIERS2` | List Modifiers (Enhanced) | Tool to get a list of modifiers sorted by created_at in descending order. Use when you need to retrieve modifiers with advanced filtering options including creation/update dates and deleted items. |
| `LOYVERSE_LIST_PAYMENT_TYPES` | List Payment Types | Tool to list payment types. Use when you need to fetch available payment methods with optional filters and pagination. |
| `LOYVERSE_LIST_POS_DEVICES` | List POS Devices | Tool to get a list of POS devices sorted by creation date in descending order. Use when you need to retrieve POS device information for store management or reporting. |
| `LOYVERSE_LIST_RECEIPTS` | List Receipts | Tool to retrieve a list of receipts. Use when you need to fetch receipts with optional filters and handle pagination. |
| `LOYVERSE_LIST_SHIFTS` | List Shifts | Tool to list shifts. Use when you need to retrieve shift records for reporting or auditing with optional filters. |
| `LOYVERSE_LIST_STORES` | List Stores | Tool to get a list of stores sorted by creation date (newest first). Use when you need to retrieve store information across multiple locations. |
| `LOYVERSE_LIST_SUPPLIERS` | List Suppliers | Tool to retrieve a list of suppliers. Use when you need a paginated supplier directory with optional filters. |
| `LOYVERSE_LIST_TAXES2` | List Taxes | Tool to get a list of taxes sorted by creation date (newest first). Use when you need to retrieve tax records with optional filtering by IDs or date ranges. |
| `LOYVERSE_LIST_VARIANTS2` | List Variants | Tool to get a list of item variants sorted by creation date (newest first). Use when you need comprehensive filtering by variant IDs, item IDs, SKU, or date ranges, including deleted variants. |
| `LOYVERSE_LIST_WEBHOOKS` | List Webhooks | Tool to list webhooks. Use when you need to retrieve all configured webhooks. |
| `LOYVERSE_UPDATE_INVENTORY` | Update Inventory | Tool to batch update inventory levels for item variants at specific stores. Use when you need to set absolute stock quantities (not deltas) for one or more variant-store combinations. |
| `LOYVERSE_UPLOAD_ITEM_IMAGE` | Upload Item Image | Tool to upload a single image for an item. Accepts image/png or image/jpeg content types. Use after confirming the item ID to upload product images. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Loyverse MCP server is an implementation of the Model Context Protocol that connects your AI agent to Loyverse. It provides structured and secure access so your agent can perform Loyverse operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Python 3.9 or higher
- A Composio account and API key
- A Loyverse connection authorized in Composio
- An OpenAI API key for the CrewAI LLM
- Basic familiarity with Python

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

**What's happening:**
- composio connects your agent to Loyverse via MCP
- crewai provides Agent, Task, Crew, and LLM primitives
- crewai-tools[mcp] includes MCP helpers
- python-dotenv loads environment variables from .env
```bash
pip install composio crewai crewai-tools[mcp] python-dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's happening:
- COMPOSIO_API_KEY authenticates with Composio
- USER_ID scopes the session to your account
- OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import dependencies

**What's happening:**
- CrewAI classes define agents and tasks, and run the workflow
- MCPServerHTTP connects the agent to an MCP endpoint
- Composio will give you a short lived Loyverse MCP URL
```python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

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

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
```

### 5. Create a Composio Tool Router session for Loyverse

**What's happening:**
- You create a Loyverse only session through Composio
- Composio returns an MCP HTTP URL that exposes Loyverse tools
```python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["loyverse"])

url = session.mcp.url
```

### 6. Initialize the MCP Server

**What's Happening:**
- Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
- MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
- Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
- Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
- Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
```python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
```

### 7. Create a CLI Chatloop and define the Crew

**What's Happening:**
- Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
- Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
- Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
- Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
- Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
- Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.
```python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

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

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

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
```

## Complete Code

```python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

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.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["loyverse"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

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

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

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")
```

## Conclusion

You now have a CrewAI agent connected to Loyverse through Composio's Tool Router. The agent can perform Loyverse operations through natural language commands.
Next steps:
- Add role-specific instructions to customize agent behavior
- Plug in more toolkits for multi-app workflows
- Chain tasks for complex multi-step operations

## How to build Loyverse MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/loyverse/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/loyverse/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/loyverse/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/loyverse/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/loyverse/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/loyverse/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/loyverse/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/loyverse/framework/cli)
- [Google ADK](https://composio.dev/toolkits/loyverse/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/loyverse/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/loyverse/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/loyverse/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/loyverse/framework/llama-index)

## Related Toolkits

- [Addresszen](https://composio.dev/toolkits/addresszen) - Addresszen is a real-time address autocomplete and verification service. It helps capture accurate, deliverable addresses with instant suggestions and validation.
- [Asin data api](https://composio.dev/toolkits/asin_data_api) - Asin data api gives you detailed, real-time product data from Amazon, including price, rank, and reviews. Perfect for e-commerce pros and data-driven marketers who need instant marketplace insights.
- [Baselinker](https://composio.dev/toolkits/baselinker) - BaseLinker is an all-in-one e-commerce management platform connecting stores, marketplaces, carriers, and more. It streamlines order processing, inventory control, and automates your sales operations.
- [Bestbuy](https://composio.dev/toolkits/bestbuy) - Best Buy is a leading retailer offering APIs for product, store, and recommendation data. Instantly access up-to-date retail insights for smarter shopping and decision-making.
- [Btcpay server](https://composio.dev/toolkits/btcpay_server) - BTCPay Server is a free, open-source, self-hosted Bitcoin payment processor. It lets merchants accept Bitcoin payments directly, cutting out middlemen and boosting privacy.
- [Cdr platform](https://composio.dev/toolkits/cdr_platform) - Cdr platform is an API for purchasing carbon dioxide removal services. It enables businesses to offset emissions by accessing verified carbon removal projects.
- [Cloudcart](https://composio.dev/toolkits/cloudcart) - CloudCart is an e-commerce platform for building and managing online stores. It helps businesses streamline product listings, orders, and customer engagement.
- [Countdown api](https://composio.dev/toolkits/countdown_api) - Countdown API gives you real-time, structured eBay product data, reviews, and seller feedback. Perfect for powering price monitoring, product research, or marketplace analytics workflows.
- [Dpd2](https://composio.dev/toolkits/dpd2) - Dpd2 is a robust email management platform for handling, sorting, and automating email workflows. Streamline your communications and boost productivity with advanced sorting, labeling, and response tools.
- [Finerworks](https://composio.dev/toolkits/finerworks) - FinerWorks is an online platform for fine art and photo printing services. Artists and photographers use it to order custom prints and manage print inventory efficiently.
- [Fingertip](https://composio.dev/toolkits/fingertip) - Fingertip is a business management platform for selling, booking, and customer engagement—all from a single link. It helps businesses streamline operations and connect with customers across social channels.
- [Fraudlabs pro](https://composio.dev/toolkits/fraudlabs_pro) - FraudLabs Pro is an online payment fraud detection service for e-commerce and merchants. It helps minimize chargebacks and revenue loss by detecting and preventing fraudulent transactions.
- [Gift up](https://composio.dev/toolkits/gift_up) - Gift Up! is a digital platform for selling, managing, and redeeming gift cards online. It streamlines promotions and gift card transactions for businesses and their customers.
- [Goody](https://composio.dev/toolkits/goody) - Goody is a gifting platform that lets users send gifts and physical products without handling logistics. It streamlines gifting by managing delivery, fulfillment, and recipient experience.
- [Gumroad](https://composio.dev/toolkits/gumroad) - Gumroad is a platform for selling digital products, physical goods, and memberships with a simple checkout and marketing tools. It streamlines creator payouts and helps you grow your audience effortlessly.
- [Instacart](https://composio.dev/toolkits/instacart) - Instacart is an online grocery delivery and pickup service platform. It lets you discover local retailers and create shoppable lists and recipes with ease.
- [Junglescout](https://composio.dev/toolkits/junglescout) - Junglescout is an Amazon product research and analytics platform for sellers. It delivers sales estimates, competitive insights, and optimization tools to boost your Amazon business.
- [Ko fi](https://composio.dev/toolkits/ko_fi) - Ko-fi is a platform that lets creators receive donations, memberships, and sales from fans. It helps creators monetize their work and grow their audience with minimal friction.
- [Lemon squeezy](https://composio.dev/toolkits/lemon_squeezy) - Lemon Squeezy is a payments and subscription platform built for software companies. It makes managing payments, taxes, and customer subscriptions effortless.
- [Memberstack](https://composio.dev/toolkits/memberstack) - Memberstack lets you add user authentication, payments, and member management to your website—no backend code required. Easily manage your site's members and subscriptions from a single platform.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Loyverse MCP?

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.

### Can I use Tool Router MCP with CrewAI?

Yes, you can. CrewAI 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.

### Can I manage the permissions and scopes for Loyverse while using Tool Router?

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.

### 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 Loyverse data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)