ONLYOFFICE DocSpace MCP integration for AI agents.
Connect AI agents to ONLYOFFICE DocSpace through 6 structured actions, including get current user, get folder contents, and get room. Review authentication…
- ACTION CONTRACTS
- 6
- 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 ONLYOFFICE DocSpace integration exposes
The ONLYOFFICE DocSpace Agent App exposes 6 provider-backed actions for productivity and storage work. Its current contract lets an authorized agent get the current user associated with the connected onlyoffice docspace api key, list file and subfolder metadata in an onlyoffice docspace folder or room, and get information about one onlyoffice docspace room. 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 ONLYOFFICE DocSpace account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ONLYOFFICE DocSpace capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_userREADGet the current user associated with the connected ONLYOFFICE DocSpace API key.
get_folder_contentsREADList file and subfolder metadata in an ONLYOFFICE DocSpace folder or room.
INPUTS: folderId / count / startIndex
get_roomREADGet information about one ONLYOFFICE DocSpace room.
INPUTS: roomId
get_userREADGet one ONLYOFFICE DocSpace user by user ID.
INPUTS: userId
list_roomsREADList rooms available to the connected ONLYOFFICE DocSpace API key.
INPUTS: count / startIndex / search
list_usersREADList users in the connected ONLYOFFICE DocSpace portal.
INPUT CONTRACTS
Know what the action needs before it runs.
get_folder_contents
folderIdREQUIRED- The numeric folder or room ID to inspect.
countOPTIONAL- Maximum number of entries to return.
startIndexOPTIONAL- Zero-based index from which to start returning entries.
get_room
roomIdOPTIONAL- The numeric room ID to retrieve.
get_user
userIdOPTIONAL- The user ID to retrieve.
list_rooms
countOPTIONAL- Maximum number of resources to return.
startIndexOPTIONAL- Zero-based index from which to start returning resources.
searchOPTIONAL- Text used to filter matching resources.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current User
Get the current user associated with the connected ONLYOFFICE DocSpace API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_userVerify with Get Folder Contents
List file and subfolder metadata in an ONLYOFFICE DocSpace folder or room. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_folder_contentsSAFETY BOUNDARY
Operate ONLYOFFICE DocSpace with explicit limits
- Authorize ONLYOFFICE DocSpace with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned ONLYOFFICE DocSpace data may still be sensitive and should be minimized before it enters model context.
- 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 ONLYOFFICE DocSpace rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the ONLYOFFICE DocSpace task completed successfully.
CONNECTION MODEL
API key
Create an API key in DocSpace under Settings > Developer Tools > API keys.
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
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
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 ONLYOFFICE DocSpace.