01
Add a connector
Open your MCP client’s custom connector settings and enter the server URL above.
Alien MCP
Ask questions about your Alien deployments.
Connect Codex, Claude, Grok, or another 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.devEnter this URL as a custom MCP connector. Alien will open a secure sign-in flow; there is no API token to create or paste.
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
- 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. A request never approves or runs anything.
- Run operations
- Run an exact operation from your project’s catalog. An operation that changes something runs only with an approved access request 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.