Skip to content

Botpress vs Composio

Which should you use? A side-by-side look at what each one does, who it suits, what it costs, how hard it is to set up, and where each falls short.

Botpress

Open source · MIT

Open-source tools to build and deploy chatbots and LLM agents, centred on Botpress Cloud.

Composio

Open source · MIT

SDK for building AI agents that can take actions in 1000+ apps via pre-authenticated tools.

The short answer

Choose Botpress if you need…

  • Developers who want to write integrations and bots as TypeScript code using the Botpress CLI and SDK
  • Teams already using Botpress Cloud who want to publish or deploy their own integrations
  • Developers who want to read example bots built only with the SDK and CLI

Choose Composio if you need…

  • Developers building AI agents that need to read or act in third-party apps
  • Teams already using a supported agent framework such as OpenAI Agents, LangChain, or Vercel AI SDK
  • Projects that want per-user scoping of app connections
  • Developers who want to expose tools to MCP clients like Claude or Cursor

Side-by-side

BotpressComposio
TypeDev toolDev tool
PriceFree and open sourceFree and open source
LicenceMITMIT
GitHub stars15k30.9k
Setup difficultyIntermediateIntermediate
How you get itInstall with a package managerInstall with a package manager
Main languageTypeScriptTypeScript
Last code update7 days ago4 days ago

What each one is

Botpress

This repository holds the open-source parts of Botpress Cloud: integrations, developer tools (a CLI, an SDK and an API client), and some example bots written as code. Botpress is described as a platform for building chatbots and assistants powered by OpenAI. The README says the visual Botpress Studio is the recommended way to build bots, and the code-based approach is mainly for experienced developers.

Composio

Composio is a TypeScript and Python SDK, plus a command-line tool, that lets AI agents use external apps on a user's behalf. It provides pre-authenticated toolkits for over 1000 apps, per-user sessions, authentication, triggers, and a sandbox. Developers use it to connect an agent framework to real services such as email.

Best for

Botpress

  • Developers who want to write integrations and bots as TypeScript code using the Botpress CLI and SDK
  • Teams already using Botpress Cloud who want to publish or deploy their own integrations
  • Developers who want to read example bots built only with the SDK and CLI

Composio

  • Developers building AI agents that need to read or act in third-party apps
  • Teams already using a supported agent framework such as OpenAI Agents, LangChain, or Vercel AI SDK
  • Projects that want per-user scoping of app connections
  • Developers who want to expose tools to MCP clients like Claude or Cursor

Strengths

Botpress

  • Released under the MIT license, so the code can be reused and modified freely
  • Uses TypeScript and a typed SDK and API client, which helps catch errors early
  • Includes a CLI for the full integration workflow: create, deploy and publish

Composio

  • Broad coverage: the README lists 1000+ toolkits and many provider adapters for common agent frameworks
  • Sessions load meta tools at runtime instead of hundreds of tool definitions, per the README
  • Available in both TypeScript and Python with an MIT license

Not ideal for

Botpress

  • Non-programmers who want a no-code chatbot builder: the README says the Studio is recommended over building bots as code
  • People looking for the on-premise Botpress v12 product: the README sends those users to a separate v12 repository
  • Anyone needing a self-contained local chatbot: the README focuses on Botpress Cloud workflows and does not describe a standalone self-hosted setup

Composio

  • Non-developers looking for a finished end-user app, since the README describes an SDK and CLI
  • People who need a fully self-hosted setup, because the README's quickstart relies on a Composio API key and dashboard
  • Projects needing a framework the README does not list as supported, which would require writing a custom provider

Trade-offs

Botpress

  • The README marks plugins as coming soon, so that part is not yet available
  • Code-first bot building is described by the authors as not the recommended route for most users
  • Setup and terminology depend on the Botpress Cloud service, so the project is tied to that platform

Composio

  • Depends on a Composio account and API key for the quickstart, so you rely on a hosted service
  • The README is truncated and gives limited detail on sandbox, triggers, and pricing
  • Some providers are experimental, such as the Pi provider in @composio/experimental

Getting started

Botpress

Install the Botpress CLI (npm)

npm install -g @botpress/cli

Create a new integration

bp init
Step-by-step guide: how to use Botpress

Composio

Install TypeScript SDK with OpenAI Agents provider

npm install @composio/core @composio/openai-agents @openai/agents

Install Python SDK with OpenAI Agents provider

pip install composio composio-openai-agents openai-agents
Step-by-step guide: how to use Composio

Frequently asked questions

What is the difference between Botpress and Composio?

Botpress: Open-source tools to build and deploy chatbots and LLM agents, centred on Botpress Cloud. Composio: SDK for building AI agents that can take actions in 1000+ apps via pre-authenticated tools. Botpress suits developers who want to write integrations and bots as typescript code using the botpress cli and sdk, while Composio suits developers building ai agents that need to read or act in third-party apps.

Are Botpress and Composio free?

Botpress: Free and open source. Composio: Free and open source.

Is Botpress or Composio more popular?

Composio has more GitHub stars (30.9k) than Botpress (15k). Popularity isn't the same as fit — check which one matches your use case above.

What are other alternatives to Botpress and Composio?

Other options people compare them with include LangChain, Prompt flow, Portkey AI Gateway, claude-context, Desktop Commander.

Keep comparing

Built from our catalogue entries for both products: open-source details come from each project's README (AI-assisted, refreshed weekly) and GitHub data; AI-tool details are editorial. Spotted something wrong? Let us know from either product's page.