Neo's Integration Catalog: Give Your Agent Access to the Tools It Needs

Neo already helps your team manage Pulumi infrastructure, but no infrastructure team works inside Pulumi alone. Pages come from PagerDuty, telemetry from Datadog or Honeycomb, follow-ups from Linear or Jira. Most of the job is shuttling context between those tools.

Today we’re launching the Integration Catalog for Pulumi Neo: one place to connect Neo to the tools your team already uses, so your agent has the context it needs to help.

Six integrations in the launch catalog

Neo ships with six integrations at launch, each exposed to the agent through the Model Context Protocol (MCP):

• Atlassian — Jira issues, Confluence pages, project context
• Datadog — metrics, logs, monitors
• Honeycomb — traces and observability queries
• Linear — issue tracking and project workflows
• PagerDuty — incidents, on-call schedules, escalations
• Supabase — database management and edge functions

Each integration is a remote MCP server. Neo calls the integration through a structured tool protocol and only sees the tools the vendor chooses to expose.

Neo in action: one task, many systems

A latency spike showed up in Datadog yesterday afternoon, and you want to know whether your deploy caused it.

You: Neo, our payments stack saw elevated p95 starting around 3pm yesterday. Did our deploy cause it? Check Datadog and Honeycomb.

Neo lines up the Pulumi update history for the payments stack against the latency and error-rate metrics in Datadog around the same window, then surfaces the top slow traces in Honeycomb to confirm the suspect change.

You: Open a Linear ticket on the platform team with the findings and link the offending update.

Neo opens the Linear issue with the summary, the Pulumi update URL, and a pointer to the Datadog dashboard, all without you leaving the chat or copy-pasting context between tabs.

How the Integration Catalog works

Admins configure credentials once. In your org’s Neo settings, open the Integration Catalog, pick an integration, and paste in an API token or service-account key.

Your team gets the capability immediately. No per-user setup, no extra OAuth flow for each developer, no asking platform to share a token in 1Password.

Credentials stay encrypted at rest. When a task runs, the service decrypts the configured credentials just long enough to hand them to the agent runtime as MCP server auth.

What’s coming next: CLI, OAuth, and access controls

This is the first cut. Here’s what we’re working on:

• CLI integrations — give Neo access to command-line tools like kubectl, aws, gcloud, and az.
• OAuth integrations — for providers whose hosted MCP servers only speak OAuth (Notion, Sentry, Vercel), and for orgs that want per-user credentials.
• Per-integration access controls — team-scoped policies so admins can say “only the platform team can let Neo touch PagerDuty.”

Try it out

The Integration Catalog is available now for Neo-enabled organizations. Open your org’s Neo settings, head to the Integrations tab, and connect the first tool you reach for when something breaks. The Neo integrations docs walk through the setup for each one.

As always, we’d love to hear what’s missing. File a feature request in pulumi-cloud-requests with the integration you want next. We’re prioritizing based on what teams actually use.

Happy building.