CloudClaw
com.mycloudclaw/cloudclaw is a MCP server that links coding agents to a hosted CloudClaw agent with 37+ connectors and 181 tools.
About
com.mycloudclaw/cloudclaw is the MCP entry point for CloudClaw, an AI agent hosting platform that bundles a large connector surface and a marketplace behind a single per-agent endpoint. developers who do not want to self-host every integration can register an agent on mycloudclaw.com, obtain an API key and agent ID, and aim Claude Code or Cursor at the streamable HTTP MCP URL so the coding agent inherits CloudClaw’s tool catalog instead of wiring dozens of servers locally. BYOK vault semantics let you supply provider keys without pasting them into chat logs. This fits Build agent-tooling when your product strategy is “agent plus hosted orchestration” rather than a bare CLI script. It is not a replacement for your application codebase—you still ship UI, auth, and data models—but it compresses time-to-connected-agent for demos and internal ops bots. Operations-minded developers may also use it for long-running hosted agents, though the catalog shelf stays on build agent-tooling because that is where MCP registration decisions usually happen.
- 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.
CloudClaw by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http cloudclaw https://mycloudclaw.com/api/agents/%7Bagent_id%7D/mcp --header "Authorization: Bearer YOUR_TOKEN"Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | Required |
What it does
Connect your IDE agent to a hosted CloudClaw agent that already bundles dozens of connectors and a tool marketplace.
Who is it for?
Best when you want a hosted agent hub with marketplace extensions and BYOK instead of hand-rolling every integration server.
Skip if: Skip if you require fully self-hosted, air-gapped agent runtimes with no third-party hosting.
What you get
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
By the numbers
- 37+ connectors per published description
- 181 tools exposed through the platform
- Server version 1.0.0 with per-agent MCP URL template
Recommended MCP Servers
0Latency MemoryPersistent memory layer for AI agents.
0nMCP — Universal AI API OrchestratorUniversal AI API Orchestrator — 1,554 tools, 96 services.
0xHumans Protocol MCPMCP for AI agents: financing, skills, lending on Base1k Patient Mcp1k patient MCP server
1trippulse1trip PULSE: 21-tool AI travel planner.
3D AI Agent Avatar3D AI Agent Avatar — render any GLB, give it a Solana wallet, a voice, and pump.fun powers.89How it compares
Hosted multi-connector agent platform MCP, not a single-purpose API bridge like one CRM or one database server.
FAQ
Who is com.mycloudclaw/cloudclaw for?
Developers 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.