Connect and Manage Servers

Connect a trusted MCP server, verify it, and make it available to the right audience.

Controlled Availability

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.

MCP Workspace is where an Agent Studio admin connects MCP servers and controls which users can reach them. This page covers the connection paths, authentication checks, access controls, and the first-time user experience.

Before You Start

Connecting servers is an Agent Studio admin task.
A connected server does not grant anyone access to its upstream system. Each tool call uses the individual user’s credentials and permissions in that system.
Start with apps and use cases that do not overlap with an existing plugin or Enterprise Search. See Configure and Test MCP Workspace.

Use trusted servers only

Moveworks does not review, approve, or vet MCP servers or their tools. Review the full inventory before you make a server available. A server decides which tools and guardrails it exposes, including whether it offers write or destructive actions.

Choose a Connection Path

Server type	Use this path
A server in the preconfigured list	Select the server and use Dynamic Client Registration (DCR) to discover its OAuth settings and create the connection.
Any other MCP-compatible remote server	Select Custom Server, enter the server URL and path, then use DCR to create the connection. If the server does not support DCR, create or reuse an HTTP connector.

Connect a Preconfigured Server

Preconfigured servers have their connection details filled in for you. MCP Workspace uses DCR to discover their OAuth settings and register the client during setup.

Create an MCP server

In Agent Studio, create an MCP server and select the server from the preconfigured list.

Discover OAuth settings

Select Discover OAuth Settings and complete the authorization flow.

Preview tools

In the Tools section, select Preview Tools. If you see the expected inventory, the server is reachable and the administrator connection can authenticate.

Select a preconfigured server, discover its OAuth settings, and preview its tools.

Tool names and descriptions come from the server and are view-only in Agent Studio. The tools shown to an administrator are not necessarily the same tools each end user sees. MCP Workspace retrieves tools for each user at runtime based on that user’s upstream permissions.

Connect a Custom Server

Use the Custom Server path for a compatible remote server that is not in the preconfigured list, including a homegrown server.

Enter the server endpoint

Select Custom Server, then enter the base URL and path from the server owner’s documentation.

Choose the authentication path

Discover the server’s OAuth settings and use DCR to create the connection. If the server does not support DCR, create or reuse an HTTP connector that you already configured for that system. Use the server owner’s exact base URL, redirect URI, scopes, and client details when required.

Verify the connection

Generate a token from MCP Workspace, then preview the tool inventory. If you see no tools or an authentication error, correct the endpoint or connector before you continue.

Custom Server form showing the MCP path, connector selection, and OAuth discovery server URL. — Custom Server setup separates the MCP path from the authentication connector and OAuth discovery URL.

MCP server connector section showing an unauthorized existing connector and an Authenticate button. — If the selected connector is unauthorized, authenticate it before you continue.

DCR works with preconfigured and custom servers

MCP Workspace supports DCR for both connection paths when the server supports it. Without DCR, a developer or administrator configures a custom server through an HTTP connector. Neither path grants end users access to the upstream system.

Verify Authentication

For a custom server that does not support DCR, configure the required OAuth 2.1 connection through an HTTP connector. Then generate a token in MCP Workspace and select Preview Tools to verify that the administrator connection can authenticate and retrieve the expected inventory.

Preview Tools validates the administrator connection. It does not guarantee that every user will see the same tool inventory. MCP Workspace retrieves tools for each user at runtime based on that user’s upstream permissions.

Publish, Enable, and Set the Audience

After you verify the server, publish your changes. The Enabled toggle turns an MCP server on or off. Launch Configuration controls which users can reach an enabled server. Start with a defined pilot audience instead of launching a new server broadly.

Launch Configuration tab and Enabled toggle annotated to show that Launch Configuration controls the audience and Enabled turns the server on or off. — Enabled turns a server on or off. Launch Configuration controls its audience.

MCP Workspace controls access at the server level. You cannot allow or block individual tools inside a server. Review the full tool inventory before you enable the server, especially when it exposes write actions.

Universal Assistant only during Controlled Availability

MCP tools run in the Universal Assistant. Specialized Assistant support is not available during Controlled Availability.

User permissions still apply

Connecting a server does not grant access to its upstream system. Each user can use only the tools and data that the server and upstream system allow for that user.

What Users Do the First Time

The first time a user asks the assistant to use a connected app, the assistant prompts that user to sign in within the conversation. After they complete sign-in, later requests can use the server without prompting again.

Example conversation in which the assistant asks a user to connect an app before completing a request. — An example of an in-chat prompt to connect an app the first time it is needed.

If a server works for some users but not others, check whether the affected users have completed this first-time authentication. Use Limitations and Troubleshooting when sign-in or a later request fails.