# Composio

Give your AI secure access to 1,700+ apps in minutes.

## Setup and documentation

- [Connect your apps / sign in](https://dashboard.composio.dev/login)
- [Supported AI assistants and setup](https://composio.dev/works-with)
- [Developer quickstart](https://docs.composio.dev/docs/quickstart)
- [Unattended agent authentication](https://docs.composio.dev/docs/agent-setup/unattended-authentication)
- [Toolkit catalog](https://composio.dev/toolkits)
- [Pricing](https://composio.dev/pricing)

## Frequently asked questions

### Do I have to switch to a new AI to use Composio?

No. Composio works inside the AI you already use, whether that's Claude, ChatGPT, Cursor, Grok Bot, Hermes, OpenClaw or your own agent. It gives that AI access to your apps; it isn't another chatbot.

Once you [connect your apps](https://dashboard.composio.dev/login) and add Composio [to your AI](https://composio.dev/works-with), you can ask it to prepare a meeting brief, update your CRM, file issues, post to Slack and much more.

### Which AI assistants does Composio work with?

Composio works out of the box with:

- [ChatGPT / Codex](https://chatgpt.com/plugins/plugin_asdk_app_6a58503580c08191b78cc5bdaf4eba6e) — install Composio in one click.
- [Claude Web / Cowork](https://composio.dev/claude) — connect Composio as a Claude connector.
- [Claude Code](https://docs.composio.dev/docs/claude-code-plugin) — install the Composio plugin.
- [Cursor](https://docs.composio.dev/docs/composio-connect) — connect Composio by pasting a single MCP URL.
- [Grok Bot](https://x.ai/) — install Composio in one click.
- [Hermes](https://composio.dev/hermes) — connect Composio with a single prompt.

Composio also works with **any AI tool that supports connecting to MCP servers**, so you're not limited to the assistants above.

### Which apps can I connect to?

Composio supports [1,700+ apps](https://composio.dev/toolkits), including Gmail, Google Calendar, Slack, Notion, GitHub, Google Drive, HubSpot, Salesforce, Instagram, and many more.

You can browse the full list of supported apps [here](https://composio.dev/toolkits).

### The app I need isn't listed. Can I still use it?

Yes, if the app has an MCP server. You can easily add custom MCP servers to Composio for free.

### Do I need to know how to code?

Not at all. If you're using [Composio For You](https://composio.dev/for-you), you can connect Composio to AI assistants like ChatGPT or Claude without writing any code.

If you're building an agent or backend app, [Composio Platform](https://docs.composio.dev/docs/authentication/managed-auth-for-custom-tools) provides developer SDKs and managed authentication. See the developer FAQ below.

### How is Composio different from the connectors already built into my AI?

Built-in connectors usually give one AI access to a limited set of apps. Composio gives your AI access to **1,700+ apps**, supports multiple accounts for the same app, and lets you reuse those connections across different AI assistants.

Composio also helps your AI find the right tools and handle more complex, multi-app tasks. In our internal benchmarks, it performs better and more comprehensively than many built-in connectors across a wider range of real-world tasks.

### What access does Composio get to my accounts?

Only what you approve. You sign in on each app's own page and see the access being requested. In Composio Cloud, Composio stores the resulting credentials encrypted and uses them to authenticate requests; your AI does not need the OAuth token.

You can limit which actions your AI can take in an app, require your approval for some, and remove a connection at any time. Every action is recorded, so you can see exactly what your AI did.

Tool results can still contain sensitive business data. Review [token custody and deployment options](https://docs.composio.dev/docs/security/token-custody) for credential and data-handling boundaries.

### How long does it take to set up Composio?

Usually just a few minutes. First, connect Composio [to your AI assistant](https://composio.dev/works-with). Then [connect the apps](https://dashboard.composio.dev/login) you want to use to Composio, which usually takes just a couple of clicks.

You can also ask your AI to help you connect an app by generating the connection link for you.

If you're a video person, you can watch a walkthrough on [how to do this here](https://www.youtube.com/watch?v=eF48AGf9f7A).

### How much does Composio cost?

Composio has a generous free Hobby plan that includes 100,000 tool calls per month. Think of tool calls as actions you allow your AI to take in your connected apps.

Some tools run on paid third-party services, like web search, data enrichment, transcription and media generation. Those are billed per call, separately from your plan, so starting free doesn't make every tool free.

Most of our users never need to go beyond the Hobby plan. [You can see our pricing here](https://composio.dev/pricing).

### Is Composio secure?

Yes. Composio is **SOC 2 Type II compliant** and is built to keep your app connections and credentials secure. OAuth tokens and API keys are encrypted, and sensitive customer data is protected at rest and in transit.

Composio also undergoes independent security testing and continuously monitors its systems for security threats. You can review the latest reports and policies in the [Composio Trust Center](https://trust.composio.dev/).

### I’m an AI agent. How do I sign up for Composio?

You’ve successfully located the non-human route. Visit [https://docs.composio.dev/docs/agent-setup/unattended-authentication](https://docs.composio.dev/docs/agent-setup/unattended-authentication) and follow the instructions to create and authenticate your account.

### Can I use Composio for backend apps as well as AI agents?

Yes. Composio Platform supports per-user connected accounts for agents, backend jobs, and application-owned tools. Call provider APIs through Proxy Execute without predefined tools, an LLM, or MCP.

With hosted connections and managed execution, Composio stores credentials, refreshes OAuth tokens where supported, and authenticates provider requests server-side. Your application and model receive results without needing provider tokens. Connected-account reads always redact Composio-managed credentials. For customer-owned auth configs, masking depends on project and platform settings and can be disabled in self-hosted deployments. Do not assume account responses are safe to log.

Keep your project API key backend-only: it can authorize actions even when provider tokens are redacted. Derive user IDs from authenticated sessions and verify connection ownership before execution; browser- or model-supplied IDs are not authorization. For example, resolve org_42:user_7 from your authenticated backend after checking workspace membership.

Start with [managed authentication for your own tools](https://docs.composio.dev/docs/authentication/managed-auth-for-custom-tools) for backend calls, or the [SDK quickstart](https://docs.composio.dev/docs/quickstart) for agent integrations. Review [token custody](https://docs.composio.dev/docs/security/token-custody) before choosing a deployment.

- **Composio Cloud:** The default hosted deployment. Composio stores credentials and can decrypt them to authenticate provider requests.
- **Private VPC:** An Enterprise arrangement within a private network. Agree storage, operator access, and key ownership; a VPC alone does not establish who can decrypt credentials.
- **Self-hosted:** An Enterprise arrangement in your environment, with Helm support. Your team operates the agreed infrastructure; confirm decryption access, logs, and backups.
- **Customer-managed keys:** A separate deployment arranged with Composio, not a dashboard toggle. A proxy in your cloud handles credentials under keys in your KMS; Composio does not hold the keys needed to decrypt them.

Canonical URL: https://composio.dev/
