Introducing Tool Router (Beta)

Last month, we launched rube a jack-of-all-trades MCP server that automatically chooses which app and tool to use. Since launching it a lot of you have been asking for ways to build on top of rube. There were janky ways to do this before, but today we're shipping the official way.

The Basics

Here's how Tool Router works:

import { Composio } from '@composio/core';

const composio = new Composio();

const userId = "rahul";

// Access the experimental ToolRouter
const mcpSession = composio.experimental.toolRouter.createSession(userId);

This gives you a pre-signed MCP URL for a user and their chat session. Everything else happens within the chat window like in Rube.

Tool Router has more control, you can choose which toolkits to support or manually handle authentication. Full docs here.

Why "Experimental"?

We're calling this experimental because we're not entirely sure how you're going to use this. We want to see how people build with this fully agentic experience before we decide on the final abstractions.

Some set of questions we have:

• how much control over the planner would you like?

  • do you even want a planner we provide?

• how much control over the search would you like?

• is the latency of the remote workbench okay?

The main question: Should we decompose Tool Router into pieces you put together yourself, or keep it as something more finished? if we are decomposing it, what should that look like

We'd love feedback on this discussion or our Discord. Ideally, we'd love to hop on a call with you and hear what could be better.

Looking Forward

We've been teasing skills for the last few months. Today we're showing you v0 of where we think this is heading.

Today this is a toolRouter with 10k+ tools, tomorrow this will be the basis of our skills with millions of skills