Pure1

Connecting Pure1 to NeuBird lets investigations pull in your Pure Storage fleet’s hardware inventory, support contract status, performance and capacity metrics, and active alerts directly from Pure1 — without opening a dashboard or running a script.

With the Pure1 integration, you can:

• Look up array/fleet hardware inventory and support contract status as configuration context
• Pull active alerts (severity, affected array) into an investigation
• Retrieve historical performance and capacity metrics for arrays, volumes, and workloads

NeuBird connects to Pure1’s hosted, read-only-by-design Manage MCP server. Unlike most connections, Pure1’s REST API supports only one authentication method — an RSA key pair, not a simple API token — so setup involves generating a key pair and registering the public half with Pure1.

Register an API Client with Pure1

1. Generate an RSA key pair locally (2048-bit or larger). Keep the private key — you’ll paste it into NeuBird; never share it with Pure Storage or anyone else.
2. Sign in to Pure1 and open Settings > API Registration.
3. Register a new API client, pasting in the public key you generated.
4. Pure1 issues an Application ID in the form pure1:apikey:.... Copy it — you’ll need it alongside the private key.

Note

Pure1 has no separate “read-only” API client role today — NeuBird only ever calls the Manage MCP server’s read-only tools, but the credential itself carries whatever access your Pure1 user/role has. Treat the private key as a highly privileged secret.

Connection Fields

Field	Required	Description
Name	Yes	A descriptive name for this connection
Description	No	An overview of what this connection is used for
Application ID	Yes	The Pure1 API Application ID issued when you registered your public key (pure1:apikey:...)
Private Key	Yes	The PEM-encoded RSA private key paired with the public key you registered in Pure1

---

For general instructions on creating and managing connections, see the Connections Overview.