Skip to main content
Applicable to: All users of MCP Servers on TrueFoundry. If you manage MCP server manifests via GitOps, additional action is required (see Migration Guide below).

​
What Is Changing

MCP Server Groups are removed from v0.112. MCP Servers will no longer be nested under groups — they are now standalone, top-level resources with their own permissions and simplified management. Before: 
MCP Server Group
  └── MCP Server
        └── Tools, Prompts, Resources
After: 
MCP Server (standalone)
  └── Tools, Prompts, Resources

​
Why This Change

  • Simplified management: The group-level management with per-server access caused confusion. Now everything is managed directly at the server level.
  • Better Virtual MCP servers: Previously limited to servers within the same group. Now you can use any MCP server you have access to when creating a Virtual MCP server.

​
What You Need to Do

  • Update your API integrations to use the new route and FQN formats.
  • If you manage MCP server manifests via Git, re-export and commit them (see below).

​
Deprecated Routes

The following formats are deprecated and will be removed in a future release.
FormatOldNew
Route/mcp/{group}/{server}/server/mcp/{server-name}/server
FQN{tenant}:mcp-server-group:{group}:mcp-server:{name}{tenant}:mcp-server:{name}

​
Git-based Manifest Management

If you store MCP server manifests in Git (GitOps workflow):
1

Re-export manifests

Re-export your manifests from the platform UI using the Apply as YAML button.
2

Verify updated format

The exported manifests will use the new format with updated server names.
3

Commit to Git

Commit the updated manifests to your Git repository.
This is a one-time update. After re-exporting, your manifests will be compatible with the new structure.

​
UI Changes

  • MCP Servers now appear as top-level resources in the sidebar.
  • No more groups — create MCP servers directly without creating a group first.
  • When creating Virtual MCP servers, reference source servers by name only (no group prefix needed). For example, use slack-tools instead of my-group/slack-tools.

​
Permissions & Access Control

  • Tenant Admins and users with “Create MCP Server” permission can create MCP servers.
  • Tenant Admins and managers of an MCP server can update its configuration.
  • Tenant Admins, managers, and users of an MCP server can access it.
MCP Server Manager and User roles are assigned per server via the Collaborators field when creating or editing an MCP server.
Virtual Account Permissions:
  • MCP Server Groups removed from the permission selector.
  • Select individual MCP Servers directly.
  • Use * wildcard to grant access to all MCP servers.

​
Backward Compatibility

All your existing MCP servers have been automatically migrated:
  • Permissions preserved — Group managers become MCP Server managers.
  • Access preserved — Users with group access retain access to servers.
  • IDs unchanged — Existing integrations continue to work.
  • Names preserved — Most servers keep their original name. Only servers with duplicate names across different groups get renamed.
Everything continues to work:
  • Old MCP server URLs (/mcp/{group}/{server}/...)
  • Old FQN format in API requests
  • Existing Virtual Account permissions
  • Prompts referencing MCP servers by old FQN
If you encounter any issues accessing MCP servers after this update, please reach out and we’ll be happy to assist.