CloudClaw
Connect your IDE agent to a hosted CloudClaw agent that already bundles dozens of connectors and a tool marketplace.
Overview
com.mycloudclaw/cloudclaw is a MCP server for the Build phase that links coding agents to a hosted CloudClaw agent with 37+ connectors and 181 tools.
What is this MCP server?
- Platform advertises 37+ connectors and 181 tools exposed via per-agent MCP URL.
- Streamable HTTP at https://mycloudclaw.com/api/agents/{agent_id}/mcp with Bearer API key.
- BYOK vault for bringing your own API keys securely.
- Built-in marketplace for extending agent capabilities.
- Open-source core referenced at github.com/mkc909/cloudclaw-core.
- 37+ connectors per published description
- 181 tools exposed through the platform
- Server version 1.0.0 with per-agent MCP URL template
What problem does it solve?
Maintaining dozens of MCP servers and API keys locally does not scale when you need one agent that can act across many SaaS systems.
Who is it for?
Indie builders who want a hosted agent hub with marketplace extensions and BYOK instead of hand-rolling every integration server.
Skip if: Teams that require fully self-hosted, air-gapped agent runtimes with no third-party hosting.
What do I get? / Deliverables
After you add your CloudClaw Bearer token and agent_id remote, your IDE agent can invoke CloudClaw’s bundled connector tools through one MCP endpoint.
- Single MCP bridge to a CloudClaw agent’s connector and tool surface
- Access to marketplace-backed extensions without local server sprawl
- Centralized secret handling via CloudClaw BYOK vault
Recommended MCP Servers
Journey fit
Hosted agent platforms are adopted when you are assembling agent capabilities into a product, not when you are only sketching an idea. CloudClaw is agent infrastructure—connectors, tools, and BYOK—mapped to the agent-tooling subphase on the build shelf.
How it compares
Hosted multi-connector agent platform MCP, not a single-purpose API bridge like one CRM or one database server.
Common Questions / FAQ
Who is com.mycloudclaw/cloudclaw for?
Solo builders and small teams shipping agent-powered workflows who want CloudClaw to host connectors, tools, and keys behind one MCP URL.
When should I use com.mycloudclaw/cloudclaw?
Use it during Build agent-tooling when you are wiring a coding agent to a production or staging CloudClaw agent with many prebuilt integrations.
How do I add com.mycloudclaw/cloudclaw to my agent?
Create an agent at mycloudclaw.com, copy your API key and agent_id, and configure the MCP remote with Authorization Bearer cc_xxxx pointing at your agent’s /mcp path.