How to integrate Baselinker MCP with LlamaIndex

This guide walks you through connecting Baselinker to LlamaIndex using the Composio tool router. By the end, you'll have a working Baselinker agent that can list all orders from this week, find orders placed by john@example.com, show pending receipts waiting to be issued through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Baselinker account through Composio's Baselinker 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
Baselinker logoBaselinker
Api Key

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.

106 Tools

Introduction

This guide walks you through connecting Baselinker to LlamaIndex using the Composio tool router. By the end, you'll have a working Baselinker agent that can list all orders from this week, find orders placed by john@example.com, show pending receipts waiting to be issued through natural language commands.

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

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

Also integrate Baselinker with

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AICrewAI

TL;DR

Here's what you'll learn:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Baselinker
  • Connect LlamaIndex to the Baselinker MCP server
  • Build a Baselinker-powered agent using LlamaIndex
  • Interact with Baselinker through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built for async/await patterns

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

The Baselinker MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Baselinker account. It provides structured and secure access to your e-commerce data, so your agent can perform tasks like managing orders, tracking inventory, processing receipts, and retrieving sales information on your behalf.

  • Order management and retrieval: Let your agent fetch, filter, and download order details—including by date, status, or customer email—for fast access to sales and customer data.
  • Inventory and purchase order tracking: Automatically retrieve current inventory documents, view purchase orders, and get document series to keep your stock and supply chain in check.
  • External storage and warehouse discovery: Seamlessly list all external stores and warehouses connected to your Baselinker account, so your agent knows where your products live.
  • Order status and custom field mapping: Ask your agent to pull order statuses or extra field definitions, making it easy to interpret, categorize, and automate order processing flows.
  • Pending receipt management: Quickly fetch receipts that still need to be issued, helping your team stay on top of fiscal compliance and transaction documentation.

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 you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Baselinker account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Baselinker

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Baselinker access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called baselinker_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["baselinker"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Baselinker actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, baselinker)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Baselinker tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Baselinker
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Baselinker tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Baselinker
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Baselinker, then start asking questions.

Complete Code

Here's the complete code to get you started with Baselinker and LlamaIndex:

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["baselinker"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Baselinker actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Baselinker to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Baselinker tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.
TOOLS

Supported Tools

Every Baselinker action and event your agent gets out of the box.

Add Inventory

Tool to add or update a BaseLinker catalog (inventory).

Add Inventory Category

Tool to add or update a category in the BaseLinker catalog.

Add Inventory Document

Tool to create a new inventory document in BaseLinker storage.

Add Inventory Manufacturer

Tool to add or update a manufacturer in the BaseLinker catalog.

Add Inventory Payer

Tool to add a new payer or update an existing one in BaseLinker storage.

Add Inventory Price Group

Tool to create or update a price group in BaseLinker storage.

Add Inventory Product

Add a new product to BaseLinker catalog or update an existing product.

Add Inventory Purchase Order

Tool to create a new purchase order in BaseLinker storage.

Add Inventory Purchase Order Items

Tool to add items to an existing purchase order in BaseLinker.

Add Inventory Supplier

Tool to add a new supplier or update an existing one in BaseLinker storage.

Add Inventory Warehouse

Tool to add a new warehouse or update an existing warehouse in BaseLinker inventories.

Add Invoice

Tool to issue an order invoice in BaseLinker.

Add Invoice Correction

Tool to issue an order invoice correction.

Add Order

Tool to add a new order to the BaseLinker order manager.

Add Order By Split

Tool to create a new order by splitting selected products from an existing order.

Add Order Duplicate

Tool to add a new order by duplicating an existing order in BaseLinker.

Add Order Return

Tool to add a new order return to BaseLinker.

Add Order Return Product

Tool to add a new product to an existing order return in BaseLinker.

Add Shop Category

Tool to add a new category to BaseLinker storage (shops, warehouses, or BaseLinker inventory).

Create Package Manual

Tool to register shipping details for orders when shipments are created outside BaseLinker.

Delete Inventory

Tool to delete a catalog from BaseLinker storage.

Delete Inventory Category

Tool to remove categories from BaseLinker warehouse.

Delete Inventory Manufacturer

Tool to remove a manufacturer from the BaseLinker catalog.

Delete Inventory Payer

Tool to remove a payer from BaseLinker storage.

Delete Inventory Price Group

Tool to remove a price group from BaseLinker storage.

Delete Inventory Product

Tool to remove a product from the BaseLinker catalog.

Delete Inventory Warehouse

Tool to remove a warehouse from BaseLinker inventories.

Delete Order Product

Tool to remove a specific product from an order in BaseLinker.

Delete Order Return Product

Tool to remove a specific product from an order return in BaseLinker.

Delete Orders

Tool to delete multiple orders from BaseLinker order manager.

Get Connect Integration Contractors

Tool to retrieve a list of contractors connected to a selected Base Connect integration.

Get Connect Integrations

Tool to retrieve a list of all Base Connect integrations on this account.

Get Courier Accounts

Tool to retrieve the list of accounts connected to a given courier.

Get Courier Fields

Tool to retrieve the form fields required for creating shipments with a specific courier.

Get Courier Packages Status History

Tool to retrieve the history of status changes for courier packages.

Get Couriers List

Tool to retrieve a list of available couriers from BaseLinker.

Get External Storage Products Quantity

Retrieve stock quantities from an external storage (shop/wholesaler) connected to BaseLinker.

Get External Storages List

Retrieve a list of external storages (shops, warehouses, wholesalers) connected to BaseLinker that can be referenced via API.

Get Inventories

Tool to retrieve a list of catalogs (inventories) available in the BaseLinker storage.

Get Inventory Available Text Field Keys

Tool to retrieve a list of product text fields that can be overwritten for a specific integration.

Get Inventory Categories

Tool to retrieve a list of categories for a BaseLinker catalog.

Get Inventory Document Items

Tool to retrieve items from inventory documents in BaseLinker.

Get Inventory Documents

Tool to retrieve a list of inventory documents.

Get Inventory Document Series

Tool to retrieve available inventory document series.

Get Inventory Extra Fields

Tool to retrieve extra fields defined for BaseLinker catalog inventory items.

Get Inventory Integrations

Tool to retrieve a list of integrations where text values in the catalog can be overwritten.

Get Inventory Manufacturers

Tool to retrieve a list of manufacturers from the BaseLinker catalog.

Get Inventory Payers

Tool to retrieve a list of payers available in BaseLinker storage.

Get Inventory Price Groups

Tool to retrieve price groups existing in BaseLinker storage.

Get Inventory Printout Templates

Tool to retrieve a list of all configured printout templates available for inventory (products).

Get Inventory Product Logs

Tool to retrieve a list of events related to product changes in the BaseLinker catalog.

Get Inventory Products Data

Tool to retrieve detailed data for selected products from the BaseLinker inventory.

Get Inventory Products List

Tool to retrieve basic data of chosen products from BaseLinker catalogs.

Get Inventory Products Prices

Retrieve gross prices of products from BaseLinker inventories.

Get Inventory Products Stock

Tool to retrieve stock data of products from BaseLinker catalogs.

Get Inventory Purchase Order Items

Tool to retrieve items from a specific purchase order in BaseLinker.

Get Inventory Purchase Orders

Tool to retrieve a list of purchase orders from BaseLinker storage.

Get Inventory Purchase Order Series

Tool to retrieve a list of purchase order document series.

Get Inventory Suppliers

Tool to retrieve a list of suppliers available in BaseLinker storage.

Get Inventory Tags

Tool to retrieve a list of tags for a BaseLinker catalog.

Get Inventory Warehouses

Tool to retrieve a list of warehouses available in BaseLinker inventories.

Get Invoice File

Tool to retrieve an invoice file from BaseLinker in base64-encoded format.

Get Invoices

Download invoices from BaseLinker order manager with optional filtering.

Get Journal List

Tool to download order event logs from the last 3 days.

Get New Receipts

Tool to retrieve receipts waiting to be issued.

Get Order Extra Fields

Tool to retrieve extra fields defined for orders.

Get Order Packages

Tool to download shipments previously created for a selected order.

Get Order Payments History

Tool to retrieve payment history for a selected order, including external payment identifiers from payment gateways.

Get Order Pick Pack History

Tool to retrieve pick and pack history for a selected order.

Get Order Printout Templates

Tool to retrieve a list of all configured printout templates available for orders.

Get Order Return Extra Fields

Tool to retrieve extra fields defined for order returns.

Get Order Return Journal List

Tool to download return event logs from the last 3 days in BaseLinker.

Get Order Return Payments History

Tool to retrieve payment history for a selected order return, including external payment identifiers from the payment gateway.

Get Order Return Product Statuses

Tool to retrieve a list of order return product statuses from BaseLinker.

Get Order Return Reasons List

Tool to retrieve a list of order return reasons.

Get Order Returns

Download order returns from BaseLinker return manager with optional filtering.

Get Order Return Status List

Tool to retrieve order return statuses created in the BaseLinker order manager.

Get Orders

Download orders from BaseLinker order manager with optional filtering.

Get Orders by Phone

Search for orders associated with a specific phone number in BaseLinker.

Get Order Sources

Tool to retrieve types of order sources along with their IDs from BaseLinker.

Get Order Status List

Tool to retrieve a list of order statuses created in the BaseLinker order manager.

Get Order Transaction Data

Tool to retrieve transaction details for a selected order.

Get Package Details

Tool to get detailed information about a package.

Get PickPack Carts

Tool to retrieve a list of all PickPack carts belonging to the authenticated user.

Get Protocol

Tool to download a parcel protocol for selected shipments.

Get Receipts

Tool to retrieve issued receipts from BaseLinker.

Get Request Parcel Pickup Fields

Tool to retrieve additional fields for a parcel pickup request from a specific courier.

Get Series

Tool to download invoice/receipt numbering series.

Get Storages List

Tool to download a list of available storages accessible via API.

Run Order Macro Trigger

Tool to run personal trigger for orders automatic actions.

Run Product Macro Trigger

Tool to execute a personal trigger for products automatic actions.

Run Request Parcel Pickup

Tool to request a parcel pickup for previously created shipments.

Set Inventory Purchase Order Status

Tool to change the status of a purchase order in BaseLinker inventory.

Set Order Fields

Tool to edit selected fields of a specific order in BaseLinker.

Set Order Payment

Tool to add a payment to an order in BaseLinker.

Set Order Product Fields

Tool to edit data of selected items in a specific BaseLinker order.

Set Order Receipt

Tool to mark orders with a receipt already issued.

Set Order Return Fields

Tool to edit selected fields of a specific order return.

Set Order Return Product Fields

Tool to edit data of selected items (e.

Set Order Return Refund

Tool to mark an order return as refunded in BaseLinker.

Set Order Return Status

Tool to change order return status in BaseLinker.

Set Order Return Statuses

Tool to batch set order return statuses in BaseLinker.

Set Orders Merge

Tool to merge multiple orders into one, based on the selected merge mode.

Set Order Status

Tool to change the status of an existing order in BaseLinker.

Set Order Statuses

Tool to batch update order statuses in BaseLinker.

Update Inventory Products Stock

Tool to update stocks of products and their variants in BaseLinker catalog.

FRAMEWORKS

How to build Baselinker MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Baselinker MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Baselinker MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Baselinker MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Baselinker MCP with Claude Cowork

Codex logo

Codex

Use Baselinker MCP with Codex

OpenClaw logo

OpenClaw

Use Baselinker MCP with OpenClaw

Hermes logo

Hermes

Use Baselinker MCP with Hermes

CLI logo

CLI

Use Baselinker MCP with CLI

Google ADK logo

Google ADK

Use Baselinker MCP with Google ADK

LangChain logo

LangChain

Use Baselinker MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Baselinker MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Baselinker MCP with Mastra AI

CrewAI logo

CrewAI

Use Baselinker MCP with CrewAI

FAQ

Frequently asked questions

With a standalone Baselinker MCP server, the agents and LLMs can only access a fixed set of Baselinker tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Baselinker and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. LlamaIndex 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 Baselinker tools.

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

Start with Baselinker.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Baselinker 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