GuideJune 1, 20256 min read

Bunnyshell Environments Skill for Claude Code

What Is the Bunnyshell Environments Skill?

The Bunnyshell Environments Skill is a Claude Skill — a set of instructions and resources that enables Claude Code to discover and manage Bunnyshell cloud environments through the bns CLI tool.

Once installed, Claude autonomously decides when to use this skill based on your environment management needs. You simply describe what you want in natural language, and Claude handles the rest.

Key Features

  • Full Environment Lifecycle — Create, deploy, stop, start, clone, and delete environments
  • Component Management — View logs, execute commands, and redeploy individual components
  • Remote Development — SSH access, port forwarding, and debug sessions
  • Pipeline Monitoring — Track deployments and view pipeline logs in real time
  • Configuration Authoring — Create and modify bunnyshell.yaml files with proper schema validation

Prerequisites

Before installing the skill, you need:

  1. Bunnyshell CLI — Install via Homebrew:
Bash
brew install bunnyshell/tap/bunnyshell-cli

  1. API Token — Get yours from the Bunnyshell Access Token page

  2. Configure the CLI:

Bash
bns configure profiles add --name default --token YOUR_TOKEN --default

Installation

Global Installation (all projects)

Bash
1git clone https://github.com/bunnyshell/bunnyshell-environments-skill.git /tmp/bns-skill
2mkdir -p ~/.claude/skills/bunnyshell-environments
3cp -r /tmp/bns-skill/* ~/.claude/skills/bunnyshell-environments/

Project-Specific Installation

Bash
1git clone https://github.com/bunnyshell/bunnyshell-environments-skill.git /tmp/bns-skill
2mkdir -p .claude/skills/bunnyshell-environments
3cp -r /tmp/bns-skill/* .claude/skills/bunnyshell-environments/

Usage Examples

Once installed, you can use natural language to manage your environments:

  • "List all my environments" — Shows your Bunnyshell environments with status
  • "Deploy environment ENV-12345" — Triggers a deployment
  • "Stop all staging environments to save costs" — Stops non-production environments
  • "Clone production for testing" — Creates a copy of your production environment
  • "Show me the logs for the api component" — Fetches component logs
  • "SSH into the frontend container" — Opens a remote shell session
  • "Forward port 3000 from the api component" — Sets up port forwarding for local debugging
  • "Create a bunnyshell.yaml for my Node.js + PostgreSQL app" — Generates configuration with proper schema

Bunnyshell MCP Server

In addition to the Claude Code skill, Bunnyshell provides a Model Context Protocol (MCP) server that enables AI-powered code editors like Cursor, Windsurf, and Claude Desktop to interact directly with the Bunnyshell API and documentation.

The MCP server gives your AI assistant access to:

  • Direct API access to Bunnyshell functionality
  • Documentation search — Ask questions about Bunnyshell and get instant answers
  • Real-time account data — Query your environments, components, and pipelines
  • Code generation — Generate Bunnyshell configurations and integrations

MCP Server Setup

The Bunnyshell MCP server is hosted at https://documentation.bunnyshell.com/mcp.

For Cursor — Add to ~/.cursor/mcp.json:

JSON
1{
2  "mcpServers": {
3    "bunnyshell": {
4      "url": "https://documentation.bunnyshell.com/mcp"
5    }
6  }
7}

For Claude Desktop — Add to your Claude Desktop MCP configuration with the same URL.

For full setup instructions, see the Bunnyshell MCP documentation.

Skill vs. MCP Server: When to Use Which

Claude Code SkillMCP Server
Best forManaging environments from the terminalAI-assisted coding in editors
Works withClaude Code CLICursor, Windsurf, Claude Desktop
CapabilitiesFull environment lifecycle, SSH, port forwardingAPI access, documentation search, code generation
SetupClone repo + install CLIAdd MCP endpoint URL

For the most powerful workflow, use both: the MCP server for documentation and code generation in your editor, and the Claude Code skill for environment management in your terminal.