Troubleshooting the MCP Server Integration

  1. Confirm the prerequisites, content requirements, and user privileges before troubleshooting individual problems. Most connection and content failures are caused by one of them.

  2. If those requirements have been met, run the connection checks to rule out the most common causes.

    • If a check fails on something you cannot change yourself, open a support case or contact your Strategy account team.

  3. Find your problem in the tables to discover fixes:

Prerequisites

Most connection failures occur when these prerequisites are not met. The environment must:

  • Be publicly accessible

  • Have collaboration services enabled

For versions before Strategy One (June 2026), restart Tomcat so the trusted relationship and cookie settings (updated when you enabled the MCP Server) take effect. To confirm they are applied, Workstation should show "Trusted relationship between the Web Server and the Intelligence Server has been successfully established" and under Cookies, the SameSite Attribute should be None with HTTP Only and Secure enabled.

Content Requirements

  • Agents must be active, certified, and added to the user's Library. Users must have view permissions on the agents. Certify only the agents you want to expose.

  • Mosaic models must be published and certified to be accessible through MCP. Users must have view permissions on the models. The Mosaic endpoint also provides access to live and in-memory intelligent cubes and in-memory MTDI cubes. These cubes must be enabled for AI and certified to be accessible through MCP.

User Privileges

  • Users must have the Use MCP Server privilege.

  • To use Agents MCP, users must have the Run AI Bots privilege.

  • Users cannot be administrators or members of the Platform Support Administrator user group.

Connection Checks

Run these checks in your browser while logged in to Strategy Library.

Replace <environment URL> with the address you use to open Library, for example, https://env-domain.trial.cloud.strategy.com. If you are not sure what the URL should look like, you can view the exact MCP URLs for your environment in Workstation. (In the Navigation pane, click Environment Settings. In the Environment tab, click Library. The MCP Endpoints are listed in the Model Context Protocol for Agent section.)

  1. Check the collaboration service. In your browser, open <environment URL>/collaboration/status. A healthy response looks like:

    {"state":"running","reason":"","isSchemaUpToDate":true,"isAiConfigured":true}

    If this response does not display, the collaboration service is not running.

  2. Check the MCP endpoint. In your browser, open <environment URL>/collaboration/mcp/agent or <environment URL>/collaboration/mcp/mosaic.

    • The expected response is Unauthorized: No token provided, which confirms the endpoint is exposed to the public network.

    • A 503 Service Unavailable or No Healthy Upstream response means the MCP endpoint is not enabled.

  3. Rule out cached cookies. If the connection fails with no clear error, retry it in an incognito window. If the connection works in incognito mode, cached Library cookies are the cause. Clear all Library cookies in your normal browser, then reconnect.

Connection and Networking Issues

Problem Solution
The agent or connector shows as "not connected" and retrying redirects to Library with a personal user instead of prompting an OAuth login, or the env-id (the environment identifier in your environment URL, a UUID like d4b8c3a2-...) does not resolve. Confirm the active env-id for the tenant and whether MCP is enabled for that environment. Do not use legacy domains such as microstrategy.com.
500 error when testing the connection. Do not assume the cause is permissions. Check in parallel whether the connecting IP is public (see the private IP problem in the next row) before changing roles or permissions.
The 500 error appears related to the connector reaching a private IP.

  • Confirm with IT that the exposed endpoint is public, not an internal load balancer or internal DNS.

  • Check whether the domain resolves differently from inside and outside the network.

Need to connect Mosaic cubes or models, not an agent.

Authentication and OAuth Issues

Problem Solution
Authorization or Token URLs contain oauth2/authorize or oauth2/token and the connection fails.

Replace oauth2 with collaboration in both URLs: /collaboration/authorize and /collaboration/token. The path should not say MicroStrategyLibrary.

  • To locate the correct URL for your environment, in Workstation, click Environment Settings in the Navigation pane. On the Environment tab, click Library. The MCP Endpoints are listed in the Model Context Protocol for Agent section.
Connection keeps dropping or repeatedly asks to re-authenticate. In Workstation, type offline_access into the scope field and press the Enter key so it becomes a tag. Text that is not converted to a tag is not saved.
Connection is authenticated (green) but the client replies "no agents available."

The agent is not certified, as noted in Content Requirements.

  • You can certify the agent in Library. Right-click the agent and select Certify, or edit the agent, click Save As, and select Certified.).

  • If the Certify option is not available, you do not have the correct certification permissions; ask a user with certification permissions on the project.
The Administrator user cannot use MCP.

Use named users (with an email address) with the Power User role enabled, not the generic Administrator account. See User Privileges.

Content and Permissions Issues

Problem Solution
Agents or Mosaic models are listed in MCP but query questions against them fail. Log in to Library directly and try the same object there: ask the agent a question or create a dashboard on the model. If it fails in Library as well, you are missing Use permissions on the object (ACLs).

Client-Specific Issues

Problem Solution
Authentication error in Copilot Studio or Power Automate when using the tenant code as Client ID.

The correct Client ID is the UUID shown in Workstation. Click Environment Settings in the Navigation pane. On the Environment tab, click Library. The Client ID is listed in the Model Context Protocol for Agent section. Do not use the tenant code as the Client ID.