Tenth in the series is Zero, a Claude Code plugin (zero@zero-plugins) that takes a different approach to the “how does the agent get access to external tools” problem than anything else covered so far.
Discover and pay at runtime
Rather than you pre-configuring API keys for every service you might want Claude to touch, Zero exposes a catalogue of thousands of tools, APIs, and services that get discovered and paid for per use at the point Claude actually needs them. There’s no upfront config step and no API keys to collect and store – the plugin handles authentication and billing behind the scenes.
It ships alongside a standalone CLI (@zeroxyz/cli) and an MCP connector at mcp.zero.xyz, so the same underlying tool access is available whether you’re working inside Claude Code, from the command line directly, or through any other MCP-compatible agent.
Where this fits against connect-apps
This is a useful contrast to next week’s post on Composio’s connect-apps, which focuses on giving Claude access to specific named services you already use – Gmail, Slack, GitHub. Zero is aimed more at the long tail: tools you wouldn’t bother setting up in advance because you’ll only need them once.
Installing it
As with most Claude Code plugins, it’s a marketplace add followed by an install:
/plugin marketplace add zero-plugins/zero
/plugin install zero@zero-pluginsNext Sunday, the last post in this series: connect-apps, Composio’s uniform execution layer for giving Claude working access to the everyday services you already have accounts with.
Leave a Reply
You must be logged in to post a comment.