How to integrate Backendless MCP with Claude Agent SDK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Backendless Logo
Claude Agent SDK Logo
divider

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, delete a file named report.pdf from backups 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.

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.

Supported Tools & Triggers

Tools
Copy FileTool to copy a file or directory within backendless file storage.
Create DirectoryTool to create a new directory at the specified path.
Create Backendless HiveTool to create a new hive.
Create Backendless TimerTool to create a new timer with schedule and code.
Delete DirectoryTool to delete a directory at the specified path in backendless file storage.
Delete FileTool to delete a file at the specified path in backendless file storage.
Delete Backendless TimerTool to delete a backendless timer by name.
Directory ListingTool to retrieve a listing of files and directories at a given path.
General Object RetrievalTool to retrieve objects from a specified backendless table with filtering, sorting, and pagination.
Get All ValuesTool to retrieve all values from a map in a specified hive.
Get Counter ValueTool to retrieve the current value of a backendless counter.
Get File CountTool to get the count of files in a backendless directory.
Get Key ItemsTool to retrieve values for a specified key in a list (all, single, or range).
Get Backendless TimerTool to retrieve information about a specific timer.
Map PutTool to set or update key-value pairs in a hive map.
Move FileTool to move a file or directory within backendless file storage.
Publish MessageTool to publish a message to a specified messaging channel.
Reset CounterTool to reset a backendless counter back to zero.
Set Counter ValueTool to set a backendless counter to a specific value conditionally.
Update Backendless TimerTool to update schedule or code of an existing timer.
Change User PasswordTool to change the password for the current user.
Delete UserTool to delete a user by user id.
Find User by IDTool to retrieve user information by id.
Grant Permission to UserTool to grant a permission to a user on a specific data object.
User LoginTool to log in a registered user with identity and password.
User LogoutTool to log out the currently authenticated user.
User Password RecoveryTool to initiate password recovery for a user.
User RegistrationTool to register a new user with email and password.
Revoke Permission from UserTool to revoke a permission from a specified user or role on a data table.
Update UserTool to update properties of an existing backendless user.
Validate User TokenTool to validate a user session token.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router 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 Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router 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

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

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.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

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

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

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

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Backendless
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["backendless"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
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

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Backendless tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="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
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

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

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Backendless
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["backendless"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Backendless tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

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.

How to build Backendless MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Backendless MCP with OpenAI Agents SDK

Google ADK

Google ADK

Use Backendless MCP with Google ADK

LangChain

LangChain

Use Backendless MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Backendless MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Backendless MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Backendless MCP with LlamaIndex

CrewAI

CrewAI

Use Backendless MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Backendless MCP?

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.

Can I use Tool Router MCP with Claude Agent SDK?

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.

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

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.

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

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free