MCP Workspace
MCP Workspace is in Controlled Availability in every region except GovCloud. To get access, register on the Moveworks Community, and Moveworks turns it on for your organization. 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.
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.
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.
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.
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.