MCP Servers
platform.extensions.mcp-workspace.servers
An MCP server entry connects a remote Model Context Protocol server so the assistant can use its tools.
To learn what MCP servers do, see MCP Servers in the Tool Studio docs.
- Endpoint:
/platform/extensions/mcp-workspace/servers| Methods: GET, PATCH, POST - Request shape: fields go at the top level of the JSON body, with no
resourcewrapper. The item’sidgoes in the URL for reads and updates, not in the body. - Updates: a JSON merge-patch with
version: {num, change_description}from your last read. Lists of objects merge row by row, so read first and send the whole list when you remove or reorder rows. See Tool Studio. - References: Uses an HTTP connector through
connector_id(the connector’sid). Productivity assistants refer to the server by itsidinmcp_server_ids.
Endpoints
All paths are relative to https://api.moveworks.ai/configurations/v1alpha1. Each endpoint page lists the request and response schema, an example, and the errors it can return.
Rules the API checks
nameandconnector_idare required, andnameis unique in your organization.- The connector must use an auth type that MCP servers support:
oauth2withauthorization_code_grantandpkce_algorithm: OAUTH2_PKCE_ALGORITHM_SHA256. enableddefaults tofalse. Set it totrueto make the server available.launch_configsets the audience with at most one ofallow_all,allowed_users,blocked_usersorallowlist_rule_dsl.allow_all: falsemeans no one can use it.- Changes to the server’s tools show up in new conversations only.