Alien MCP

Ask questions about your Alien deployments.

Connect a remote MCP client to inspect projects, follow rollouts, and search logs. Every connection is limited to the one workspace you choose, and it is read-only unless you approve more when you connect.

Remote MCP server

Streamable HTTP · OAuth

https://mcp.alien.dev

Enter this URL as a custom MCP connector. Alien will open a secure sign-in flow; there is no API token to create or paste.

Your client must support Streamable HTTP and OAuth. End-to-end verification with Codex and Claude is still pending.

01

Add a connector

Open your MCP client’s custom connector settings and enter the server URL above.

02

Choose a workspace

Sign in to Alien and select the one workspace this connection may access.

03

Start asking

Ask about deployment state, rollout progress, resources, events, or logs.

What it can read

Operational context, without dashboard hopping.

  • List projects and deployments
  • Inspect deployment health
  • Summarize Remote Operator installations
  • Follow release rollouts
  • Review deployment events
  • Inventory managed resources
  • Search deployment logs
  • Review incidents

Security model

OAuth, not copied tokens

The client receives a short-lived, audience-bound credential after you approve access.

Read-only by default

A client can do more only when it asks for an extra permission during sign-in and you approve it. To add one to an existing connection, reconnect. Alien rechecks your live workspace membership on every call.

Request access
Create a time-bounded request to run one exact operation, to debug with kubectl, aws, gcloud, or az, or both. A request never approves or runs anything. After the customer approves debug access, you run alien debug in the Alien CLI. The MCP connection never opens a debug session.
Run operations
Run an exact operation from your project’s catalog. An operation that changes something runs only with an approved access request that you created for that operation and its parameters. A read-only operation can also run when your project’s policy allows it automatically.
Change rollouts
Promote releases, pin a deployment to a release, change its release channel, retry, or redeploy. These use your own workspace permissions, the same as the CLI.

Learn more

New to Model Context Protocol?

Read the MCP introduction