Skip to main content
ClawAgoraClawAgora
Back to Blog

From ZIP Uploads to MCP: Our Agent-Native Approach

Rockman Zheng·
From ZIP Uploads to MCP: Our Agent-Native Approach

image: /blog/images/from-zip-uploads-to-mcp-agent-native.png

When we first built ClawAgora's seller upload flow, the process looked like this:

  1. Seller tells their agent to export the workspace
  2. Agent scans, sanitizes, and packages files into a ZIP
  3. Seller finds the ZIP file on disk
  4. Goes to ClawAgora, drags it into the upload zone
  5. Fills in title, description, category, pricing
  6. Submits

We went through this exact flow on March 9, packaging our first workspace — a personal research assistant with 18 skills — for listing. The agent did the hard work (scanning ~500 files, sanitizing persona references, packaging 88 files into a 152KB ZIP), but the human still had to be the courier between the agent and the platform.

Six steps. Multiple context switches. The seller acting as middleware between their agent and our marketplace.

The problem with copy-paste workflows

This isn't unique to ClawAgora. Most AI agent tooling today relies on human-in-the-loop patterns — copy this prompt, paste it there, download this file, upload it here. We're building tools for agents but forcing humans to be the glue.

The irony is that agents are supposed to reduce manual work, not create new busywork.

Discovering ACP and MCP

While researching how to improve this, we came across the Agent Client Protocol (ACP) — a new standard by JetBrains and Zed for connecting code editors to AI agents. ACP itself is designed for editor-to-agent communication, but it validated an important pattern: standardized protocols between clients and agents.

More importantly, ACP delegates tool use to the Model Context Protocol (MCP). And MCP is something agents like OpenClaw and Claude Code already support natively.

This gave us the key insight: what if sellers' agents could talk directly to ClawAgora through MCP tools?

The MCP server approach

Instead of building a custom protocol, the plan is to publish a @clawagora/mcp-server npm package. Sellers would add it to their agent's MCP configuration once:

{
  "mcpServers": {
    "clawagora": {
      "command": "npx",
      "args": ["@clawagora/mcp-server"],
      "env": {
        "CLAWAGORA_API_KEY": "sk-..."
      }
    }
  }
}

The MCP server exposes tools like validate_workspace, upload_workspace, and create_draft_listing. The agent calls these as native tool invocations — no copy-paste, no manual upload, no context switching.

What the new seller experience would look like

Seller: "Export and list my workspace on ClawAgora"

Agent: Scanning workspace files... found 47 files.
Agent: Sanitizing — stripped 3 API keys, 1 credential file.
Agent: Packaging workspace into ZIP (4.2 MB).
Agent: Validating against ClawAgora requirements... passed.
Agent: Uploading to ClawAgora... complete. 3 skills detected.
Agent: Draft created. Review at https://clawagora.com/seller/workspaces/abc123

One natural-language command. Zero context switches. The seller reviews the draft on the website and publishes.

Six steps become two.

Why this matters beyond ClawAgora

We think this pattern — agents connecting to platforms via MCP — will become standard for agent-native marketplaces. The alternative (human-mediated copy-paste workflows) doesn't scale as agents become more capable.

ACP's tight coupling with MCP also means that as editor-agent integration matures, any ACP-compatible editor will automatically be able to use ClawAgora's MCP server. We get future compatibility for free.

What's next

We're building this in phases:

  1. MCP Server (current focus) — native tool calls from any MCP-capable agent
  2. CLI fallback — for agents that can run shell commands but don't support MCP
  3. Real-time dashboard — WebSocket-based live view of agent activity during upload

If you have an OpenClaw workspace you want to list, the current flow works today — become a seller and use the curation prompt in the seller center to package your workspace. We are building toward a future where your agent handles the entire listing process natively. In the meantime, reach out on X or at help@clawagora.com if you want to be part of shaping that experience.

For what makes a workspace worth listing, see The Anatomy of a High-Quality Workspace Template. And for the story behind ClawAgora's first listing, read Seller Zero.