How to integrate Backendless MCP with Claude Agent SDK

This guide walks you through connecting Backendless to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Backendless agent that can list all files in the user uploads folder, create a new directory for project assets, retrieve users where status is active through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Backendless account through Composio's Backendless 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
Backendless logoBackendless
Api Key

Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure.

30 Tools

Introduction

This guide walks you through connecting Backendless to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Backendless agent that can list all files in the user uploads folder, create a new directory for project assets, retrieve users where status is active through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Backendless account through Composio's Backendless MCP server.

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

Also integrate Backendless with

OpenAI Agents SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Backendless
  • Configure an AI agent that can use Backendless as a tool
  • Run a live chat session where you can ask the agent to perform Backendless operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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

The Backendless MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Backendless account. It provides structured and secure access to your backend services, so your agent can perform actions like managing file storage, retrieving and updating database records, handling directories, and orchestrating server-side logic on your behalf.

  • Dynamic file and directory management: Allow your agent to create, copy, delete, and list files or folders in your Backendless storage, keeping your app data organized.
  • Database record retrieval and filtering: Empower the agent to fetch objects from specific tables with advanced filtering, sorting, and pagination for instant data access.
  • Automated backend task scheduling: Let the agent create or delete timers to run recurring or one-off server-side logic, enabling powerful backend automation.
  • Custom Hive resource management: Instruct your agent to create new Backendless Hive resources and retrieve full maps of stored values for scalable, flexible data handling.
  • Safe data cleanup: Make it easy for your agent to remove obsolete files, directories, or scheduled tasks, helping maintain a tidy and efficient backend environment.

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:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Backendless account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • 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 @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Backendless functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

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

  // Create Tool Router session for Backendless
  const session = await composio.create(USER_ID, {
    toolkits: ['backendless'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Backendless
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Backendless tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Backendless
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Backendless and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['backendless']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Backendless tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Backendless through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

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

Copy File

Tool to copy a file or directory within Backendless file storage.

Create Directory

Tool to create a new directory at the specified path.

Create Backendless Hive

Tool to create a new Hive.

Create Backendless Timer

Tool to create a new timer with schedule and code.

Delete Directory

Tool to delete a directory at the specified path in Backendless file storage.

Delete File

Deletes a file from Backendless file storage at the specified path.

Delete Backendless Timer

Deletes a Backendless timer by its unique name.

Directory Listing

Tool to retrieve a listing of files and directories at a given path.

General Object Retrieval

Tool to retrieve objects from a specified Backendless table with filtering, sorting, and pagination.

Get All Values

Tool to retrieve all values from a map in a specified Hive.

Get Counter Value

Tool to retrieve the current value of a Backendless counter.

Get File Count

Tool to get the count of files in a Backendless directory.

Get Key Items

Tool to retrieve values for a specified key in a list (all, single, or range).

Get Backendless Timer

Tool to retrieve information about a specific timer.

Map Put

Tool to set or update key-value pairs in a Hive map.

Move File

Tool to move a file or directory within Backendless file storage.

Publish Message

Tool to publish a message to a specified messaging channel.

Reset Counter

Tool to reset a Backendless counter back to zero.

Set Counter Value

Tool to set a Backendless counter to a specific value conditionally.

Update Backendless Timer

Tool to update schedule or code of an existing timer.

Delete User

Tool to delete a user by user ID.

Find User by ID

Tool to retrieve user information by ID.

Grant Permission to User

Tool to grant a permission to a user on a specific data object.

User Login

Tool to log in a registered user with identity and password.

User Logout

Tool to log out the currently authenticated user.

User Password Recovery

Tool to initiate password recovery for a user.

User Registration

Tool to register a new user with email and password.

Revoke Permission from User

Tool to revoke a permission from a specified user or role on a specific data object.

Update User

Tool to update properties of an existing Backendless user.

Validate User Token

Tool to validate a user session token.

FRAMEWORKS

How to build Backendless MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Backendless MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use Backendless MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Backendless MCP with Claude Cowork

Codex logo

Codex

Use Backendless MCP with Codex

OpenClaw logo

OpenClaw

Use Backendless MCP with OpenClaw

Hermes logo

Hermes

Use Backendless MCP with Hermes

CLI logo

CLI

Use Backendless MCP with CLI

Google ADK logo

Google ADK

Use Backendless MCP with Google ADK

LangChain logo

LangChain

Use Backendless MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Backendless MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Backendless MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Backendless MCP with LlamaIndex

CrewAI logo

CrewAI

Use Backendless MCP with CrewAI

FAQ

Frequently asked questions

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

Yes, you can. Claude Agent SDK 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 Backendless tools.

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

Start with Backendless.It takes 30 seconds.

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