WPS MCP
Operate WPS MCP through your OOMOL-connected account. This skill calls the wps_mcp connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.
Running an action
Assume the user has already installed the oo CLI, signed in, and connected WPS MCP. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.
1. Inspect the contract to get the authoritative input/output schema before building a payload:
oo connector schema "wps_mcp" --action "<action_name>"
2. Run the action with a JSON payload that matches the input schema:
oo connector run "wps_mcp" --action "<action_name>" --data '<json>' --json
--data takes a JSON object string or @path/to/file.json; omit it to send {}.- The response is
{ "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.
Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action’s live schema with oo connector schema to get its authoritative input fields.
Available actions
call_tool — Call a current WPS MCP tool with JSON arguments after checking its live schema and behavior annotations.create_file_with_content — Create a WPS document, PDF, spreadsheet, or smart sheet and populate it with JSON-friendly content. [write]create_folder — Create a folder in a known WPS drive and parent folder. [write]get_file_info — Get metadata, drive details, extended attributes, or permissions for a WPS file.list_files — List entries in a known WPS drive folder with filtering, sorting, and pagination.list_my_files — List entries in the root of the connected user’s WPS cloud documents with filtering, sorting, and pagination.list_tools — Discover the current WPS document, spreadsheet, presentation, PDF, and workspace MCP tools with their live input schemas.read_file — Read a WPS cloud document as Markdown, plain text, structured KDC data, or spreadsheet cells according to its format.search_files — Search WPS cloud documents and folders across drives by file name, content, creator, location, type, or time.
Safety
- Untagged actions are reads (get / list / search) — safe to run directly.
- Actions tagged
[write] change WPS MCP state — confirm the exact payload and effect with the user before running.
- Actions tagged
[destructive] remove or overwrite data — always confirm the target and get explicit approval first.
First-time setup
These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.
-
oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux
irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell
-
Not signed in / authentication error — sign in to your OOMOL account once:
oo auth login
-
scope_missing / credential_expired / app_not_ready / app_not_found — WPS MCP is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:
https://console.oomol.com/app-connections?provider=wps_mcp
-
HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.
Resources
---
name: oo-wps-mcp
description: "WPS MCP (wps.cn). Use this skill for ANY WPS MCP request — reading, creating, and updating data. Whenever a task involves WPS MCP, use this skill instead of calling the API directly."
allowed-tools: [Bash(oo *)]
metadata:
title: "WPS MCP"
author: "OOMOL"
version: "1.0.0"
services: ["wps_mcp"]
icon: "https://static.oomol.com/logo/third-party/wps_mcp.svg"
---
# WPS MCP
Operate **WPS MCP** through your OOMOL-connected account. This skill calls the `wps_mcp` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.
## Running an action
Assume the user has already installed the oo CLI, signed in, and connected WPS MCP. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.
**1. Inspect the contract** to get the authoritative input/output schema before building a payload:
```bash
oo connector schema "wps_mcp" --action "<action_name>"
```
**2. Run the action** with a JSON payload that matches the input schema:
```bash
oo connector run "wps_mcp" --action "<action_name>" --data '<json>' --json
```
- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.
- The response is `{ "data": ..., "meta": { "executionId": "..." } }`; the execution id lives under `meta.executionId`.
Each action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.
## Available actions
- `call_tool` — Call a current WPS MCP tool with JSON arguments after checking its live schema and behavior annotations.
- `create_file_with_content` — Create a WPS document, PDF, spreadsheet, or smart sheet and populate it with JSON-friendly content. [write]
- `create_folder` — Create a folder in a known WPS drive and parent folder. [write]
- `get_file_info` — Get metadata, drive details, extended attributes, or permissions for a WPS file.
- `list_files` — List entries in a known WPS drive folder with filtering, sorting, and pagination.
- `list_my_files` — List entries in the root of the connected user's WPS cloud documents with filtering, sorting, and pagination.
- `list_tools` — Discover the current WPS document, spreadsheet, presentation, PDF, and workspace MCP tools with their live input schemas.
- `read_file` — Read a WPS cloud document as Markdown, plain text, structured KDC data, or spreadsheet cells according to its format.
- `search_files` — Search WPS cloud documents and folders across drives by file name, content, creator, location, type, or time.
## Safety
- Untagged actions are reads (get / list / search) — safe to run directly.
- **Actions tagged `[write]` change WPS MCP state — confirm the exact payload and effect with the user before running.**
- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**
## First-time setup
These are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.
- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):
```bash
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux
```
```powershell
irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell
```
- **Not signed in / authentication error** — sign in to your OOMOL account once:
```bash
oo auth login
```
- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — WPS MCP is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:
```text
https://console.oomol.com/app-connections?provider=wps_mcp
```
- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.
## Resources
- WPS MCP homepage: https://www.wps.cn
