Getting Started
Install the full Ontopix Claude Code setup — marketplaces, plugins, and MCP servers.
This guide walks you through installing the full Ontopix Claude Code setup: marketplaces, plugins, and MCP servers.
Prerequisites
- Claude Code CLI installed (official docs)
- Git and a terminal
- Node.js with
npx(for MCP servers that use npx) - Python with
uvx(for serena and aws-mcp)
Step 1: Add Marketplaces
Marketplaces are registries of plugins you can install. Add all four to get access to the full plugin set:
claude plugin marketplace add ontopix/claude-setup
claude plugin marketplace add athola/claude-night-market
claude plugin marketplace add obra/superpowers
claude plugin marketplace add anthropics/claude-code
Step 2: Install Plugins
Install all 10 plugins. Each one adds specific skills, commands, and agents to your Claude Code sessions.
# Ontopix patterns (required)
claude plugin install ontopix@ontopix-plugins
# Core skills: TDD, debugging, brainstorming, plans
claude plugin install superpowers@superpowers-dev
# Git/workspace: commits, PRs, docs, dependencies
claude plugin install sanctum@claude-night-market
# Code review: bugs, architecture, tests
claude plugin install pensive@claude-night-market
# Workflow methodologies, evidence gathering, reviews
claude plugin install imbue@claude-night-market
# Meta-skills: skill authoring, hooks, validation
claude plugin install abstract@claude-night-market
# Resource optimization, token conservation
claude plugin install conserve@claude-night-market
# Infrastructure building blocks (auth, errors, git platform)
claude plugin install leyline@claude-night-market
# Spec Driven Development: spec, plan, tasks, implement
claude plugin install spec-kit@claude-night-market
# Ralph Wiggum technique (Anthropic official)
claude plugin install ralph-wiggum@claude-code-plugins
What Each Plugin Does
| Plugin | Purpose |
|---|---|
| ontopix | Live access to Ontopix engineering patterns via MCP |
| superpowers | Core skills — TDD, debugging, brainstorming, planning |
| sanctum | Git workflows — commits, PRs, docs, dependencies |
| pensive | Code review — bugs, architecture, tests, shell scripts |
| imbue | Methodologies — evidence gathering, structured reviews |
| abstract | Meta-skills — skill authoring, plugin validation, hooks |
| conserve | Resource optimization — token conservation, context management |
| leyline | Infrastructure — auth patterns, error handling, git platform |
| spec-kit | Spec-driven development — specifications, plans, tasks |
| ralph-wiggum | Iterative loop technique from Anthropic |
Step 3: Configure MCP Servers
MCP (Model Context Protocol) servers extend Claude Code with external capabilities. Some are auto-bundled with plugins; most need manual configuration.
Auto-Bundled
The ontopix-docs MCP server is configured automatically when you install the ontopix plugin. However, for global availability you should also add it manually:
claude mcp add --transport http ontopix-docs https://docs.ontopix.dev/mcp -s user
Manual MCP Servers
Add each server for the capabilities you need:
# Semantic code analysis (LSP)
claude mcp add serena -- uvx --from git+https://github.com/oraios/serena serena start-mcp-server --context ide-assistant --enable-web-dashboard false --enable-gui-log-window false -s user
# Browser automation and debugging
claude mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest -s user
# Browser testing with Playwright
claude mcp add playwright -- npx -y @executeautomation/playwright-mcp-server -s user
# UI component builder (21st.dev)
claude mcp add magic -- npx -y @21st-dev/magic -s user
# Fast code apply
claude mcp add morphllm-fast-apply -- npx -y @morph-llm/morph-fast-apply -s user
# Chain-of-thought reasoning
claude mcp add sequential-thinking -- npx -y @modelcontextprotocol/server-sequential-thinking -s user
# Library documentation context
claude mcp add context7 -- npx -y @upstash/context7-mcp -s user
# AWS services (CLI, docs, SOPs)
claude mcp add aws-mcp -- uvx mcp-proxy-for-aws@latest https://aws-mcp.us-east-1.api.aws/mcp --metadata AWS_REGION=eu-west-1 -s user
MCP Server Summary
| Server | Purpose | Requires |
|---|---|---|
| ontopix-docs | Ontopix engineering patterns | Auto-bundled via plugin |
| serena | Semantic code analysis (LSP) | Python/uvx |
| chrome-devtools | Browser automation and debugging | Node.js/npx |
| playwright | Browser testing | Node.js/npx |
| magic | UI component builder (21st.dev) | Node.js/npx |
| morphllm-fast-apply | Fast code apply | Node.js/npx |
| sequential-thinking | Chain-of-thought reasoning | Node.js/npx |
| context7 | Library documentation context | Node.js/npx |
| aws-mcp | AWS services (CLI, docs, SOPs) | Python/uvx |
Step 4: Verify Your Setup
After installation, verify everything is working:
# Check all plugins are installed
claude plugin list
You should see all 10 plugins listed. Then start a Claude Code session and verify:
- Check MCP tools are available — Ask Claude to list its available MCP tools. You should see
ontopix-docstools likeget-page,search-pages, andlist-pages. - Test pattern access — Try asking: "Search ontopix docs for repository structure". Claude should query the MCP server and return results from docs.ontopix.dev.
- Test a skill — Try
/brainstormor/commit-msgto verify plugin skills are loaded.
Troubleshooting
Plugin not found
Make sure the marketplace was added first. Plugins are installed from marketplaces, so the marketplace must exist before claude plugin install will find the plugin.
claude plugin marketplace add ontopix/claude-setup
claude plugin install ontopix@ontopix-plugins
MCP server fails to start
Check that the required runtime is installed:
- For servers using
npx: Make sure Node.js is installed andnpxis on your PATH. - For servers using
uvx: Make sure Python anduvx(fromuv) are installed.
ontopix-docs not responding
Verify network access to docs.ontopix.dev:
curl -s https://docs.ontopix.dev/mcp | head -c 200
If this fails, check your network connection or firewall settings.
Skills not appearing
If slash commands like /brainstorm do not appear, try restarting your Claude Code session. Plugins are loaded at session start.