Nova Connect

Nova Connect is the hosted remote MCP deployment for Nova. Connect your editor to the managed AstroPulse endpoint — no Docker, no local server.

Recommended default

If you want Nova in your editor or CLI and do not want to manage Docker, uv, or a local MCP server process, use Nova Connect.

Nova Connect vs Nova Direct

	Nova Connect	Nova Direct
Runtime	Hosted by AstroPulse	Self-hosted by your team
User setup	Add one MCP endpoint	Run Docker / local services
Best for	Managed editor integrations	Data-sovereign, air-gapped, full deploy
Auth	OAuth or API key	Local credentials
Deploy	Request access	Included

Endpoint

https://platform.astropulse.io/mcp

What You Can Do

• Inspect cluster health and workload state
• Debug rollouts, pod crashes, and deployment failures
• Analyze resource pressure and Kubernetes events
• Run security scans and generate incident playbooks
• Create, upgrade, scale, and validate clusters
• Manage applications across AWS, GCP, and Azure

Deploy from your editor (Request Access)

Deploy capabilities are available on request. Once approved, you'll receive the deploy endpoint to add to your editor config.

To request access, contact us or use the Request Access button in the Nova Connect dashboard.

Authentication

Auth	Clients
OAuth (automatic sign-in)	Claude Code, Claude.ai, Claude Desktop, VS Code, Cursor
API Key (manual setup)	Cursor (also supports OAuth), Windsurf, Gemini CLI, Codex, JetBrains

OAuth

The client opens a browser sign-in flow automatically — no keys needed.

Multi-Organization Support

If you belong to multiple organizations, append ?org=<orgId> to the MCP URL to scope the OAuth session to a specific org:

https://platform.astropulse.io/mcp?org=your-org-uuid

Find your organization ID by running astroctl org list or in Settings → Organization.

For editor integrations (Claude Code, VS Code, Cursor, Claude Desktop), use the org-scoped URL when adding the MCP server. For example:

claude mcp add --transport http astro-platform https://platform.astropulse.io/mcp?org=your-org-uuid

Single org per connection

Each MCP connection is scoped to one organization. To work with a different org, remove the server and re-add it with the new ?org= value.

API Key

For clients without OAuth, or for CI/CD and headless environments:

1. Generate an API key at Settings → API Keys
2. Set it in your environment:

export ASTROPULSE_API_KEY="your-api-key-here"

3. Pass it in the MCP transport headers (see editor examples below).

API key security

• Never commit API keys to source control. Use environment variables or a secrets manager.
• Rotate keys periodically via the API Keys Console.
• Each key is scoped to a single user. Use separate keys for separate environments.
• Revoke compromised keys immediately from the console.

Quick Start

1. Pick your editor.
2. Add the MCP endpoint using the config below.
3. OAuth clients sign in automatically. API key clients need a key from Settings → API Keys.

Supported Integrations

Claude Code CLI

Claude Code Remote MCP

$ claude mcp add --transport http astro-platform https://platform.astropulse.io/mcp

On first use, a browser window opens automatically for OAuth sign-in. After authenticating, the session persists across restarts.

Claude.ai (Browser)

Use Nova Connect directly in your browser — no install required. Available on Free, Pro, Max, Team, and Enterprise plans.

1. Open claude.ai and click your profile icon → Settings.
2. Navigate to Connectors in the sidebar.
3. Click "Add custom connector".
4. Enter the URL: https://platform.astropulse.io/mcp
5. Complete OAuth when prompted. Nova tools appear in your conversations.

Team and Enterprise plans

Organization admins must first add the connector in Organization Settings → Connectors before team members can access it. Members then connect individually through Settings → Connectors.

Cursor

Add to ~/.cursor/mcp.json or .cursor/mcp.json. Cursor supports both OAuth and API key auth:

Cursor MCP Config (OAuth — recommended)

$ 
{
"mcpServers": {
  "astro-platform": {
    "url": "https://platform.astropulse.io/mcp"
  }
}
}

For headless or CI environments, use API key auth instead:

Cursor MCP Config (API Key)

$ 
{
"mcpServers": {
  "astro-platform": {
    "url": "https://platform.astropulse.io/mcp",
    "headers": {
      "Authorization": "Bearer YOUR_ASTROPULSE_API_KEY"
    }
  }
}
}

VS Code Agent Mode

Add to .vscode/mcp.json. VS Code supports OAuth — sign-in opens automatically:

.vscode/mcp.json

$ 
{
"servers": {
  "astro-platform": {
    "type": "http",
    "url": "https://platform.astropulse.io/mcp"
  }
}
}

Claude Desktop

1. Open Claude Desktop and go to Settings → Connectors.
2. Click "Add custom connector".
3. Enter the URL: https://platform.astropulse.io/mcp
4. A browser window opens for OAuth sign-in. Complete the flow to authorize Nova.
5. After sign-in, tools load automatically. The session refreshes in the background.

Gemini CLI

Gemini CLI requires API key auth:

Gemini CLI MCP Config

$ 
{
"mcpServers": {
  "astro-platform": {
    "url": "https://platform.astropulse.io/mcp",
    "headers": {
      "Authorization": "Bearer YOUR_ASTROPULSE_API_KEY"
    }
  }
}
}

Codex

Codex requires API key auth:

Codex MCP Config

$ 
{
"mcpServers": {
  "astro-platform": {
    "url": "https://platform.astropulse.io/mcp",
    "headers": {
      "Authorization": "Bearer YOUR_ASTROPULSE_API_KEY"
    }
  }
}
}

Windsurf

Windsurf requires API key auth:

Windsurf MCP Config

$ 
{
"mcpServers": {
  "astro-platform": {
    "url": "https://platform.astropulse.io/mcp",
    "headers": {
      "Authorization": "Bearer YOUR_ASTROPULSE_API_KEY"
    }
  }
}
}

JetBrains IDEs

JetBrains AI Assistant requires API key auth:

JetBrains MCP Config

$ 
{
"mcpServers": {
  "astro-platform": {
    "url": "https://platform.astropulse.io/mcp",
    "headers": {
      "Authorization": "Bearer YOUR_ASTROPULSE_API_KEY"
    }
  }
}
}

Other MCP Clients

Any MCP client that supports remote HTTP transport can use Nova Connect:

• Endpoint: https://platform.astropulse.io/mcp
• Server name: astro-platform
• Auth: OAuth (if supported by client) or Authorization: Bearer <ASTROPULSE_API_KEY> header

When To Use Nova Direct Instead

Use Nova Direct instead of Nova Connect if you need:

• full prompt-to-production deploy from your local workspace
• local Docker-based execution
• air-gapped or private-network-only access
• the built-in MCP Marketplace
• full control over where Nova, models, and credentials run

Nova Direct is the self-hosted path. Nova Connect is the hosted remote MCP path.

Troubleshooting

401 or authentication failures

• OAuth: Make sure the client completed the sign-in flow and is using the exact URL https://platform.astropulse.io/mcp.
• API key: Verify ASTROPULSE_API_KEY is set and the key has not expired. Generate a new key at Settings → API Keys.

OAuth redirect fails or times out

If the browser sign-in opens but never completes:

1. Remove the MCP server from your client and re-add it.
2. Ensure you are using the exact URL https://platform.astropulse.io/mcp (no trailing slash).
3. Check that your browser is not blocking pop-ups for the sign-in page.
4. If the issue persists, switch to API key authentication as a workaround.

Client does not support OAuth

Use API key authentication. Set ASTROPULSE_API_KEY and pass it as an Authorization: Bearer header in the transport config.

Client still asks you to run Docker locally

That is the Nova Direct / stdio setup path, not Nova Connect. For Nova Connect, use the hosted URL https://platform.astropulse.io/mcp.

Need the local / self-hosted path

Go to Nova Direct if your environment requires local execution or the built-in MCP Marketplace.