Bunnyshell MCP Server

Created By
aminalali8a year ago
Overview

what is Bunnyshell MCP Server?

Bunnyshell MCP Server is a Model Context Protocol (MCP) server implementation that allows AI assistants to interact with the Bunnyshell platform through its CLI.

how to use Bunnyshell MCP Server?

To use the Bunnyshell MCP Server, set up the server by cloning the repository and running the setup script. Then, connect your AI assistant (like Claude) to the MCP server using your Bunnyshell API token.

key features of Bunnyshell MCP Server?

  • Organization Management: List and navigate organizations
  • Project Management: Create, list, and delete projects
  • Environment Management: Manage environments (create, start, stop, delete)
  • Component Operations: Deploy, debug, and SSH into components
  • Variable & Secret Management: Manage environment variables and secrets
  • Remote Development: Start remote development sessions and set up port forwarding

use cases of Bunnyshell MCP Server?

  1. Managing Bunnyshell resources through natural language commands
  2. Automating project and environment management tasks
  3. Facilitating remote development workflows

FAQ from Bunnyshell MCP Server?

  • What are the prerequisites for using Bunnyshell MCP Server?

You need Node.js 18+, npm, Bunnyshell CLI, Claude Desktop, and Docker for setup.

  • How do I connect my AI assistant to the MCP server?

Start a conversation with Claude, add an attachment, and select 'Connect to MCP server'.

  • Is my API token secure?

Yes, API tokens are not stored in code or configuration files and can be provided via environment variables.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aminalali8
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago