Composio
Your agent acts. We'll handle the rest.
107 followers
Your agent acts. We'll handle the rest.
107 followers
Your AI agent knows what to do, Composio gives it the tools to actually do it. 1,000+ production-ready tools with managed auth, smart tool resolution, and sandboxed execution. Your agent calls the tool, we handle OAuth, permissions, and reliability. Five lines of code to go from chatbot to general-purpose agent. Used by teams at Zoom, Glean, and HubSpot.
This is the 5th launch from Composio. View more
Universal CLI by Composio
Launching today
There’s a lot of debate right now around how agents should use tools: MCP vs. CLI.
We don’t think there’s one right answer.
Universal CLI by Composio gives you a single interface to connect agents to tools, whether you're working with MCP, APIs, or both.
Same underlying system. Just another way to access it.
Free Options
Launch Team
Composio
Product Hunt
Rube by Composio
Hey PH community. Soham, co-founder at Composio.
We're taking a side today: we go where our users are.
And right now, a big chunk of them are in the terminal. Claude Code users. Agent builders running scripts. Teams with CI/CD pipelines. They've been asking for this.
MCP is a protocol. CLI is an interface. They solve different problems at different layers and we support both. But the timing for CLI is right, and we're not going to sit on the sidelines while the ecosystem moves.
Announcing Universal CLI by Composio
With this one command your agent get to access:
- 1000+ tools
- managed auth
- scoped permissions
All from your terminal.
If you're already on Composio via MCP, this is additive. Use whatever fits your environment.
Building something with it? Drop it below — happy to go deep.
Got any feedback? Let us know what you think in comments below.
@soham_ganatra3 For teams scoping permissions across multiple devs, how granular does the auth get? Can you lock it to specific tools/actions per env/user without boilerplate?
The MCP vs CLI thing is genuinely annoying to navigate as someone who runs a bunch of terminal-based agents. I keep hitting cases where one tool works great over MCP but another only has a CLI wrapper. Having a unified interface that handles both underneath makes a lot of sense. Curious how you handle auth token refresh for long-running agents - that’s usually where things break silently.
Product Hunt
Congrats on the launch! I'm a big fan of composio, I've been using @Rube by Composio for almost all my agents. I see that we can also install Composio natively into other agents aside from the CLI as well. How does the new launch and those other methods compare to Rube? Which do your recommend?
The MCP vs CLI take is spot on. I've been going back and forth on which approach to use for my agent workflows and honestly it shouldn't matter that much. One interface for both is the right call.
How's the OAuth handling work in practice? That's always the part where things get messy when you're connecting to like 10 different services.
This seems very helpful for solo developers. How do teams collaborate using this system?