Neo Integrations

Neo on its own knows about your infrastructure footprint: your code, your stacks, your state. Most of what your team actually does happens elsewhere, in the systems you use to plan, communicate, and operate. Integrations bridge that gap in two ways: by connecting Neo to those external systems, and by letting you reach Neo from where you already work.

MCP integrations and CLI integrations handle the first part. MCP brings context in from issue trackers, observability platforms, runbook wikis, and on-call tools. CLI integrations cover what MCP doesn’t reach, calling out to cloud-provider CLIs against credentials managed in Pulumi ESC. GitHub and Slack handle the second: mention Neo from a PR thread or a Slack channel to start a task without switching to the Pulumi Cloud console.

All integrations are configured at the organization level by an administrator. Once enabled, they’re available to every Neo task in the organization.