Allow MCP-based integrations with Spacelift without requiring spacectl

Problem

Spacelift currently provides MCP functionality through the spacectl MCP server.

To use MCP with Spacelift today, users must:

1. Install spacectl

2. Authenticate using spacectl profile login

3. Configure their coding assistant to run:

spacectl mcp server

Requiring a CLI purely to support MCP integrations makes it harder to integrate Spacelift into internal platforms that standardize on API-driven MCP servers.

Proposed Solution

Provide a way to integrate Spacelift into MCP-based AI systems without requiring spacectl.

This could be achieved in one of two ways:

Option 1

Provide an official Spacelift MCP server that communicates directly with the Spacelift API / GraphQL.

Option 2

Provide documented integration patterns that allow customers to easily build their own MCP servers using the existing GraphQL API.

Ideal Capabilities

An MCP integration should allow AI tools to interact with Spacelift capabilities such as:

• discovering modules in the Spacelift module registry

• retrieving module metadata (inputs, outputs, examples)

• identifying the latest module version

• generating infrastructure code using approved modules

This enables AI assistants to generate infrastructure that aligns with an organization's approved module ecosystem.

Customer Value

Many organizations are adopting AI-assisted infrastructure development.

When infrastructure patterns are encapsulated into approved modules, AI tools can safely generate infrastructure code by discovering and using those modules.

Allowing MCP integrations without requiring a CLI dependency would make it easier for organizations to integrate Spacelift into internal developer platforms where multiple systems are connected through MCP servers and APIs.