WPS MCP MCP integration for AI agents.
Connect AI agents to WPS MCP through 9 structured actions, including get file info, create file with content, and call tool. Review authentication, inputs, w…
- ACTION CONTRACTS
- 9
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the WPS MCP integration exposes
The WPS MCP Agent App exposes 9 provider-backed actions for productivity and storage work. Its current contract lets an authorized agent get metadata, drive details, extended attributes, or permissions for a wps file, create a wps document, pdf, spreadsheet, or smart sheet and populate it with json-friendly content, and call a current wps mcp tool with json arguments after checking its live schema and behavior annotations. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected WPS MCP account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real WPS MCP capabilities.
Showing 9 of 9 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_file_infoREADGet metadata, drive details, extended attributes, or permissions for a WPS file.
INPUTS: file_id / link_id / url / with_drive / with_ext_attrs
create_file_with_contentWRITECreate a WPS document, PDF, spreadsheet, or smart sheet and populate it with JSON-friendly content.
INPUTS: name / file_extension / content / drive_id / parent_id
call_toolREVIEWCall a current WPS MCP tool with JSON arguments after checking its live schema and behavior annotations.
INPUTS: toolName / arguments
create_folderWRITECreate a folder in a known WPS drive and parent folder.
INPUTS: drive_id / parent_id / name / on_name_conflict / parent_path
list_filesREADList entries in a known WPS drive folder with filtering, sorting, and pagination.
INPUTS: drive_id / parent_id / filter_exts / filter_type / order
list_my_filesREADList entries in the root of the connected user's WPS cloud documents with filtering, sorting, and pagination.
INPUTS: filter_exts / filter_type / order / order_by / page_size
list_toolsREADDiscover the current WPS document, spreadsheet, presentation, PDF, and workspace MCP tools with their live input schemas.
read_fileREADRead a WPS cloud document as Markdown, plain text, structured KDC data, or spreadsheet cells according to its format.
INPUTS: file_id / link_id / url / format / enable_upload_medias
search_filesREADSearch WPS cloud documents and folders across drives by file name, content, creator, location, type, or time.
INPUTS: keyword / type / file_type / drive_ids / parent_ids
INPUT CONTRACTS
Know what the action needs before it runs.
get_file_info
file_idOPTIONAL- A WPS file ID used to select the document.
link_idOPTIONAL- A WPS share link ID used to select the document.
urlOPTIONAL- A WPS document URL used to select the document.
with_driveOPTIONAL- Whether the response should include the containing drive.
with_ext_attrsOPTIONAL- Whether the response should include extended attributes.
create_file_with_content
nameREQUIRED- The complete file name, such as Weekly Report.docx.
file_extensionREQUIRED- The file extension without a leading dot.
contentOPTIONAL- UTF-8 Markdown content for OTL, DOCX, or PDF files.
drive_idOPTIONAL- The destination WPS drive ID. Defaults to the personal drive.
parent_idOPTIONAL- The destination folder ID. Defaults to the root folder 0.
call_tool
toolNameREQUIRED- The exact tool name returned by list_tools.
argumentsOPTIONAL- JSON arguments matching the inputSchema returned for the selected tool.
create_folder
drive_idREQUIRED- The destination WPS drive ID.
parent_idREQUIRED- The parent folder ID. Use 0 for the drive root.
nameREQUIRED- The folder name without a file extension.
on_name_conflictOPTIONAL- How WPS should handle an existing name.
parent_pathOPTIONAL- Relative folder path segments that WPS should create when missing.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get File Info
Get metadata, drive details, extended attributes, or permissions for a WPS file. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_file_infoControl Create File With Content
Create a WPS document, PDF, spreadsheet, or smart sheet and populate it with JSON-friendly content. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_file_with_contentVerify with List Files
List entries in a known WPS drive folder with filtering, sorting, and pagination. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_filesSAFETY BOUNDARY
Operate WPS MCP with explicit limits
- Authorize WPS MCP with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in WPS MCP rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the WPS MCP task completed successfully.
CONNECTION MODEL
API key
Access Token sent to WPS MCP as an Authorization bearer token. Sign in and copy the Token from https://account.wps.cn/usercenter/agent-identity?isclient=false.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by WPS MCP.