Hi team, we're evaluating the MCP Server connectio...
# gooddata-cloud
m
Hi team, we're evaluating the MCP Server connection in GD Cloud, and can't see how we can enable it for certain workspaces but not others. Does anyone know if this is possible.
k
Thinking completed The knowledge sources don't explicitly describe a workspace-level toggle for enabling or disabling the MCP Server itself on a per-workspace basis. However, there are a couple of relevant points: The MCP endpoint is workspace-scoped by design The MCP Server connection URL already targets a specific workspace:
Copy code
https://your-gooddata-host/api/v1/actions/workspaces/workspaceId/ai/mcp
This means each MCP client connection is inherently tied to a single workspace. You control which workspace an MCP client connects to simply by choosing the
workspaceId
in the endpoint URL. [MCP Server Connect] Access control is handled through authentication and permissions Since requests run as the authenticated user (via API token, signed JWT, or Interactive SSO), the user's GoodData permissions determine what they can access within that workspace. You can restrict who can connect to a given workspace by managing user permissions at the workspace level. [MCP Server Connect] Interactive SSO is a Beta feature with an Early Access toggle If you're specifically asking about the Interactive SSO authentication method for MCP, that is a Beta feature enabled at the organization level (not per workspace) under Early Access settings — not a per-workspace toggle. [Interactive SSO] In summary: The MCP Server doesn't appear to have a per-workspace on/off switch in the way Early Access experimental features do. The workspace scoping is achieved through the endpoint URL and user permissions rather than a feature flag. If you need to prevent MCP access to certain workspaces, managing user permissions on those workspaces would be the recommended approach. If this doesn't address your use case, please add more details to this thread so the Support team can investigate further: Community support (Startup & Professional) You're already in the right place — the GoodData Support team monitors this Slack and a team member will join the conversation when human review is needed. You can also visit the Community Forums. 24/7 Support (Enterprise plans) If this is a Severity 1 (L1) critical issue or your account includes 24/7 Support: • Submit a ticket: support.gooddata.com • Email: support@gooddata.com • Call: +1 (415) 200-0194 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.
m
Hi Mark, I just want to add to the above: there’s currently no setting to switch the MCP Server on or off for individual workspaces. Access is controlled by the identity the MCP client uses. If each user connects with their own credentials (Interactive SSO, a signed JWT or their own API token), the MCP Server can only reach the workspaces that user has permissions for. If the client uses a shared or admin API token, it can reach every workspace that token has access to, so for this use case we’d recommend per-user authentication (MCP Server – Connect, Permissions for AI and integrations). Hope this helps!
👍 1