> For the complete documentation index, see [llms.txt](https://docs.miuro.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.miuro.ai/miuro-claw/claw-as-platform.md). # Claw as Platform ***Developer & Platform Capabilities (Claw as Platform)*** Miuro Claw is not only a creative tool for end users, but also an open music capability platform designed for AI Agents. Miuro follows an **“MCP First”** strategy, with the goal of becoming the default music capability provider within the AI Agent ecosystem. ### **Why Build a Platform?** Current mainstream AI music products (such as Suno and Udio) are closed consumer-facing tools and still do not offer official public APIs. Developers who want to integrate their capabilities must rely on unofficial wrappers, which carry legal risks (violating Terms of Service) and lack stability guarantees. Miuro Claw differentiates itself by: * Providing official, stable, and auditable open interfaces * Supporting **MCP (Model Context Protocol)**, a cross-vendor standard * Enabling capability calls from both cloud and on-device environments * Implementing secure billing and rate limiting through a unified LLM Gateway This positions Miuro with the potential to become the **“default music capability provider for AI Agents.”** *** ### **Currently Available Capabilities** | Capability | Description | Maturity | | ------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | -------- | | **Personal Access Token (PAT)** | Users can issue scoped API tokens for Agent/script integration, with instant revocation support | ✅ Live | | **Fine-grained Permission Control** | Supports minimal permission scopes such as `songs:read/write` and `credits:read` | ✅ Live | | **Agent API** | Provides the `/api/agent/v1` endpoint for song generation, library queries, credit checks, etc. | ✅ Live | | **Unified LLM Gateway** | All model calls (web, device, and Agent) are routed through a single gateway with unified account-based billing | ✅ Live | | **Call Auditing** | Every API call records token, tool, parameters, result, and duration for full traceability | ✅ Live | | **Rate Limiting & Replay Protection** | Rate limiting by token/account/IP, with automatic alerts and graceful degradation for abnormal behavior | ✅ Live | | **MCP Server (stdio)** | Provides the npm package `@miuro/mcp`, enabling one-click integration with Claude Desktop, OpenClaw, Cursor, etc. | ✅ Live | | **OpenClaw Skill Package** | Miuro skill package that can be directly loaded into the OpenClaw runtime | ✅ Live | *** ### **Integration Methods for Developers** Developers can integrate Miuro’s music capabilities in the following ways: 1. **MCP Protocol Integration (Recommended)** * Quickly connect music capabilities to Agents that support MCP (such as Claude or Cursor) via the standard MCP Server. * Supports both stdio and HTTP/SSE modes. 2. **RESTful API Integration** * Use PAT + Agent API for traditional HTTP calls. * Suitable for developers with existing backend systems or custom-built Agents. 3. **Skill Package Integration** * Directly install the Miuro Skill package in environments that support OpenClaw for deeper integration. *** ### **Planned Capabilities** | Capability | Description | Maturity | | --------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------------- | | **MCP Server (HTTP/SSE)** | Remote-hosted MCP Server that allows integration without local installation | 📋 Planned | | **MCP Resources & Prompts** | Provides resources (songs, libraries, charts) and pre-built prompt templates | 📋 Planned | | **Skill Hub (Skill Marketplace)** | A marketplace where developers can publish, price, and monetize skills with platform revenue sharing | 🚧 In Progress | | **Async Callbacks / Webhook** | Event notifications (generation completed, failed, timeout) via signed webhooks | 📋 Planned | | **Sandbox Testing Environment** | Get test tokens and limited free quota upon registration with independent metering | 📋 Planned | | **Structured Creation API** | Inspired by ElevenLabs Composition Plan; supports declarative multi-section creation planning | 🔭 Vision | | **Developer Documentation Site** | `developers.miuro.ai` (bilingual Chinese/English) with installation guides, API references, and SDK examples | 📋 Planned | *** ### **Strategic Significance of Platformization** By opening APIs and building the MCP ecosystem, Miuro Claw is evolving from a single product into foundational infrastructure for music capabilities. This means: * Other AI Agents can easily call professional music generation and arrangement capabilities * Developers no longer need to train music models from scratch to offer high-quality music features to their users * Miuro can gain broader ecosystem reach and usage scenarios through platformization Miuro believes that in the Agent era, **“Capability as a Service”** will become a major trend, and music capability is a high-value vertical with clear demand. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.miuro.ai/miuro-claw/claw-as-platform.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.