Troubleshooting and FAQ

Troubleshooting

I don't see spacelift in /mcp

• Re-run the add command; confirm the URL and account name.
• Verify .mcp.json path and JSON validity.

OAuth window didn't open.

Check pop-up blockers. Try re-auth via /mcp → select server again.

A change fails because the project is locked

A write fails when another session holds the project lock. Wait for the lock to expire after about five minutes of inactivity, or release it explicitly through the UI or API.

Policy denies everything

• Start with allow-list for one resource type and expand.
• Use a separate test project/space while iterating.
• Enable policy sampling by adding sample = true to your policy to capture evaluation events and debug in the Policy Workbench (UI → Policies → select policy → Show simulation panel).

AWS creation fails

Verify integration is attached to the project, region matches prompts, and access is Read+Write.

FAQ

• Can I use a client other than Claude Code?

  Yes. Claude Desktop (custom connector), VS Code, and Cursor all work, and any MCP-capable client should work with the same URL. See Connecting to the Spacelift MCP server.

• Where are the Terraform files?

  Intent works at a higher abstraction. Your agent calls provider operations under Spacelift governance. No IaC files are required for day-1 usage.

• Can I export to Terraform/OpenTofu later?

  Yes. Use Intent to IaC to generate HCL code from your project and optionally create a Spacelift stack with imported state.

• How do I keep things safe?

  Put guardrails in place before you let an assistant make changes: write Intent policies that allow only the operations you intend, scope access with spaces and RBAC, and grant mcp:read-only sessions when you only need to inspect. For stricter isolation, run Intent on a private worker pool.