Claudeworks banner
Mduffy37 Mduffy37

Claudeworks

Development community

Description

Profile manager and plugin marketplace for Claude Code. Per-profile MCPs, skills, agents, and slash commands. Multi-agent teams. macOS, open source.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

ClaudeWorks

ClaudeWorks

Run separate Claude Code setups without hand-editing config.

macOS MIT Version 1.0.0

Home  ·  Docs  ·  Releases  ·  Issues

Each profile is an isolated Claude Code config directory: its own MCP servers, skills, agents, slash commands, and settings. Work in one terminal, personal in another, both running Claude Code with different tools loaded. 647 curated plugins and 4,795 skills come built in.

ClaudeWorks profile sidebar with two terminals running Claude Code side by side, each with a different skill set


Why this exists

I kept managing two Claude Code setups by hand, the work one with its MCP servers and skill set, the personal one with a different CLAUDE.md and different tools. Swapping meant editing `~/.claude.json` and `mcp.json` by hand, then undoing it next session. Claude Code has no native multi-profile support, so I built this instead.

Plugin caches are shared across profiles via symlinks, so you install a plugin once and updates propagate everywhere.

What it does

Each profile runs in its own `CLAUDE_CONFIG_DIR`, which is Claude Code's built-in way to redirect its config root. MCP servers, skills, agents, and slash commands from profile A can't appear in profile B's session. Real per-proces