Enable the MCP Server
Beginning in Strategy (October 2026) you can authenticate with API token and use MCP in a multi-tenant environment.
Enable the MCP server before connecting MCP clients to it for interaction with agents and Mosaic models.
An administrator needs to enable the MCP server once for each environment.
-
Once your environment is ready, open Workstation.
-
In the navigation bar on the left, click Environments, if it is not already open.
-
Double-click your environment to connect.
-
Right-click your environment and select Properties.
-
In the navigation bar on the left, click Library.
-
Click Create Trusted Relationship.
-
Scroll to the Cookies section.
-
For SameSite Attribute, select None. Enable HTTP Only and Enable Secure are then selected automatically.
-
Scroll to the Model Context Protocol for Agent section.
-
Add offline_access to the offline scopes and press the Enter key to save it.
-
Generate the client secret by clicking the icon
next to the Client Secret box. -
Copy and save the Client Secret, which is used in the MCP client configuration.
-
The offline access and client secret are required for clients that use manual OAuth configuration (Copilot Studio, Gemini Enterprise, ChatGPT, and AWS if metadata discovery fails).
-
-
Click OK to save your changes.
-
Restart the Library server to apply the changes.
-
For versions before Strategy One (June 2026), restart Tomcat so the trusted relationship and cookie settings take effect.
Authenticate with API Token
Prerequisites
-
To configure authentication with API token, you need Generate API Token privilege.
Generate API Token
-
Once your environment is ready, open Workstation.
-
In the navigation bar on the left, click Environments, if it is not already open.
-
Double-click your environment to connect.
-
Right-click your environment and select Properties.
-
In the navigation bar on the left, click Library.
-
In the Library Server toggle API Token Authentication on.
-
Click Save.
-
In the Navigation pane, click Users & Groups.
-
In the left pane, click API Token tab.
-
Click Create API Token.
-
Search the user you want to create an API token for and click Create.
-
Click Copy next to API token.
Save the API token somewhere safe. You will not be able to see the API token again after you close the window
-
Note the Expires on value under API token. Your API token will only be valid until that date and time.
-
Close the Create API Token dialog.
For steps how to use API Token with CoPilot Studio as an example see: Connect a Client Using an MCP Server
For more information on creating API tokens see: Create API Tokens For Other Users
Using MCP in a Multi‑Tenant Environment
If your Strategy environment is configured for multi‑tenant usage, you can scope MCP access to specific tenants. This ensures that MCP only exposes projects and content that belong to the tenant associated with the user.
Prerequisites
-
The Multi‑Tenant feature must be enabled.
-
The user account must be created and correctly assigned to the appropriate tenant.
Construct MCP endpoints
- Go to Tenants in Workstation.
-
Right-click the selected tenant object and choose Properties.
-
Choose Users and Groups. Make sure the user is assigned to correct tenant.
-
Choose General and copy the ID field. This is your Application ID.
-
Construct the Mosaic MCP Endpoint using envrionment URL and Application ID
<Env URL>/collaboration/mcp/mosaic/<Application ID>
Use this URL as the Mosaic MCP endpoint in your client configuration.
-
Construct the Agent MCP Endpoint using envrionment URL and Application ID
<Env URL>/collaboration/mcp/agent/<Application ID>
Use this URL as the Agent MCP endpoint in your client configuration.
Configure OAuth2 Endpoints for Non‑DCR Clients
If your client does not support Dynamic Client Registration (DCR), Application ID must be included in the authorization and token endpoints.
-
Construct the Authorization Endpoint:
<Env URL>/collaboration/authorize/<Application ID>
Enter this URL as the Authorization endpoint in your client’s OAuth2 configuration.
-
Construct the Token Endpoint:
<Env URL>/collaboration/token/<Application ID>
Enter this URL as the Token endpoint in your client’s OAuth2 configuration.
Verify Tenant‑Scoped Access
-
Connect to MCP using the configured Mosaic and Agent endpoints.
-
Sign in with a user assigned to the tenant.
-
Confirm that:
-
The login page matches the tenant’s login behavior (not a default or unrelated tenant).
-
The user only sees the projects associated with that tenant (and any shared projects configured for it).
-
-
If you see unexpected projects or the default (non‑tenant) login page, verify that the Application ID in your URLs is correct and that the user is assigned to the intended tenant.
Configure and Use Tenant Aliases
Tenant aliases let you use readable names (for example, Employee, Customer) instead of long Application IDs in your MCP and OAuth2 URLs.
-
Locate the MCP server configuration file, typically config.json, on the Strategy server.
-
Open config.json in a text editor.
-
Find or add the mcpConfig section.
-
Under mcpConfig, add an applicationAliases block with your aliases and corresponding Application IDs. For example:
-
Save the changes to config.json.
-
Restart collabService on the server to apply the updated alias configuration. Wait for the service to fully restart before testing the new endpoints.
-
Use Aliases in the MCP Endpoints:
<Env URL>/collaboration/mcp/mosaic/<Alias>
<Env URL>/collaboration/mcp/agent/<Alias>
-
Use Aliases in OAuth2 Endpoints
<Env URL>/collaboration/authorize/<Alias>
<Env URL>/collaboration/token/<Alias>
Verify the alias‑based access.
-
Connect from your client using the alias‑based endpoints.
-
Sign in with a user assigned to the tenant mapped to that alias.
-
Confirm that:
-
The login page matches the tenant’s login behavior (not a default or unrelated tenant).
-
The user only sees the projects associated with that tenant (and any shared projects configured for it).
-
-
If you see the default login page or incorrect projects, verify that:
-
The alias is correctly defined in config.json and mapped to the correct Application ID.
-
collabService was restarted after the configuration change.
-
The same alias is used consistently in all endpoints (Mosaic MCP, Agent MCP, Authorization, Token).
-
"mcpConfig": {
"applicationAliases": {
"Employee": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX1",
"Customer": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX2",
"tenantA": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX3",
"tenantB": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX4"
},
}
