Integration

Composio integration

Composio is a catalogue of third-party tools and authenticated connections for AI agents. Browse the toolkits it supports, read the tools each toolkit exposes with their input schemas, see which accounts are connected, and run a tool against one of those connections. A tool is addressed by its slug, e.g. "GITHUB_CREATE_AN_ISSUE", and runs under a connected account you have already authorised in Composio.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Composio.Built from the 8 Composio tools below, on the connection you add once.

What you can do with Composio

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Tools, 3 operations

  • execute_toolExecute toolPOSTAgents: ask firstRun a Composio tool against a connected account.
  • get_toolGet toolGETAgents: ask firstRead one Composio tool and its input schema.
  • list_toolsList toolsGETAgents: ask firstList the tools Composio exposes, optionally for one toolkit.

Connected accounts, 2 operations

  • get_connected_accountGet connected accountGETAgents: ask firstRead one Composio connected account.
  • list_connected_accountsList connected accountsGETAgents: ask firstList the accounts connected in Composio.

Toolkits, 2 operations

  • get_toolkitGet toolkitGETAgents: ask firstRead one Composio toolkit by slug.
  • list_toolkitsList toolkitsGETAgents: ask firstList the toolkits Composio supports.

Triggers, 1 operation

  • list_trigger_typesList trigger typesGETAgents: ask firstList the trigger types Composio exposes.

Use Composio from Claude Code, Cursor or Codex

Connect Composio in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Composio operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Composio

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Composio once

    Add your Composio connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Composio integration FAQ

What can you do with the Composio integration?

LiveContext exposes 8 operations on Composio, covering tools, connected accounts, toolkits and triggers.

Popular integrations

Browse the whole catalog