MCP Workspace | Moveworks

Controlled Availability

MCP Workspace is in Controlled Availability for a limited set of customers. To join, register your interest on the Moveworks Community; Moveworks turns it on for selected organizations. Capabilities and limits may change.

MCP Workspace is where a Tool 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 credentials configured for that connection.

Connect a server

Connect a preconfigured or custom server, confirm that it returns its tools, and set its tool approval policy.

Pilot and roll out

Give the server to a small audience, test real requests, and decide when to widen access.

Troubleshooting

Find the tool call behind a response, then work through a failed request stage by stage.

Requirements and limits

Check supported transports, authentication, and server requirements, and plan around current limits.

What MCP changes

Before MCP, adding a new system often meant building and maintaining a Tool 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

An admin connects an MCP server with its endpoint and authentication configuration.
MCP Workspace retrieves the server’s tool inventory.
A user asks for help in a conversation. The assistant selects a relevant tool and calls it with the connection’s configured access.
The tool result returns in the conversation.

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	Tool Studio plugin
Run a live lookup or standard action against a trusted external tool	MCP Workspace

MCP Workspace or a Tool Studio plugin?

Use MCP Workspace when a trusted server already exposes a bounded action or live lookup. Use a Tool Studio plugin when you need to control the business rules, systems, and conversation design for a mission-critical workflow.

Use MCP Workspace when	Use a Tool 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.

If the system you need doesn’t already have an MCP server, build a plugin in Tool Studio instead.

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.

ServiceNow MCP servers

ServiceNow’s MCP Server Console can expose a Knowledge Graph, or existing Subflows and Actions, as tools on an MCP server on your instance. These guides cover the ServiceNow setup and the MCP Workspace connection end to end.

ServiceNow MCP: Knowledge Graph

Answer questions over related ServiceNow data, including data brought in with Workflow Data Fabric.

ServiceNow MCP: Flows and Actions

Run existing Workflow Studio Subflows and Actions from the assistant without rebuilding them in Tool Studio.