AgentToolHub
Skill

mcp-chaining

mcp-chaining — a Claude Code skill from parcadei/continuous-claude-v3

Features

  • ✓Persistent learning environment for Claude Code
  • ✓Maintains context across sessions for seamless development
  • ✓Orchestrates specialized agents for task coordination
  • ✓Intelligent code analysis to optimize token usage
  • ✓Extensive skill set with natural language triggers
  • ✓Visit the GitHub repo for more details

Installation Guide

bash
# Clone
git clone https://github.com/parcadei/Continuous-Claude-v3.git
cd Continuous-Claude-v3/opc

# Run setup wizard (12 steps)
uv run python -m scripts.setup.wizard

Note: The pyproject.toml is in opc/. Always run uv commands from the opc/ directory.

What the Wizard Does

| Step | What It Does |
|------|--------------|
| 1 | Backup existing .claude/ config (if present) |
| 2 | Check prerequisites (Docker, Python, uv) |
| 3-5 | Database + API key configuration |
| 6-7 | Start Docker stack, run migrations |
| 8 | Install Claude Code integration (32 agents, 109 skills, 30 hooks) |
| 9 | Math features (SymPy, Z3, Pint - optional) |
| 10 | TLDR code analysis tool |
| 11-12 | Diagnostics tools + Loogle (optional) |

#### To Uninstall:

text
cd Continuous-Claude-v3/opc
  uv run python -m scripts.setup.wizard --uninstall

What it does

  • Archives your current setup → Moves ~/.claude to ~/.claude-v3.archived.<timestamp>

  • Restores your backup → Finds the most recent ~/.claude.backup.* (created during install) and restores it

  • Preserves user data → Copies these back from the archive:

    • - history.jsonl (your command history)
    - mcp_config.json (MCP servers)
    - .env (API keys)
    - projects.json (project configs)
    - file-history/ directory
    - projects/ directory

  • Removes CC-v3 additions → Everything else (hooks, skills, agents, rules)

    • Safety Features

  • Your current setup is archived with timestamp - nothing gets deleted

  • The wizard asks for confirmation before proceeding

  • It restores from the backup that was made during installation

  • All your Claude Code settings stay intact

    • Remote Database Setup

    By default, CC-v3 runs PostgreSQL locally via Docker. For remote database setups:

    #### 1. Database Preparation

    bash
    # Connect to your remote PostgreSQL instance
psql -h hostname -U user -d continuous_claude

# Enable pgvector extension (requires superuser or rds_superuser)
CREATE EXTENSION IF NOT EXISTS vector;

# Apply the schema (from your local clone)
psql -h hostname -U user -d continuous_claude -f docker/init-schema.sql

    Managed PostgreSQL tips:

    - AWS RDS: Add vector to shared_preload_libraries in DB Parameter Group

    - Supabase: Enable via Database Extensions page

    - Azure Database: Use Extensions pane to enable pgvector

    #### 2. Connection Configuration

    Set CONTINUOUS_CLAUDE_DB_URL in ~/.claude/settings.json:

    json
    {
  "env": {
    "CONTINUOUS_CLAUDE_DB_URL": "postgresql://user:password@hostname:5432/continuous_claude"
  }
}

    Or export before running Claude:

    bash
    export CONTINUOUS_CLAUDE_DB_URL="postgresql://user:password@hostname:5432/continuous_claude"
claude

    See .env.example for all available environment variables.

    First Session

    bash
    # Start Claude Code
claude

# Try a workflow
> /workflow

    First Session Commands

    | Command | What it does |
    |---------|--------------|
    | /workflow | Goal-based routing (Research/Plan/Build/Fix) |
    | /fix bug <description> | Investigate and fix a bug |
    | /build greenfield <feature> | Build a new feature from scratch |
    | /explore | Understand the codebase |
    | /premortem | Risk analysis before implementation |

    ---

    Reviews