Agent enablement
An agent surface is the gateway’s primary configuration unit. It combines inbound routing, caller authentication, identity derivation, policy enforcement, and outbound call controls for one managed agent backend. Start with a starter guide to create a working surface for your protocol, then layer on access controls and policies.
| Guide | What you will achieve |
|---|---|
| A2A surface starter | Build and deploy a Vertex A2A example agent, route A2A traffic through an Agent Gateway surface, and validate direct versus gateway-mediated calls. |
| MCP surface starter | Create an MCP surface from a starter template, configure required fields, validate outbound routing, and save reusable templates. |
| Expose a REST API as MCP tools | Configure an MCP proxy that reads an OpenAPI specification and generates one MCP tool per REST endpoint, making any REST API accessible to MCP-compatible agents. |
| Configure per-caller Credential Delegation | Add a Credential Delegation element to a surface, bound to each caller’s Caller Context identity, so the gateway acquires and injects per-user OAuth tokens without exposing App credentials to callers. Works for any surface type and any OAuth 2.0 Authorization Code API; uses GitHub Copilot MCP as the sample target. |
| Enable A2A communication with a Copilot Studio agent | Configure an A2A proxy so A2A callers can communicate with a Microsoft Copilot Studio agent through the gateway, with the gateway handling Direct Line protocol translation. |
| Control which A2A versions and messages a surface accepts | Choose the A2A versions an A2A surface accepts and how strictly the gateway checks each request before it reaches your managed agent. |
Was this page helpful?
Glad to hear it. Thanks for letting us know.
Sorry to hear that. Thanks for letting us know.