@cubby-pro/mcp

MCP (Model Context Protocol) server for Cubby -- deploy apps, manage secrets, and interact with Cubby programmatically from AI tools like Claude Desktop, Claude Code, and Cursor.

This package runs as a local stdio MCP server. It needs access to the user's filesystem to read project directories for deploys, so it is launched on the user's machine by their MCP client (not hosted remotely).

Prerequisites

You must be logged in to Cubby first. Run this in your terminal:

npx cubbypro login

The MCP server reads credentials from the same store as the CLI, so you only need to log in once.

Setup

Claude Desktop

Add to your Claude Desktop configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "cubby": {
      "command": "npx",
      "args": ["-y", "@cubby-pro/mcp"]
    }
  }
}

Restart Claude Desktop after saving.

Claude Code

Claude Code reads project-local MCP config from .claude/settings.local.json (or .claude/settings.json for shared config). cubby init scaffolds this file for you. To configure manually:

{
  "mcpServers": {
    "cubby": {
      "command": "npx",
      "args": ["-y", "@cubby-pro/mcp"]
    }
  }
}

Cursor

Add to your Cursor MCP settings (.cursor/mcp.json in your project, or the global Cursor settings):

{
  "mcpServers": {
    "cubby": {
      "command": "npx",
      "args": ["-y", "@cubby-pro/mcp"]
    }
  }
}

Available Tools

All tools share the same authenticated session as the CLI.

| Tool | Description | |------|-------------| | list_apps | List your deployed apps | | get_app | Get details for a single app | | delete_app | Delete a deployed app | | check_app | Validate a local project (matches cubby check) | | deploy_app | Deploy an app from a local project directory | | get_logs | Read container logs for an app | | plan_app | Show subscription plan + app slot usage | | whoami | Show the currently authenticated Cubby user | | list_secrets | List secret names for an app | | set_secret | Set a secret on an app | | delete_secret | Delete a secret from an app | | db_create_branch / db_list_branches / db_delete_branch | Manage Neon branches (Pro plan) | | db_snapshot / db_list_snapshots / db_restore | Manage Neon snapshots (Pro plan) | | db_export | Export the app's database (Builder+) |

deploy_app — directory-only today

deploy_app accepts a single argument:

• directory (required) — an absolute path on the local filesystem (e.g. /Users/you/projects/my-app).

There is no files mode and no tarball_base64 mode. If the MCP client cannot expose a directory on disk (some hosted/remote MCP transports), deploy_app returns a NO_LOCAL_FS error. In that case, ask the user to run cubby deploy from their terminal.

Troubleshooting

"Not authenticated" Run npx cubbypro login in your terminal first. The MCP server shares credentials with the CLI.

"Transport error" or server won't start Ensure Node.js >= 18 is installed. Try running npx -y @cubby-pro/mcp directly in your terminal to check for errors (output goes to stderr).

Tools not appearing Restart your MCP client (Claude Desktop, Claude Code, Cursor) after adding the configuration.

deploy_app returns NO_LOCAL_FS Your MCP client is not running this server with local filesystem access. The Cubby MCP server only supports local stdio deploys today. Either run the server locally (Claude Desktop / Claude Code / Cursor on your own machine), or fall back to cubby deploy in your terminal.

Claude Desktop deploy fails or hangs

• Make sure you passed deploy_app an absolute project path. Relative paths and tilde (~) are not expanded the same way across clients.
• Confirm you ran cubby login in a terminal first — Claude Desktop launches the MCP server with a non-interactive shell and cannot complete a magic-link login on your behalf.
• Look at Claude Desktop's MCP log output for the underlying error before retrying.