> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://help.moveworks.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://help.moveworks.com/_mcp/server. # MCP Workspace MCP Workspace is available to a limited set of customers. Moveworks is validating the experience and gathering feedback, so capabilities and limits may change. To request access, [register your interest](https://community.moveworks.com/p/mcp-workspace-controlled-availability). MCP Workspace is where an Agent Studio admin connects and governs MCP servers. The MCP client is the runtime that lets the Moveworks assistant discover and call those servers' tools in a conversation, using the user's credentials in the upstream system. Connect a preconfigured or custom server, verify its authentication, and make it available to a pilot. Reduce tool overlap, test the server with a pilot, and decide when to expand access. Plan around current CA limits and work through a failed request stage by stage. Prepare a private server for MCP Workspace without turning it into a full plugin workflow. ## What MCP changes Before MCP, adding a new system often meant building and maintaining an Agent Studio plugin for a specific use case. With MCP Workspace, an admin can connect a trusted remote server that already exposes the tools the assistant needs. The server still defines its tools and enforces access. MCP Workspace gives you a place to connect the server, review its tool inventory, and control which users can reach it. This helps with two common problems: * **Coverage limited by development capacity**: You can connect a new system when it already exposes an MCP server, without first building a plugin for every bounded use case. * **Server sprawl without control**: Admins have one place to review, enable, and scope access to each connected server. ## How it works 1. An admin connects an MCP server with its endpoint and authentication configuration. 2. MCP Workspace retrieves the server's tool inventory. 3. A user asks for help in a conversation. The assistant selects a relevant tool and calls it with that user's upstream access. 4. The tool result returns in the conversation. ```mermaid flowchart LR Admin["Agent Studio admin"] -->|connects and governs| Workspace["MCP Workspace"] User["User"] -->|makes a request| Assistant["Moveworks assistant"] Workspace -->|makes the server available| Assistant Assistant -->|calls a tool with the user's upstream access| Server["Remote MCP server"] Server -->|returns a result| Assistant ``` ## Where MCP fits MCP is one of several ways to connect the assistant to your systems. | Use | Choose | | -------------------------------------------------------------------- | ------------------- | | Find or research content across files and knowledge sources | Enterprise Search | | Run a controlled, organization-specific business process | Agent Studio plugin | | Run a live lookup or standard action against a trusted external tool | MCP Workspace | ## MCP Workspace or an Agent Studio plugin? Use MCP Workspace when a trusted server already exposes a bounded action or live lookup. Use an Agent Studio plugin when you need to control the business rules, systems, and conversation design for a mission-critical workflow. | Use MCP Workspace when | Use an Agent Studio plugin when | | ------------------------------------------------------ | --------------------------------------------------------------------------------- | | The server already exposes the tool you need. | You need organization-specific actions or business rules. | | The request is a lookup, read, or standard write. | The workflow is mission-critical, multi-step, or needs predictable orchestration. | | You can accept the server's tool surface and behavior. | You need control of inputs, validation, outputs, and lifecycle. | For example, use MCP Workspace to create a Linear issue, look up a GitHub pull request, or fetch a Slack thread. Use a plugin for a workflow such as new-hire onboarding that coordinates several internal systems and your own process rules. ## Common MCP Use Cases MCP Workspace works best for bounded, transactional work against a connected app. | Work type | Example | | --------------- | --------------------------------------------------------------------------------------- | | Lookup | Check open GitHub pull requests or the current ServiceNow incident owner. | | Standard action | Create a Linear issue or post a Slack update. | | Bulk action | Add a comment to a clearly scoped set of issues. | | Multi-app work | Read action items from one app, then create tasks in another after you state each step. | For bulk actions and multi-app work, be explicit about the scope and steps. The assistant does not automatically compose a complex workflow from a vague goal. ## Start with a pilot Start with a server for a new app or use case, a small pilot audience, and a few clear requests. That gives you a clean way to validate tool selection, authentication, and results before the server competes with the rest of your tool environment. Use [Connect and Manage Servers](/agent-studio/mcp-workspace/connect-and-manage-servers) to set up the server, then [Configure and Test MCP Workspace](/agent-studio/mcp-workspace/configure-and-test-mcp-workspace) to configure and validate the pilot. ## Common Questions You can connect compatible remote MCP servers. Both preconfigured and custom server paths support DCR when the server supports it. If a custom server does not support DCR, configure its authentication through an HTTP connector. Local MCP servers are not supported. The user's upstream permissions apply. Connecting a server does not grant a user access to data or actions that the upstream system does not already allow. Standard log redaction for personally identifiable information and credentials applies to MCP activity. Configure data handling for each server in [Launch Configuration](/agent-studio/access-control/end-user-access-control/launch-configuration), as you would for an Agent Studio plugin. No. Governance is server-level during Controlled Availability. You enable, disable, and set access for the whole server. Yes, when the request names the apps, scope, and each intended step. Review write-capable servers carefully because MCP Workspace does not add a confirmation gate before a write. Open **More info > Reveal AI Reasoning** on a response and look for a tool call in the format `mcp____`.