Tool Router Quick Start

Tool Router automatically discovers, authenticates, and executes the right tools for any task. It’s an experimental feature that handles the entire workflow—from finding relevant tools across 500+ integrations to managing authentication and parallel execution.

This is what powers complex agentic products like Rube.

Quick Start

Create a presigned URL for each user session. This URL exposes Tool Router capabilities through the Model Context Protocol (MCP).

1
from composio import Composio
2
composio = Composio()
3
4
userId = "hey@example.com"
5
# Create a tool router session
6
session = composio.experimental.tool_router.create_session(
7
    user_id=userId,
8
)
9
# Returns:
10
# {
11
#   'session_id': '<session_id>',
12
#   'url': '<mcp_url>'
13
# }
14
15
mcpUrl = session['url']

The URL you get here is an MCP StreamableHTTP URL. You can use this URL in any MCP client, you can see how it lists tools inside the inspector here.

Building on top of this URL with providers

The necessary scaffolding will be integrated into existing providers abstraction before toolRouter is generally available.

Use the presigned URL with any frameworks that support MCP directly, few examples below:

OpenAI

Connect via OpenAI’s MCP connector to use Tool Router with GPT models

Vercel AI SDK

Use experimental_createMCPClient with StreamableHTTPClientTransport to integrate with Next.js apps

Claude

Connect remote MCP servers through Anthropic’s MCP connector API

LangChain

Load Tool Router tools using langchain_mcp_adapters for Python workflows

How Tool Router Works

The Tool Router executes a three-phase workflow:

1. Discovery
Searches across all available tools to find ones matching your task. Returns relevant toolkits with their descriptions, schemas, and connection status.

2. Authentication
Checks if the user has an active connection to the required toolkit. If not, creates an auth config and returns a connection URL using Auth Link. The user completes authentication through this link.

3. Execution
Loads authenticated tools into context and executes them. Supports parallel execution across multiple tools for efficiency.

Context Management

The Tool Router intelligently manages context to avoid overwhelming the LLM with unnecessary information. Tools are only loaded into context when needed—search discovers relevant tools, and multi execute loads them just-in-time for execution. When working with large outputs, the remote workbench stores them as files in persistent storage, allowing iteration without consuming context windows. The system also segments tools within each MCP server, exposing only the subset required for the current task.

Available Tools

The router exposes six meta tools through MCP. These tools orchestrate the complete workflow from discovery to execution:

Customizing the Tool Router

Restricting Toolkits

Control which toolkits are available by specifying them during session creation. This limits which apps your users can access.

1
session = composio.experimental.toolRouter.createSession("hey@example.com", {
2
  toolkits: ["github", "slack"],
3
})

Manual Connection Management

You can manually manage connections, this is advanced and still a bit of work in progress.

To manually manage connections, you can set manuallyManageConnections to true and limit the toolkits you want to use.

Once you pass the auth config id, you can use our regular functions to connect accounts and check authentication status.

1
// Access the experimental ToolRouter
2
const session = await composio.experimental.toolRouter.createSession("hey@example.com", {
3
  toolkits: [{ toolkit: 'gmail', authConfigId: 'ac_nnn' }],
4
  manuallyManageConnections: true,
5
});

Feedback

This is still very experimental and work in progress, you can expect the contracts to change and improve as we iterate on this. That said we would love to hear your feedback on this

Give us feedback on this github discussion here