Nova Connect
Nova Connect puts AstroPulse in the editor or AI client you already use. Add one hosted MCP endpoint, sign in, and ask about your clusters and applications, debug a rollout, or scale and upgrade from where you write code. There is nothing to install or run: AstroPulse hosts the endpoint, and every call runs as you, in your organization.
When you need it
- You work in an editor or AI client that speaks MCP and want your platform in it, without switching to the console.
- You debug from code. Read app logs, cluster diagnostics, pod events and resource pressure in plain language next to the code that caused them.
- You operate from the same place. Create, upgrade, scale and validate clusters, and deploy, debug and resync applications.
Before you start
- An AstroPulse account in the organization you want to work in.
- An MCP client that supports remote servers over HTTP, for example Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor or VS Code agent mode.
- For a client without OAuth sign-in, an API key.
In the console
-
Open Nova AI in the console sidebar and select Open Nova Connect.
-
Open Integrations and pick your client. Each one shows its exact setup steps and config.
-
Add the endpoint to your client. This is the URL your client connects to:
https://platform.astropulse.io/mcpFor Claude Code:
Terminalclaude mcp add --transport http astro-platform https://platform.astropulse.io/mcpFor a client configured with JSON, such as Cursor (
.cursor/mcp.json):JSON{"mcpServers": {"astro-platform": {"url": "https://platform.astropulse.io/mcp"}}}VS Code agent mode uses
.vscode/mcp.jsonwith"servers"and"type": "http". Clients that add connectors in their settings, such as Claude Desktop, take the URL in their Add custom connector dialog. -
Sign in. An OAuth client opens a browser sign-in on first use, and the session is kept after that.
In claude.ai or ChatGPT
Browser AI clients take AstroPulse as a custom connector, with the same URL and sign-in:
- claude.ai: add a custom connector with
https://platform.astropulse.io/mcp. See Claude's guide. - ChatGPT: add a custom MCP server with the same URL. See ChatGPT's guide.
Each client decides which plans can add a custom connector and whether an admin adds it first; its guide says.
You should see
AstroPulse's tools listed in your client under the server name you chose (astro-platform above). Ask, for example, "which of my clusters is unhealthy?" and the answer comes from your organization.
Sign in with an API key
For a client without OAuth, or a headless setup, send an API key with every request, in the Authorization: Bearer <key> header or the X-Astropulse-API-Key header:
{
"mcpServers": {
"astro-platform": {
"url": "https://platform.astropulse.io/mcp",
"headers": {
"Authorization": "Bearer <your-api-key>"
}
}
}
}
A personal key acts as you. For CI or other automation, use a service account key, which belongs to the organization.
Choose the organization
With OAuth, Nova Connect works in your current organization in the console. To pin a connection to another organization you belong to, add ?org=<organization-id> to the URL:
https://platform.astropulse.io/mcp?org=<organization-id>
astroctl org list shows your organization IDs. Each connection works in one organization; to use another, add the server again with its ?org= value. An API key always works in the organization it was created in.
Prompt to Production
Say "deploy" in your code editor and Prompt to Production takes your code to a running service: it reads your repository, works out what it needs to run on AstroPulse, shows the plan and deploys after you confirm. It is available on request: select Request Access on the Prompt to Production card on the Nova Connect page. Prompt to Production
How your access is kept safe
- As you, nowhere else. Every call runs with your own permissions, in one organization. Nova Connect cannot reach an organization you are not a member of.
- The same checks as the console. Changes go through the same AstroPulse API as the console and
astroctl, so they are validated and refused the same way. - No key with OAuth. OAuth clients sign in through the browser and never need an API key in a config file. For a key, keep it in an environment variable or a secret store, never in source control, and revoke it from API Keys if it may have leaked.
Other ways in
- Nova Cloud: Nova in the browser, with skills, investigations and approvals.
- Nova in your terminal:
astroctl nova. - Nova Direct: Nova in your own environment, available on request.
If it's refused
?org=<organization-id> to the URL.?org= value is not an organization ID.astroctl org list.If an OAuth sign-in never completes, remove the server from your client, add it again with the exact URL, and allow the sign-in window to open.