mirror of
https://github.com/SuperClaude-Org/SuperClaude_Framework.git
synced 2025-12-29 16:16:08 +00:00
* fix(orchestration): add WebFetch auto-trigger for infrastructure configuration Problem: Infrastructure configuration changes (e.g., Traefik port settings) were being made based on assumptions without consulting official documentation, violating the 'Evidence > assumptions' principle in PRINCIPLES.md. Solution: - Added Infrastructure Configuration Validation section to MODE_Orchestration.md - Auto-triggers WebFetch for infrastructure tools (Traefik, nginx, Docker, etc.) - Enforces MODE_DeepResearch activation for investigation - BLOCKS assumption-based configuration changes Testing: Verified WebFetch successfully retrieves Traefik official docs (port 80 default) This prevents production outages from infrastructure misconfiguration by ensuring all technical recommendations are backed by official documentation. * feat: Add PM Agent (Project Manager Agent) for seamless orchestration Introduces PM Agent as the default orchestration layer that coordinates all sub-agents and manages workflows automatically. Key Features: - Default orchestration: All user interactions handled by PM Agent - Auto-delegation: Intelligent sub-agent selection based on task analysis - Docker Gateway integration: Zero-token baseline with dynamic MCP loading - Self-improvement loop: Automatic documentation of patterns and mistakes - Optional override: Users can specify sub-agents explicitly if desired Architecture: - Agent spec: SuperClaude/Agents/pm-agent.md - Command: SuperClaude/Commands/pm.md - Updated docs: README.md (15→16 agents), agents.md (new Orchestration category) User Experience: - Default: PM Agent handles everything (seamless, no manual routing) - Optional: Explicit --agent flag for direct sub-agent access - Both modes available simultaneously (no user downside) Implementation Status: - ✅ Specification complete - ✅ Documentation complete - ⏳ Prototype implementation needed - ⏳ Docker Gateway integration needed - ⏳ Testing and validation needed Refs: kazukinakai/docker-mcp-gateway (IRIS MCP Gateway integration) * feat: Add Agent Orchestration rules for PM Agent default activation Implements PM Agent as the default orchestration layer in RULES.md. Key Changes: - New 'Agent Orchestration' section (CRITICAL priority) - PM Agent receives ALL user requests by default - Manual override with @agent-[name] bypasses PM Agent - Agent Selection Priority clearly defined: 1. Manual override → Direct routing 2. Default → PM Agent → Auto-delegation 3. Delegation based on keywords, file types, complexity, context User Experience: - Default: PM Agent handles everything (seamless) - Override: @agent-[name] for direct specialist access - Transparent: PM Agent reports delegation decisions This establishes PM Agent as the orchestration layer while respecting existing auto-activation patterns and manual overrides. Next Steps: - Local testing in agiletec project - Iteration based on actual behavior - Documentation updates as needed * refactor(pm-agent): redesign as self-improvement meta-layer Problem Resolution: PM Agent's initial design competed with existing auto-activation for task routing, creating confusion about orchestration responsibilities and adding unnecessary complexity. Design Change: Redefined PM Agent as a meta-layer agent that operates AFTER specialist agents complete tasks, focusing on: - Post-implementation documentation and pattern recording - Immediate mistake analysis with prevention checklists - Monthly documentation maintenance and noise reduction - Pattern extraction and knowledge synthesis Two-Layer Orchestration System: 1. Task Execution Layer: Existing auto-activation handles task routing (unchanged) 2. Self-Improvement Layer: PM Agent meta-layer handles documentation (new) Files Modified: - SuperClaude/Agents/pm-agent.md: Complete rewrite with meta-layer design - Category: orchestration → meta - Triggers: All user interactions → Post-implementation, mistakes, monthly - Behavioral Mindset: Continuous learning system - Self-Improvement Workflow: BEFORE/DURING/AFTER/MISTAKE RECOVERY/MAINTENANCE - SuperClaude/Core/RULES.md: Agent Orchestration section updated - Split into Task Execution Layer + Self-Improvement Layer - Added orchestration flow diagram - Clarified PM Agent activates AFTER task completion - README.md: Updated PM Agent description - "orchestrates all interactions" → "ensures continuous learning" - Docs/User-Guide/agents.md: PM Agent section rewritten - Section: Orchestration Agent → Meta-Layer Agent - Expertise: Project orchestration → Self-improvement workflow executor - Examples: Task coordination → Post-implementation documentation - PR_DOCUMENTATION.md: Comprehensive PR documentation added - Summary, motivation, changes, testing, breaking changes - Two-layer orchestration system diagram - Verification checklist Integration Validated: Tested with agiletec project's self-improvement-workflow.md: ✅ PM Agent aligns with existing BEFORE/DURING/AFTER/MISTAKE RECOVERY phases ✅ Complements (not competes with) existing workflow ✅ agiletec workflow defines WHAT, PM Agent defines WHO executes it Breaking Changes: None - Existing auto-activation continues unchanged - Specialist agents unaffected - User workflows remain the same - New capability: Automatic documentation and knowledge maintenance Value Proposition: Transforms SuperClaude into a continuously learning system that accumulates knowledge, prevents recurring mistakes, and maintains fresh documentation without manual intervention. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * docs: add Claude Code conversation history management research Research covering .jsonl file structure, performance impact, and retention policies. Content: - Claude Code .jsonl file format and message types - Performance issues from GitHub (memory leaks, conversation compaction) - Retention policies (consumer vs enterprise) - Rotation recommendations based on actual data - File history snapshot tracking mechanics Source: Moved from agiletec project (research applicable to all Claude Code projects) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * feat: add Development documentation structure Phase 1: Documentation Structure complete - Add Docs/Development/ directory for development documentation - Add ARCHITECTURE.md - System architecture with PM Agent meta-layer - Add ROADMAP.md - 5-phase development plan with checkboxes - Add TASKS.md - Daily task tracking with progress indicators - Add PROJECT_STATUS.md - Current status dashboard and metrics - Add pm-agent-integration.md - Implementation guide for PM Agent mode This establishes comprehensive documentation foundation for: - System architecture understanding - Development planning and tracking - Implementation guidance - Progress visibility Related: #pm-agent-mode #documentation #phase-1 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * feat: PM Agent session lifecycle and PDCA implementation Phase 2: PM Agent Mode Integration (Design Phase) Commands/pm.md updates: - Add "Always-Active Foundation Layer" concept - Add Session Lifecycle (Session Start/During Work/Session End) - Add PDCA Cycle (Plan/Do/Check/Act) automation - Add Serena MCP Memory Integration (list/read/write_memory) - Document auto-activation triggers Agents/pm-agent.md updates: - Add Session Start Protocol (MANDATORY auto-activation) - Add During Work PDCA Cycle with example workflows - Add Session End Protocol with state preservation - Add PDCA Self-Evaluation Pattern - Add Documentation Strategy (temp → patterns/mistakes) - Add Memory Operations Reference Key Features: - Session start auto-activation for context restoration - 30-minute checkpoint saves during work - Self-evaluation with think_about_* operations - Systematic documentation lifecycle - Knowledge evolution to CLAUDE.md Implementation Status: - ✅ Design complete (Commands/pm.md, Agents/pm-agent.md) - ⏳ Implementation pending (Core components) - ⏳ Serena MCP integration pending Salvaged from mistaken development in ~/.claude directory Related: #pm-agent-mode #session-lifecycle #pdca-cycle #phase-2 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * fix: disable Serena MCP auto-browser launch Disable web dashboard and GUI log window auto-launch in Serena MCP server to prevent intrusive browser popups on startup. Users can still manually access the dashboard at http://localhost:24282/dashboard/ if needed. Changes: - Add CLI flags to Serena run command: - --enable-web-dashboard false - --enable-gui-log-window false - Ensures Git-tracked configuration (no reliance on ~/.serena/serena_config.yml) - Aligns with AIRIS MCP Gateway integration approach 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * refactor: rename directories to lowercase for PEP8 compliance - Rename superclaude/Agents -> superclaude/agents - Rename superclaude/Commands -> superclaude/commands - Rename superclaude/Core -> superclaude/core - Rename superclaude/Examples -> superclaude/examples - Rename superclaude/MCP -> superclaude/mcp - Rename superclaude/Modes -> superclaude/modes This change follows Python PEP8 naming conventions for package directories. * style: fix PEP8 violations and update package name to lowercase Changes: - Format all Python files with black (43 files reformatted) - Update package name from 'SuperClaude' to 'superclaude' in pyproject.toml - Fix import statements to use lowercase package name - Add missing imports (timedelta, __version__) - Remove old SuperClaude.egg-info directory PEP8 violations reduced from 2672 to 701 (mostly E501 line length due to black's 88 char vs flake8's 79 char limit). * docs: add PM Agent development documentation Add comprehensive PM Agent development documentation: - PM Agent ideal workflow (7-phase autonomous cycle) - Project structure understanding (Git vs installed environment) - Installation flow understanding (CommandsComponent behavior) - Task management system (current-tasks.md) Purpose: Eliminate repeated explanations and enable autonomous PDCA cycles 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * feat(pm-agent): add self-correcting execution and warning investigation culture ## Changes ### superclaude/commands/pm.md - Add "Self-Correcting Execution" section with root cause analysis protocol - Add "Warning/Error Investigation Culture" section enforcing zero-tolerance for dismissal - Define error detection protocol: STOP → Investigate → Hypothesis → Different Solution → Execute - Document anti-patterns (retry without understanding) and correct patterns (research-first) ### docs/Development/hypothesis-pm-autonomous-enhancement-2025-10-14.md - Add PDCA workflow hypothesis document for PM Agent autonomous enhancement ## Rationale PM Agent must never retry failed operations without understanding root causes. All warnings and errors require investigation via context7/WebFetch/documentation to ensure production-quality code and prevent technical debt accumulation. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * feat(installer): add airis-mcp-gateway MCP server option ## Changes - Add airis-mcp-gateway to MCP server options in installer - Configuration: GitHub-based installation via uvx - Repository: https://github.com/oraios/airis-mcp-gateway - Purpose: Dynamic MCP Gateway for zero-token baseline and on-demand tool loading ## Implementation Added to setup/components/mcp.py self.mcp_servers dictionary with: - install_method: github - install_command: uvx test installation - run_command: uvx runtime execution - required: False (optional server) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: kazuki <kazuki@kazukinoMacBook-Air.local> Co-authored-by: Claude <noreply@anthropic.com>
319 lines
12 KiB
Markdown
319 lines
12 KiB
Markdown
# SuperClaude MCP サーバーガイド 🔌
|
||
|
||
[](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/mcp-servers.md#superclaude-mcp-servers-guide-)
|
||
|
||
## 概要
|
||
|
||
[](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/mcp-servers.md#overview)
|
||
|
||
MCP(モデルコンテキストプロトコル)サーバーは、専用ツールを通じてClaude Codeの機能を拡張します。SuperClaudeは6つのMCPサーバーを統合し、タスクに応じてサーバーをいつ起動するかをClaudeに指示します。
|
||
|
||
### 🔍 現実チェック
|
||
|
||
[](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/mcp-servers.md#-reality-check)
|
||
|
||
- **MCPサーバーとは**: 追加ツールを提供する外部Node.jsプロセス
|
||
- **含まれていないもの**:SuperClaude 機能が組み込まれている
|
||
- **アクティベーションの仕組み**: クロードは状況に応じて適切なサーバーを使用するための指示を読み上げます
|
||
- **提供されるもの**:Claude Codeのネイティブ機能を拡張する実際のツール
|
||
|
||
**コアサーバー:**
|
||
|
||
- **context7** : 公式ライブラリドキュメントとパターン
|
||
- **段階的思考**:多段階の推論と分析
|
||
- **マジック**:モダンなUIコンポーネント生成
|
||
- **プレイライト**:ブラウザ自動化とE2Eテスト
|
||
- **morphllm-fast-apply** : パターンベースのコード変換
|
||
- **serena** : セマンティックコード理解とプロジェクトメモリ
|
||
|
||
## クイックスタート
|
||
|
||
[](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/mcp-servers.md#quick-start)
|
||
|
||
**セットアップの確認**:MCPサーバーは自動的に起動します。インストールとトラブルシューティングについては、[「インストールガイド」](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/Getting-Started/installation.md)と[「トラブルシューティング」](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/Reference/troubleshooting.md)を参照してください。
|
||
|
||
**自動アクティベーションロジック:**
|
||
|
||
|リクエストに含まれるもの|アクティブ化されたサーバー|
|
||
|---|---|
|
||
|ライブラリのインポート、API名|**コンテキスト7**|
|
||
|`--think`、デバッグ|**連続思考**|
|
||
|`component`、`UI`、 フロントエンド|**魔法**|
|
||
|`test`、、`e2e``browser`|**劇作家**|
|
||
|複数ファイルの編集、リファクタリング|**morphllm-高速適用**|
|
||
|大規模プロジェクト、セッション|**セレナ**|
|
||
|
||
## サーバーの詳細
|
||
|
||
[](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/mcp-servers.md#server-details)
|
||
|
||
### コンテキスト7 📚
|
||
|
||
[](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/mcp-servers.md#context7-)
|
||
|
||
**目的**: 公式ライブラリドキュメントへのアクセス **トリガー**: インポートステートメント、フレームワークキーワード、ドキュメントリクエスト **要件**: Node.js 16+、APIキーなし
|
||
|
||
```shell
|
||
# Automatic activation
|
||
/sc:implement "React authentication system"
|
||
# → Provides official React patterns
|
||
|
||
# Manual activation
|
||
/sc:analyze auth-system/ --c7
|
||
```
|
||
|
||
### 連続思考 🧠
|
||
|
||
[](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/mcp-servers.md#sequential-thinking-)
|
||
|
||
**目的**: 構造化された多段階の推論と体系的な分析 **トリガー**: 複雑なデバッグ、`--think`フラグ、アーキテクチャ分析 **要件**: Node.js 16+、APIキーなし
|
||
|
||
```shell
|
||
# Automatic activation
|
||
/sc:troubleshoot "API performance issues"
|
||
# → Enables systematic root cause analysis
|
||
|
||
# Manual activation
|
||
/sc:analyze --think-hard architecture/
|
||
```
|
||
|
||
### 魔法✨
|
||
|
||
[](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/mcp-servers.md#magic-)
|
||
|
||
**目的**: 21st.dev パターンからのモダン UI コンポーネント生成 **トリガー**: UI リクエスト、`/ui`コマンド、コンポーネント開発 **要件**: Node.js 16+、TWENTYFIRST_API_KEY()
|
||
|
||
```shell
|
||
# Automatic activation
|
||
/sc:implement "responsive dashboard component"
|
||
# → Generates accessible UI with modern patterns
|
||
|
||
# API key setup
|
||
export TWENTYFIRST_API_KEY="your_key_here"
|
||
```
|
||
|
||
### 劇作家🎭
|
||
|
||
[](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/mcp-servers.md#playwright-)
|
||
|
||
**目的**: 実際のブラウザ自動化とE2Eテスト **トリガー**: ブラウザテスト、E2Eシナリオ、視覚的検証 **要件**: Node.js 16以上、APIキーなし
|
||
|
||
```shell
|
||
# Automatic activation
|
||
/sc:test --type e2e "user login flow"
|
||
# → Enables browser automation testing
|
||
|
||
# Manual activation
|
||
/sc:validate "accessibility compliance" --play
|
||
```
|
||
|
||
### morphllm-fast-apply 🔄
|
||
|
||
[](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/mcp-servers.md#morphllm-fast-apply-)
|
||
|
||
**目的**: 効率的なパターンベースのコード変換 **トリガー**: 複数ファイルの編集、リファクタリング、フレームワークの移行 **要件**: Node.js 16+、MORPH_API_KEY
|
||
|
||
```shell
|
||
# Automatic activation
|
||
/sc:improve legacy-codebase/ --focus maintainability
|
||
# → Applies consistent patterns across files
|
||
|
||
# API key setup
|
||
export MORPH_API_KEY="your_key_here"
|
||
```
|
||
|
||
### セレナ🧭
|
||
|
||
[](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/mcp-servers.md#serena-)
|
||
|
||
**目的**: プロジェクトメモリを使用したセマンティックコード理解 **トリガー**: シンボル操作、大規模コードベース、セッション管理 **要件**: Python 3.9+、UV パッケージマネージャー、API キーなし
|
||
|
||
```shell
|
||
# Automatic activation
|
||
/sc:load existing-project/
|
||
# → Builds project understanding and memory
|
||
|
||
# Manual activation
|
||
/sc:refactor "extract UserService" --serena
|
||
```
|
||
|
||
## 構成
|
||
|
||
[](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/mcp-servers.md#configuration)
|
||
|
||
**MCP 構成ファイル ( `~/.claude.json`):**
|
||
|
||
```json
|
||
{
|
||
"mcpServers": {
|
||
"context7": {
|
||
"command": "npx",
|
||
"args": ["-y", "@upstash/context7-mcp@latest"]
|
||
},
|
||
"sequential-thinking": {
|
||
"command": "npx",
|
||
"args": ["-y", "@modelcontextprotocol/server-sequential-thinking"]
|
||
},
|
||
"magic": {
|
||
"command": "npx",
|
||
"args": ["@21st-dev/magic"],
|
||
"env": {"TWENTYFIRST_API_KEY": "${TWENTYFIRST_API_KEY}"}
|
||
},
|
||
"playwright": {
|
||
"command": "npx",
|
||
"args": ["@playwright/mcp@latest"]
|
||
},
|
||
"morphllm-fast-apply": {
|
||
"command": "npx",
|
||
"args": ["@morph-llm/morph-fast-apply"],
|
||
"env": {"MORPH_API_KEY": "${MORPH_API_KEY}"}
|
||
},
|
||
"serena": {
|
||
"command": "uvx",
|
||
"args": ["--from", "git+https://github.com/oraios/serena", "serena", "start-mcp-server", "--context", "ide-assistant"]
|
||
}
|
||
}
|
||
}
|
||
```
|
||
|
||
## 使用パターン
|
||
|
||
[](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/mcp-servers.md#usage-patterns)
|
||
|
||
**サーバー制御:**
|
||
|
||
```shell
|
||
# Enable specific servers
|
||
/sc:analyze codebase/ --c7 --seq
|
||
|
||
# Disable all MCP servers
|
||
/sc:implement "simple function" --no-mcp
|
||
|
||
# Enable all servers
|
||
/sc:design "complex architecture" --all-mcp
|
||
```
|
||
|
||
**マルチサーバー調整:**
|
||
|
||
```shell
|
||
# Full-stack development
|
||
/sc:implement "e-commerce checkout"
|
||
# → Sequential: workflow analysis
|
||
# → Context7: payment patterns
|
||
# → Magic: UI components
|
||
# → Serena: code organization
|
||
# → Playwright: E2E testing
|
||
```
|
||
|
||
## トラブルシューティング
|
||
|
||
[](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/mcp-servers.md#troubleshooting)
|
||
|
||
**よくある問題:**
|
||
|
||
- **サーバーが接続されていません**: Node.js を確認してください: `node --version`(v16 以上が必要)
|
||
- **Context7 が失敗しました**: キャッシュをクリアしてください:`npm cache clean --force`
|
||
- **Magic/Morphllm エラー**: API キーがない場合に発生する可能性があります (有料サービス)
|
||
- **サーバーのタイムアウト**: Claude Codeセッションを再起動します
|
||
|
||
**クイックフィックス:**
|
||
|
||
```shell
|
||
# Reset connections
|
||
# Restart Claude Code session
|
||
|
||
# Check dependencies
|
||
node --version # Should show v16+
|
||
|
||
# Test without MCP
|
||
/sc:command --no-mcp
|
||
|
||
# Check configuration
|
||
ls ~/.claude.json
|
||
```
|
||
|
||
**API キーの設定:**
|
||
|
||
```shell
|
||
# For Magic server (required for UI generation)
|
||
export TWENTYFIRST_API_KEY="your_key_here"
|
||
|
||
# For Morphllm server (required for bulk transformations)
|
||
export MORPH_API_KEY="your_key_here"
|
||
|
||
# Add to shell profile for persistence
|
||
echo 'export TWENTYFIRST_API_KEY="your_key"' >> ~/.bashrc
|
||
echo 'export MORPH_API_KEY="your_key"' >> ~/.bashrc
|
||
```
|
||
|
||
**環境変数の使用法:**
|
||
|
||
- ✅ `TWENTYFIRST_API_KEY`- Magic MCP サーバー機能に必要
|
||
- ✅ `MORPH_API_KEY`- Morphllm MCP サーバー機能に必要
|
||
- ❌ ドキュメント内のその他の環境変数 - 例のみ、フレームワークでは使用されません
|
||
- 📝 どちらも有料のサービスAPIキーですが、フレームワークはそれらなしでも動作します
|
||
|
||
## サーバーの組み合わせ
|
||
|
||
[](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/mcp-servers.md#server-combinations)
|
||
|
||
**APIキーなし(無料)** :
|
||
|
||
- コンテキスト7 + シーケンシャルシンキング + 劇作家 + セレナ
|
||
|
||
**1 APIキー**:
|
||
|
||
- プロフェッショナルなUI開発に魔法を加える
|
||
|
||
**2つのAPIキー**:
|
||
|
||
- 大規模リファクタリングのために morphllm-fast-apply を追加
|
||
|
||
**一般的なワークフロー:**
|
||
|
||
- **学習**:コンテキスト7 + シーケンシャルシンキング
|
||
- **Web開発**:マジック + context7 + プレイライト
|
||
- **エンタープライズリファクタリング**:serena + morphllm + sequential-thinking
|
||
- **複雑な分析**:シーケンシャルシンキング + コンテキスト7 + セレナ
|
||
|
||
## 統合
|
||
|
||
[](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/mcp-servers.md#integration)
|
||
|
||
**SuperClaude コマンドを使用する場合:**
|
||
|
||
- 分析コマンドは自動的にSequential + Serenaを使用します
|
||
- 実装コマンドはMagic + Context7を使用する
|
||
- テストコマンドにはPlaywright + Sequentialを使用する
|
||
|
||
**動作モードの場合:**
|
||
|
||
- ブレインストーミングモード:発見のためのシーケンシャル
|
||
- タスク管理:永続性のための Serena
|
||
- オーケストレーションモード: 最適なサーバーの選択
|
||
|
||
**パフォーマンスコントロール:**
|
||
|
||
- システム負荷に基づく自動リソース管理
|
||
- 同時実行制御: `--concurrency N`(1-15)
|
||
- 制約下での優先度ベースのサーバー選択
|
||
|
||
## 関連リソース
|
||
|
||
[](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/mcp-servers.md#related-resources)
|
||
|
||
**必読:**
|
||
|
||
- [コマンドガイド](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/commands.md)- MCPサーバーをアクティブ化するコマンド
|
||
- [クイックスタートガイド](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/Getting-Started/quick-start.md)- MCP セットアップガイド
|
||
|
||
**高度な使用法:**
|
||
|
||
- [行動モード](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/modes.md)- モード-MCP調整
|
||
- [エージェントガイド](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/agents.md)- エージェントとMCPの統合
|
||
- [セッション管理](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/User-Guide/session-management.md)- Serena ワークフロー
|
||
|
||
**技術リファレンス:**
|
||
|
||
- [例のクックブック](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/Reference/examples-cookbook.md)- MCP ワークフローパターン
|
||
- [技術アーキテクチャ](https://github.com/khayashi4337/SuperClaude_Framework/blob/master/docs/Developer-Guide/technical-architecture.md)- 統合の詳細 |