AI Integration

Nullstone integrates with AI coding agents (Claude Code, Claude Desktop, Cursor, and any other MCP-compatible client) across three surfaces:

Surface	Purpose	Install
MCP Server	Lets agents take action — list stacks, deploy apps, spin up envs, tail logs, discover modules.	Install MCP
Skills Catalog	Teaches agents the shape and style of Nullstone YAML — when to trigger, which top-level key, the canonical idioms.	Install skills
Editor Integration	JSON-schema-driven autocomplete and validation in VS Code, JetBrains, Neovim, and more.	Published to schemastore.org

Which do I need?

Pick based on what you want the agent to do:

• "Run plans, deploys, and env operations against my org." → MCP Server. One install gives every CLI command as a tool.
• "Edit .nullstone/*.yml correctly when I ask." → Skills Catalog + MCP Server. The skill codifies the style; the MCP gives the agent modules_find/modules_describe to resolve unknown modules.
• "Get autocomplete when I edit the YAML." → Editor Integration — no AI involved.

Most teams install all three. The MCP and the skills catalog are complementary: the MCP acts, the skills codify conventions.

Quick start

# 1. Install the Nullstone CLI (prerequisite for the MCP).
curl -sSL https://docs.nullstone.io/install.sh | sh
nullstone configure --api-key=<your-api-key>
nullstone set-org <your-org>

# 2. Install the MCP server binary from GitHub releases.
#    See https://github.com/nullstone-io/mcp-server/releases

# 3. Install the skills catalog (one-time clone).
git clone https://github.com/nullstone-io/agent-skills.git ~/.claude/agent-skills
cp -R ~/.claude/agent-skills/skills/* ~/.claude/skills/

Then register the MCP in your client — see Install MCP for Claude Code, Claude Desktop, and Cursor configurations.

What's next

• MCP Server overview — architecture, tool naming, safety model.
• Skills catalog overview — what a skill is, how it differs from an MCP tool.
• nullstone-config-files — the first skill in the catalog.