Agents & API

Your cloud.
In your workflow.

Put infrastructure within reach of your coding agent, scripts, and CI. The REST API and hosted MCP server share the same platform and access controls.

MCP · remote HTTP configuration
{
  "mcpServers": {
    "helicarrier": {
      "url": "https://app.helicarrier.xyz/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Built for automation

From understanding
to taking action.

Read project context, follow logs, or deploy a service. Choose the scope that matches the work.

Hosted MCP

Connect a compatible MCP client using Streamable HTTP. Use OAuth where the client supports it, or an API key.

REST API

Make authenticated HTTP requests for projects, deployments, variables, networking, and data services.

Scoped keys

Limit access to one service or project, restrict environments, and choose read or write permissions by category.

Deploy triggers

Give a CI pipeline a revocable URL that can only trigger a deployment of one service.

Read-only inspection

Let an agent investigate logs, deployments, and metrics with a key that cannot change your infrastructure.

Shared project context

Expose projects as MCP resources so compatible clients can attach infrastructure context to a conversation.

Details that matter

Start with a key. Know its scope.

Create a key in your dashboard and keep it in a secret store. Call the identity endpoint first to discover the account, project, or service it can access. Then build from that scope.

  • Bearer authentication for the REST API and MCP
  • API keys are shown once and can be revoked
  • Scoped permissions are checked by both interfaces
REST API · your first request
curl "https://app.helicarrier.xyz/api/auth/me" \
  -H "Authorization: Bearer $HELI_API_KEY"

Go a little deeper

Built to be understood.

Start with a guide, then find the details as you need them.

Ready when you are

Make something.
We’ll keep it running.

Bring your code. Give your next idea a home on Helicarrier Cloud.