MooseStack Claude Code Plugin
The Problem
Getting Claude Code set up to build MooseStack apps is a multi-step process. You need to install the moose CLI, the 514 CLI, configure two MCP servers, set up a language server, and install a ClickHouse best practices skill. Each step has its own install command, its own config format, and its own place it needs to go. If you miss one, Claude is working without the full picture.
This plugin collapses all of that into one install.
Who Is This For
Developers using Claude Code to build data-intensive applications with MooseStack. Whether you're starting a new project or onboarding onto an existing one, this plugin makes sure Claude has everything it needs from the first session.
What the User Experiences
Before this plugin: You follow a setup guide. You install CLIs. You copy-paste MCP configs. You remember to install the skill. You hope you didn't miss a step. Claude works, but it might not have access to your dev server, or the docs, or the ClickHouse rules. You only find out when something goes wrong.
After installing this plugin:
- You install the plugin once.
- On your next Claude Code session, a startup hook silently checks for missing dependencies and installs them. No manual steps.
- You run
/moosestack:setup and Claude walks you through creating a hosting account, scaffolding a project, and starting local dev.
- From that point on, every Claude Code session in a MooseStack project has full access to everything listed below.
What Claude Gets
This plugin gives Claude six capabilities it doesn't have out of the box:
| Capability | What it does for Claude |
|---|
| MooseDev MCP | Live access to your running Moose project. Claude can inspect your data models, query ClickHouse, read logs, and check infrastructure health without you copy-pasting anything. |
| Context7 MCP | Always-available MooseStack documentation. Claude can look up APIs, configuration options, and patterns without you having to find and paste docs. |
| MooseStack LSP | Language intelligence for .ts, .tsx, and .py files in Moose projects. Claude gets type information, diagnostics, and project-aware completions. |
| moose CLI | The core CLI for scaffolding (moose init), running (moose dev), querying (moose query), and managing MooseStack projects. |
| 514 CLI | The CLI for deploying to 514 Labs hosting. |
| ClickHouse Best Practices Skill | 28 rules for reviewing data models, schemas, queries, and configurations. Claude references these when designing tables, choosing orderByFields, writing queries, or reviewing your ClickHouse setup. |
Together, these mean Claude can go from "help me build a data pipeline" to actually building one, with access to your running infrastructure, the official docs, and battle-tested ClickHouse patterns.
How It Works
- Session start hook runs
scripts/ensure-deps.sh, which checks for moose, 514, and the ClickHouse skill. Anything missing gets installed automatically.
- MCP servers are declared in
.mcp.json and available to Claude immediately. The MooseDev MCP only works when moose dev is running. Context7 is always available.
- LSP is declared in
.lsp.json and activates on .ts, .tsx, and .py files.
/moosestack:setup is a guided command that walks you through account creation, project scaffolding, and starting local dev.
Design Decisions
Skill pulled live from repo, not hardcoded. The ClickHouse best practices skill is installed dynamically from 514-labs/agent-skills via npx skills add so it stays in sync with upstream. Bundling skill files as a submodule was considered but rejected because it would require plugin updates every time the skill changes.
Local Testing
cd moosestack-claude-plugin
claude --plugin-dir .
Or run the automated test suite:
./scripts/test-plugin.sh
The test suite validates file structure, JSON schemas, URL reachability, dependency detection logic (in a sandboxed environment), and Claude Code integration (MCP servers, LSP, hooks, skills, and command content).
Submitting to the Official Marketplace
- Push this repo to
514-labs/moosestack-claude-plugin on GitHub
- Submit via the Claude plugin submission portal
- Or submit a PR to
anthropics/claude-plugins-official
Links
sjnims
agiletec-inc
rohitg00
anthropics
EricGrill
jeremylongshore