MCP & Integration Guides

MCP servers

AEP's Agent Orchestration Engine talks to tools through the Model Context Protocol (MCP) — any MCP-compatible server can be registered and its tools become callable by an agent. Point AEP at your server's endpoint, and its tools appear alongside the built-in skills.

Source control

GitHub — connect a repository to let skills open PRs, comment on issues, and read CI status. Authentication uses a scoped personal access token or a GitHub App install, configured from your AEP account's Integrations panel.

Cloud providers

AWS, Azure, GCP — infrastructure-facing skills (provisioning checks, cost analysis, config drift detection) authenticate against your cloud provider using a read-scoped service credential you supply. No credentials are ever stored outside your own provider's secret manager when one is configured.

ITSM, ERP, and SIEM

• ITSM (ServiceNow-style) — relevant once AOP ships; incident and change-management skills will read/write tickets through your ITSM's REST API.
• ERP — relevant once AFP ships; finance-automation skills will connect to your ERP's export/reporting endpoints.
• SIEM — relevant once ASP ships; security skills will ingest findings from your SIEM and route remediation actions back through it.

These three are previewed here because they're part of the platform's shared integration story (see Platform — Integrations), even though the products that use them are still on the Roadmap.

Next steps

• Wiring your own agents/scripts in via API key instead of a UI-managed integration? See the AEP CLI quickstart.
• Full API surface for building a custom integration: API Reference.