An agent shouldn't have to learn 24 vendor APIs. EAG fronts them all with 48 plain-language tools, so the agent loads one small catalog instead of a sprawl of schemas — and spends its context on the work instead of the plumbing. Swap the system underneath a tool and not one agent changes. Every call is identity-scoped to the caller and audited — and where the backend supports OAuth 2.0 on-behalf-of, it runs as the signed-in user so the backend's own permissions apply underneath EAG's. The Identity column below tells you which is which, per connector.
Identity — Per-user means the caller's own token reaches the backend, so its permissions apply underneath EAG's. Shared credential, per-user scoping means EAG resolves the caller to a system principal and filters results to them, over one service connection. Click any connector to see the exact tools it binds, coloured by tier — read write privileged. Full definitions live in the tool catalog.
Backends that already speak MCP are fronted with configuration only — no driver code. EAG still applies your identity, policy, rate limits and audit on every call.
These ship as configuration templates, disabled by default. Vendors revise their MCP tool names, so you verify the downstream names against your server before enabling — the console names any tool it can't find at startup rather than failing silently.
Don't see your system? Anything with a REST, SOAP, OData or SQL interface is a manifest away — see the docs for adding one, or [email protected].