Connect a Client Using an MCP Server
Interact with agents from multiple clients and with Mosaic models in a ChatGPT-like interface connected to an MCP Server. Before you can interact, you must connect the client.
For an overview of using a MCP server, see Interact with Agents and Mosaic Models Using an MCP Server.
Connecting a client is the same procedure for agents and for Mosaic; only the URL differs.
Copy the URL for your server from Server URLs and add it in your client, then sign in to Strategy Library when prompted. Connect to Clients provides steps for common MCP clients.
Prerequisites
-
You must have the privileges outlined below.
| Action | Required Privilege | Notes |
| Connect to MCP server |
Authenticated user |
Clients must have valid credentials and tokens |
| Use MCP Server | Beginning in Strategy One (March 2026), must be set to use MCP for agents and Mosaic | |
| List agents | Read access | Only users with permission can list agents |
| Ask agent | Run AI Bots | Must be allowed to execute actions and questions |
-
You cannot be an administrator or in the Platform Support Administrator user group.
-
Agents must be certified to be used in the MCP server. This allows you to determine which agents are available. For example, if you want to test only production agents, you can certify only those.
-
The agent must be added to Library.
Server URLs
In the following URLs, env-domain serves as a placeholder for your environment ID. Replace env-domain with your environment's domain and append the corresponding URL.
-
Agent MCP Server URL:
https://env-domain.trial.cloud.strategy.com/collaboration/mcp/agent -
Mosaic MCP Server URL:
https://env-domain.trial.cloud.strategy.com/collaboration/mcp/mosaic
For clients that use manual OAuth configuration, use the following values:
| Connection | URL |
| Authorization URL | https://env-domain.trial.cloud.strategy.com/collaboration/authorize |
| Token URL | https://env-domain.trial.cloud.strategy.com/collaboration/token |
| Refresh URL | https://env-domain.trial.cloud.strategy.com/collaboration/token |
| Scopes | offline_access |
Connect to Clients
Enable the MCP Server before connecting MCP clients to it for interaction with agents and Mosaic.
Select the connection procedure for the client you are working with:
Connect to the MCP Server using Claude
-
Log into Claude PRO version.
-
In the toolbar in the chat box, click the Search and Tools icon
and select Manage Connectors. -
Click Browse Connectors.
-
In the introductory paragraph, click the link for add a custom one.
-
In the Add Custom Connector window, type a Name for the connector.
-
Type your Remote MCP Server URL using the following syntax:
https://env-domain/collaboration/mcp/agent
Replace domain with your MCP server.
-
Beginning in Strategy One (March 2026), you can access Mosaic models in the MCP server. Use this syntax instead: https://env-domain/collaboration/mcp/mosaic.
-
-
Click Add.
-
If the same window opens again, click Cancel.
-
Check that your new connector displays in the list of connectors.
-
Click Connect next to your new connector.
-
Strategy Library opens. Log in with your credentials.
-
At the message, click Open Claude.
Your new connector now displays Configure instead of Connect.
-
Click the New Chat icon
in the sidebar.
Connect to the MCP Server using Copilot Studio
-
Open Copilot Studio.
-
Click Agents in the toolbar on the left.
-
Create a new agent by clicking Create Blank Agent in the toolbar or click an existing agent.
-
Scroll down to the Tools section and click Add Tool.
-
Click New Tool on the right, below the suggestions.
-
Click Model Context Protocol.
-
Type the Server Name, Server Description, and Server URL including the complete server path. For the URL, use the following syntax:
https://env-domain/collaboration/mcp/agent
Replace domain with your MCP server.
-
Beginning in Strategy One (March 2026), you can access Mosaic models in the MCP server. Use this syntax instead: https://env-domain/collaboration/mcp/mosaic.
-
-
For the Authentication, select OAuth 2.0.
-
For the Type, select Manual.
-
Type your Client ID, Client Secret, Authorization URL, Token URL Template, Refresh URL, and Scopes.
-
Click Create.
-
Copy the Redirect URL displayed in the Preview window. Provide it to the MCP owner, so they can help to add the redirect_url in the MCP configuration.
-
The MCP owner adds it in Workstation, in the environment's properties. It is located on the Library page, in the Model Context Protocol for Agent section, as shown below:
-
-
Click Next.
-
To establish the connection, click Not Connected.
-
After you are signed in and connected, click Create.
-
A new browser window displays. Strategy Library opens. Log in with your credentials.
You can now interact with your agent or Mosaic model using Copilot Studio.
Connect to the MCP Server using Gemini Enterprise
-
Go to the Google Agent Development Kit site and follow the installation guide to set up the Agent Development Kit on your machine. Once installed, you will have a deployment file ready to work with.
If you have an existing ADK deployment file in your GitHub repository, go to the next step.
-
Create a Python virtual environment.
-
Install all dependencies from pyproject.toml.
-
Ensure the mcp_url and AUTH_ID match in both agent.py and deploy.py.
-
Deploy your ADK agent to the Vertex AI Agent Engine by running the following command:
python deploy.py -
Once deployment succeeds, you can view your agent running in the Agent engine:
-
Add a new resource to the Gemini Enterprise Authorization server and register the ADK agent to Gemini Enterprise. Follow the steps below:
-
Search for Gemini Enterprise.
-
Navigate to agents.
-
Click Add Agent.
-
Select Custom Agent Via Agent Engine.
-
-
Add a new authorization, ensuring that the Authorization ID matches the AUTH_ID deployed in the deploy.py script.
-
Click Next.
-
Add your agent's configuration. Follow the steps below:
-
Use the same Authorization ID as above.
-
Type the resource name of the ADK engine in the Agent Engine Reasoning box. You can find the resource name in the Agent Engine portal.
-
Click Create.
-
Connect to the MCP Server using ChatGPT
The Callback URL varies depending on the address of the connected MCP server. You need to copy it from ChatGPT into Workstation before completing the connection.
-
Open ChatGPT.
-
In the bottom left, click your name.
-
Click Settings.
-
In the navigation pane on the left, click Apps.
-
Click Create App.
-
Fill in the information to create the app.
-
Add an Icon image file (optional).
-
Type a Name, an optional Description, and the MCP Server URL using the format https://env-domain/collaboration/mcp/agent, replacing domain with your MCP server.
-
Beginning in Strategy One (March 2026), you can access Mosaic models in the MCP server. Use this syntax instead: https://env-domain/collaboration/mcp/mosaic.
-
-
From the Authentication drop-down list, select OAuth.
-
-
Click Advanced Settings.
-
In the Registration Method, select User-Defined OAuth Client.
-
Click the Click to Copy icon
next to the Callback URL.
-
Add the Callback URL to Workstation:
-
Open Workstation.
-
Connect to the environment.
-
Right-click the environment and select Properties.
-
In the navigation pane on the left, click Library.
-
Scroll to the Model Context Protocol for Agent section.
-
Click Add New URL next to Callback URL (for Server Applications) and paste the copied URL.
-
Click OK to save the change.
-
-
Return to ChatGPT.
-
In the Advanced Settings panel, select Dynamic Client Registration (DCR) from the Registration Method drop-down list.
-
In the New App panel, select the check box next to I understand and want to continue.
-
Click Create.
You can now interact with your agent or Mosaic model in ChatGPT.
Connect to the MCP Server using AWS/Amazon Quick Suite
-
Log into the AWS access portal.
-
Click AdministratorAccess.
-
Search for Amazon Quick Suite and select it.
-
In the navigation bar on the left, click Connectors.
-
Click the Create for Your Team tab. Click Model Context Protocol.
-
Click Create New.
-
Type the Name and Description.
-
In the MCP Server Endpoint box, copy and paste your MCP server URL using the following syntax:
https://env-domain/collaboration/mcp/agent
Replace domain with your MCP server.
-
Beginning in Strategy One (March 2026), you can access Mosaic models in the MCP server. Use this syntax instead: https://env-domain/collaboration/mcp/mosaic.
-
-
Click Next.
-
From the OAuth Configuration drop-down list, select Default OAuth App.
-
If metadata discovery fails, it falls back to user authentication. In that case, type the Client ID, Client Secret, Token URL, and Authorization URL.
-
-
Click Create and Continue.
-
Review the list of enabled actions. Click Next.
-
After publishing, click Try It to test the MCP, or continue with the next step to test.
Start Testing
-
In the navigation panel on the left, click Chat Agents.
-
To interact with Mosaic models, see Mosaic Workflows.
-
-
Click Create Chat Agent.
-
If you want to specify the agent's persona, describe it, then click Generate. If not, click Skip.
-
Type a name in the box at the top of window.
-
In the Actions section at the bottom of the window, click Link Actions.
-
Select MCP Agent, then click Link.
-
At the top of the window, click Launch Chat Agent.
-
Once the Successfully Launched Chat Agent message displays, you can interact with your agent using AWS.
Connect to the MCP Server using VS Code Copilot
-
Open Copilot.
-
Open a new window using Ctrl+Shift+P.
-
Look up MCP: Add Server.
-
Choose HTTP (HTTP or Server-Sent Events).
-
Paste your MCP server URL using the following syntax:
https://env-domain/collaboration/mcp/agent
Replace domain with your MCP server.
-
Beginning in Strategy One (March 2026), you can access Mosaic models in the MCP server. Use this syntax instead: https://env-domain/collaboration/mcp/mosaic.
-
-
Type a Name for the server.
-
Select Global.
-
Click Allow authentication.
-
Click Open the external website.
-
Strategy Library opens. Log in with your credentials.
-
In the window, click Open Visual Studio Code.
-
Ensure your mcp.json file looks like the image below, with your own URL. Click Start above the mcp line.
-
Click Allow to connect.
-
Ensure that the MCP connection is running, by checking the mcp.json file for the Running status.
