{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":23887,"path":"intelligent-experiences/mcp-server-console-domain-separation.md","title":"Domain separation and MCP Server Console","bundle":null,"doc_type":null,"release":"australia","body":"\n# Domain separation and MCP Server Console\n\nDomain separation is supported for MCP Server Console. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.\n\n## Support level: Standard\n\n-   Includes all aspects of **Basic** level support.\n-   Application properties are domain-aware as needed.\n-   Business logic: The service provider \\(SP\\) creates or modifies processes per customer. The use cases reflect proper use of the application by multiple SP customers in a single instance.\n-   The instance owner must configure the minimum viable product \\(MVP\\) business logic and data parameters per tenant as expected for the specific application.\n\nSample use case: An admin must be able to make comments required when a record closes for one tenant, but not for another.\n\nFor more information on support levels, see [Application support for domain separation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/domain-separated-apps.md).\n\n## How domain separation works in MCP Server Console\n\nDomain separation limits the MCP tools and servers that a user can access based on their current domain. The rules follow a top-down hierarchy: a domain can view its own records, all records from descendant domains, and global records. The domain can't access records from ancestor or sibling domains.\n\n-   To enable domain separation in your MCP instance, install the domain separation plugin.\n-   The parent domain can view the servers, tools, and apps created within its child domains, and those created within its own domain.\n\n    **Note:** A domain can view it's own records, descendent domain's and global records. But it can't view ancestor's and sibling domain records.\n\n-   An MCP tool can be attached to a server within the same domain.\n-   When a tool or server is created via the UI, it is stamped with the creating user's current `sys_domain`. This stamp is the source of truth for all visibility and scoping decisions.\n\n**Parent Topic:**[MCP Server Console reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/intelligent-experiences/mcp-server-console-reference.md)\n\n**Related topics**  \n\n\n[Domain separation for service providers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/domain-sep-landing-page.md)\n\n"}}