Omni Reader Multimodal Document Parser for Openclaw

1. Create a Cue API key yourself at cuecue.cn. The agent cannot create or inspect your key. For the local Bridge, Node.js 20.12 or later is required.
2. For local files or local result-management tools, install the Bridge:

npx -y @cueai/[email protected] setup

3. Configure the local MCP server in your agent configuration, replacing the placeholders with your key and permitted local roots:

{
  "mcpServers": {
    "omni-reader": {
      "command": "npx",
      "args": ["-y", "@cueai/[email protected]"],
      "env": {
        "CUE_API_KEY": "<your-api-key>",
        "OMNI_ALLOWED_ROOTS": "<authorized-local-directories-separated-by-colons>"
      }
    }
  }
}

4. For public or signed HTTPS URLs only, you can configure the remote MCP endpoint instead; it does not support local paths:

{
  "mcpServers": {
    "omni-reader": {
      "type": "streamable-http",
      "url": "https://mcp.cuecue.cn/api/omni-reader/mcp/",
      "headers": {
        "Authorization": "Bearer <your-api-key>"
      }
    }
  }
}

5. Check the Bridge installation and configuration:

npx -y @cueai/[email protected] doctor --json

6. Before parsing, run the lightweight version check when using the Bridge:

npx -y @cueai/[email protected] doctor --silent-check

Use a local path only after the agent obtains your confirmation. The Bridge is limited to user-authorized files and directories. Do not submit a bare oss:// URL; provide an accessible HTTP(S) or signed HTTPS URL instead. For Openclaw Skills setup, choose one connection mode based on the input and required tools.

Inputs and limits

The documented limit is one file per parse request, with a maximum size of 256 MiB. Video is recommended in MP4 (H.264 + AAC); splitting long videos into 15–30 minute segments is advised. Default output is Markdown; hypertext and chunks are available through the documented remote output parameter. The currently supported detail value is text; grounded and layout are unavailable.

MCP tools and result lifecycle

The remote endpoint exposes the first three tools; the local Bridge exposes all seven. Parsing can return an operation_id while processing. Preserve it and poll the same operation rather than resubmitting the source. MCP tool responses may wrap JSON in content[].text, which must be extracted and parsed before reading status fields.

Storage and metadata

• Parsing defaults to no_store=true; the documentation states that source files and results are not stored on the server. Large results over 64 KiB may be temporarily cached locally and automatically cleared after 24 hours.
• Local Bridge result artifacts can be read, saved to a stable file, or discarded. Results are not automatically described as permanent files; use save_result when a stable copy is required.
• Structured errors can include code, failure_scope, retryable, user_action, and request_id. Use these fields to decide next steps and support troubleshooting.
• The parse source accepts an HTTP(S) URL or an authorized local path. Use signed HTTPS links instead of bare oss:// URLs.