Butterbase Skills: A Claude Code Plugin for Butterbase's AI-Native Backend

What Butterbase Skills Is and What Problem It Solves

MCP servers for backend-as-a-service platforms expose many tools, and manually configuring each tool's connection and context in Claude Code is repetitive. Butterbase Skills automates that configuration. Installing the plugin adds an .mcp.json file that points Claude Code at the Butterbase MCP server endpoint, a CLAUDE.md file that loads always-on context about Butterbase environment variables, workflows, patterns, and documentation references, and six skill definitions for common Butterbase tasks.

The plugin targets developers who use Claude Code as their primary coding interface and want to build applications on Butterbase without interrupting their workflow to look up tool names, environment variable formats, or MCP connection details. According to the README, all 42-plus tools become available in Claude Code immediately after completing the OAuth consent step.

Installing the Plugin and Completing OAuth

Installation requires a single command:

claude plugin add @butterbase/skills

After that, the MCP server must be connected across every client you use. The Butterbase CLI handles this step:

npx @butterbase/cli mcp install

The README describes this command as walking through Claude Code, Cursor, VS Code, JetBrains, Codex, Gemini CLI, and other detected clients and printing per-client OAuth follow-up hints. Once the CLI finishes, OAuth is completed once per client. In Claude Code, restart the session and run `/mcp` or `claude mcp login butterbase` to trigger the OAuth flow. No API key copying is required: the README states that sign-in is OAuth only.

For local development against a Butterbase monorepo running on the local machine, the MCP server URL defaults to `http://localhost:4000/mcp`. To point the plugin at the local server, set:

export CONTROL_API_URL=http://localhost:4000

The Six Skill Workflows

The plugin ships six named skills, each triggering a guided workflow in Claude Code:

butterbase:build-app drives the creation of a complete application from scratch, for prompts such as 'Build me a blog with auth and comments.'

butterbase:schema-design assists with database schema design for use cases like 'Design a schema for an e-commerce app.'

butterbase:deploy-frontend deploys frontend code to a live URL, for prompts like 'Deploy my React app to production.'

butterbase:debug-rls guides debugging of Row-Level Security problems, such as 'Users are seeing each other's data.'

butterbase:function-dev helps develop serverless functions, for cases like 'Create a cron job to clean up expired sessions.'

butterbase:contributing covers contributing to Butterbase itself, for questions such as 'How do I add a new MCP tool?'

The skills load from the skills/ directory in the plugin package. The commands/ directory handles the slash commands. The CLAUDE.md file provides the always-on context that applies to every Claude Code session, not just skill-triggered ones.

What the Plugin Contains

The published package on npm (@butterbase/skills, version 0.3.1 at the time of writing) contains the following files:

- .claude-plugin/ holds the plugin's configuration files for Claude Code. - .mcp.json auto-configures the HTTPS endpoint for the Butterbase MCP server. - CLAUDE.md provides always-on context: environment variable names, workflow documentation, patterns, and documentation references. - skills/ holds the six guided skill definitions. - commands/ holds the slash command definitions.

The README also mentions three companion packages: @butterbase/sdk (TypeScript SDK for client-side and server-side use), @butterbase/cli (project scaffolding and backend management), and the butterbase_docs MCP tool, which can be called with any topic such as auth, storage, or functions to retrieve comprehensive reference documentation.

Limitations and Constraints

Butterbase Skills is not a general-purpose plugin. Every feature in it is specific to Butterbase: the MCP tools, the skill workflows, the CLAUDE.md context, and the OAuth flow all require an active Butterbase account. Developers not using Butterbase have no reason to install it.

The plugin is at version 0.3.1 with no GitHub releases, and the last push to the repository was on 2026-06-28. If Butterbase's API or MCP tool set has changed since that push, the skill definitions or the CLAUDE.md documentation in the plugin may not reflect the current state of the platform. Before building a project on top of skill-driven workflows, verify that the installed plugin version matches the Butterbase API version your project targets.

The plugin also has no offline mode. It depends on the Butterbase MCP server being reachable at the configured endpoint. Local development against `http://localhost:4000/mcp` requires the full Butterbase monorepo to be running locally. If the local server is not running, tool calls will fail silently or return connection errors rather than useful error messages.

Comparison with Direct MCP Configuration

Without the plugin, a developer using Claude Code with Butterbase would need to manually add the Butterbase MCP server to Claude Code's configuration, supply the connection URL and credentials by hand, and add documentation to the project's own CLAUDE.md file or paste it into the context on each session. The plugin replaces all of those steps with a single install command and one OAuth flow.

The nearest alternative approach is configuring Claude Code's MCP settings directly using the claude mcp add command and maintaining a custom CLAUDE.md with Butterbase documentation. This gives more control over which tools are exposed and what context is loaded, but requires the developer to keep that configuration up to date as Butterbase's toolset evolves. The plugin's main value is that it keeps that configuration synchronized with the plugin's release cadence.

Editorial conclusion

Butterbase Skills is worth installing for any developer who uses Claude Code to build on Butterbase. The plugin eliminates the manual MCP server configuration step and preloads the context Claude Code needs to call Butterbase tools correctly. The meaningful constraint is that it is tightly coupled to Butterbase itself: teams not using Butterbase have no use for it, and the skill workflows and MCP tools depend on a Butterbase account with an active OAuth session. Before relying on it in a project, confirm that the version of the plugin matches the Butterbase API version your project targets and check the CLAUDE.md file in the installed plugin for the exact environment variable names the skills reference.

Frequently asked questions

Official sources

1. butterbase-ai/butterbase-skills on GitHub
2. Issues
3. License: MIT
4. README