## What it does
- Exposes Customer Service data and tools *outward* — case, customer, knowledge, activity and email actions — to Copilot Studio agents and external MCP clients over HTTP. Agent 365 Tooling Gateway (ATG) is the Microsoft-hosted gateway that sits in front of the Dynamics 365 CX MCP Server - Service, handles OAuth, and does the on-behalf-of exchange through to Dataverse. This is the outbound counterpart to registering inbound MCP servers in Service Agent.
+ Exposes Customer Service data and tools *outward* — case, customer, knowledge, activity and email actions — to Copilot Studio agents and external MCP clients over HTTP. The server went **generally available in September 2026** as an independent offering, the **Dynamics 365 Customer Experience MCP Server for Service**. Agent 365 Tooling Gateway (ATG) is the Microsoft-hosted gateway that sits in front of the Dynamics 365 CX MCP Server - Service, handles OAuth, and does the on-behalf-of exchange through to Dataverse. This is the outbound counterpart to registering inbound MCP servers in Service Agent.
  
  ## Key facts
+ - **GA since September 2026**, sold and positioned as an independent offering rather than a Service Agent sub-feature. That changes the scoping conversation — a client can buy into the server without adopting Service Agent.
+ - Ships **more than 90 service-oriented tools** spanning case management, customer information access, knowledge management, email assistance, and activity/conversation management.
+ - Validated clients: Microsoft 365 Copilot (including Service Agent), Copilot Studio agents, Visual Studio Code, GitHub Copilot CLI, and other HTTP-based MCP clients.
+ - Access aligns with existing Dataverse roles and permissions — the server doesn't introduce a parallel permission model.
  - ATG is an OAuth 2.0-protected resource. Clients request a token for the *gateway* resource, not for the MCP server directly, and the gateway performs the on-behalf-of hop to Dataverse.
  - The scope is `<ATG-ring-app-id>/.default`. Because `/.default` doesn't support incremental or dynamic consent, a tenant admin has to grant admin consent up front — there's no per-user consent prompt.
  - Three rings, each with its own gateway host and Entra app ID: Test, PreProd and Prod. The environment ID in the server URL must belong to the same ring as the host, or it won't resolve.
    … 27 unchanged lines …
  
  ---
  
- *Public preview / early-2026 capability — worth revisiting once GA lands and the ring hosts and app IDs settle*
+ *Worth revisiting after the next release wave. Last refreshed 2026-09-22 when the CX MCP Server for Service reached GA as an independent offering with 90+ tools and a published validated-client list.*