oh-my-claude-sisyphus 3.5.5 → 3.5.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -8,7 +8,7 @@ Configure Model Context Protocol (MCP) servers to extend Claude Code's capabilit
8
8
 
9
9
  ## Overview
10
10
 
11
- MCP servers provide additional tools that Claude Code agents can use. This skill helps you configure popular MCP servers using the `claude mcp add` command-line interface.
11
+ MCP servers provide additional tools that Claude Code agents can use. This skill helps you configure popular MCP servers in your `~/.claude/settings.json`.
12
12
 
13
13
  ## Step 1: Show Available MCP Servers
14
14
 
@@ -54,51 +54,94 @@ Do you have a GitHub Personal Access Token?
54
54
  - Enter your token, or type 'skip' to configure later
55
55
  ```
56
56
 
57
- ## Step 3: Add MCP Servers Using CLI
57
+ ## Step 3: Update settings.json
58
58
 
59
- Use the `claude mcp add` command to configure each MCP server. The CLI automatically handles settings.json updates and merging.
59
+ Read the current `~/.claude/settings.json` and add/update the `mcpServers` section.
60
60
 
61
61
  ### Context7 Configuration:
62
- ```bash
63
- claude mcp add context7 -- npx -y @upstash/context7-mcp
62
+ ```json
63
+ {
64
+ "mcpServers": {
65
+ "context7": {
66
+ "command": "npx",
67
+ "args": ["-y", "@upstash/context7-mcp"]
68
+ }
69
+ }
70
+ }
64
71
  ```
65
72
 
66
73
  ### Exa Web Search Configuration:
67
- ```bash
68
- claude mcp add -e EXA_API_KEY=<user-provided-key> exa -- npx -y exa-mcp-server
74
+ ```json
75
+ {
76
+ "mcpServers": {
77
+ "exa": {
78
+ "command": "npx",
79
+ "args": ["-y", "exa-mcp-server"],
80
+ "env": {
81
+ "EXA_API_KEY": "<user-provided-key>"
82
+ }
83
+ }
84
+ }
85
+ }
69
86
  ```
70
87
 
71
88
  ### Filesystem Configuration:
72
- ```bash
73
- claude mcp add filesystem -- npx -y @modelcontextprotocol/server-filesystem <allowed-directories>
89
+ ```json
90
+ {
91
+ "mcpServers": {
92
+ "filesystem": {
93
+ "command": "npx",
94
+ "args": ["-y", "@modelcontextprotocol/server-filesystem", "<allowed-directories>"]
95
+ }
96
+ }
97
+ }
74
98
  ```
75
99
 
76
100
  ### GitHub Configuration:
101
+ ```json
102
+ {
103
+ "mcpServers": {
104
+ "github": {
105
+ "command": "docker",
106
+ "args": ["run", "-i", "--rm", "-e", "GITHUB_PERSONAL_ACCESS_TOKEN", "ghcr.io/github/github-mcp-server"],
107
+ "env": {
108
+ "GITHUB_PERSONAL_ACCESS_TOKEN": "<user-provided-token>"
109
+ }
110
+ }
111
+ }
112
+ }
113
+ ```
114
+ > Note: GitHub MCP requires Docker. Alternatively, configure as a remote URL: https://api.githubcopilot.com/mcp/
115
+
116
+ ## Step 4: Merge Configuration
117
+
118
+ When updating settings.json:
119
+
120
+ 1. Read existing file: `~/.claude/settings.json`
121
+ 2. Parse as JSON (handle comments with jsonc-parser if needed)
122
+ 3. Merge new `mcpServers` entries with existing ones (don't overwrite user's other MCP servers)
123
+ 4. Write back to file with proper formatting
77
124
 
78
- **Option 1: Docker (local)**
79
125
  ```bash
80
- claude mcp add -e GITHUB_PERSONAL_ACCESS_TOKEN=<user-provided-token> github -- docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io/github/github-mcp-server
126
+ # Backup existing settings first
127
+ cp ~/.claude/settings.json ~/.claude/settings.json.bak 2>/dev/null || true
81
128
  ```
82
129
 
83
- **Option 2: HTTP (remote)**
84
- ```bash
85
- claude mcp add --transport http github https://api.githubcopilot.com/mcp/
86
- ```
130
+ Use the Edit tool or Write tool to update the settings file, preserving existing configuration.
87
131
 
88
- > Note: Docker option requires Docker installed. HTTP option is simpler but may have different capabilities.
89
-
90
- ## Step 4: Verify Installation
132
+ ## Step 5: Verify Installation
91
133
 
92
134
  After configuration, verify the MCP servers are properly set up:
93
135
 
94
136
  ```bash
95
- # List configured MCP servers
96
- claude mcp list
97
- ```
137
+ # Check if settings.json has mcpServers
138
+ grep -q "mcpServers" ~/.claude/settings.json && echo "MCP servers configured" || echo "Configuration may have failed"
98
139
 
99
- This will display all configured MCP servers and their status.
140
+ # List configured servers
141
+ node -e "const s = require('$HOME/.claude/settings.json'); console.log('Configured MCP servers:', Object.keys(s.mcpServers || {}).join(', ') || 'none')"
142
+ ```
100
143
 
101
- ## Step 5: Show Completion Message
144
+ ## Step 6: Show Completion Message
102
145
 
103
146
  ```
104
147
  MCP Server Configuration Complete!
@@ -109,7 +152,6 @@ CONFIGURED SERVERS:
109
152
  NEXT STEPS:
110
153
  1. Restart Claude Code for changes to take effect
111
154
  2. The configured MCP tools will be available to all agents
112
- 3. Run `claude mcp list` to verify configuration
113
155
 
114
156
  USAGE TIPS:
115
157
  - Context7: Ask about library documentation (e.g., "How do I use React hooks?")
@@ -118,15 +160,11 @@ USAGE TIPS:
118
160
  - GitHub: Interact with GitHub repos, issues, and PRs
119
161
 
120
162
  TROUBLESHOOTING:
121
- - If MCP servers don't appear, run `claude mcp list` to check status
122
- - Ensure you have Node.js 18+ installed for npx-based servers
123
- - For GitHub Docker option, ensure Docker is installed and running
163
+ - If MCP servers don't appear, check ~/.claude/settings.json for syntax errors
164
+ - Ensure you have Node.js 18+ installed for npx commands
124
165
  - Run /oh-my-claudecode:doctor to diagnose issues
125
166
 
126
- MANAGING MCP SERVERS:
127
- - Add more servers: /oh-my-claudecode:mcp-setup or `claude mcp add ...`
128
- - List servers: `claude mcp list`
129
- - Remove a server: `claude mcp remove <server-name>`
167
+ To add more MCP servers later, run: /oh-my-claudecode:mcp-setup
130
168
  ```
131
169
 
132
170
  ## Custom MCP Server
@@ -135,50 +173,23 @@ If user selects "Custom":
135
173
 
136
174
  Ask for:
137
175
  1. Server name (identifier)
138
- 2. Transport type: `stdio` (default) or `http`
139
- 3. For stdio: Command and arguments (e.g., `npx my-mcp-server`)
140
- 4. For http: URL (e.g., `https://example.com/mcp`)
141
- 5. Environment variables (optional, key=value pairs)
142
- 6. HTTP headers (optional, for http transport only)
176
+ 2. Command to run (e.g., `npx`, `node`, path to executable)
177
+ 3. Arguments (comma-separated)
178
+ 4. Environment variables (optional, key=value pairs)
143
179
 
144
- Then construct and run the appropriate `claude mcp add` command:
145
-
146
- **For stdio servers:**
147
- ```bash
148
- # Without environment variables
149
- claude mcp add <server-name> -- <command> [args...]
150
-
151
- # With environment variables
152
- claude mcp add -e KEY1=value1 -e KEY2=value2 <server-name> -- <command> [args...]
153
- ```
154
-
155
- **For HTTP servers:**
156
- ```bash
157
- # Basic HTTP server
158
- claude mcp add --transport http <server-name> <url>
159
-
160
- # HTTP server with headers
161
- claude mcp add --transport http --header "Authorization: Bearer <token>" <server-name> <url>
162
- ```
180
+ Then add to mcpServers section accordingly.
163
181
 
164
182
  ## Common Issues
165
183
 
166
184
  ### MCP Server Not Loading
167
185
  - Ensure Node.js 18+ is installed
168
186
  - Check that npx is available in PATH
169
- - Run `claude mcp list` to verify server status
170
- - Check server logs for errors
187
+ - Verify no JSON syntax errors in settings.json
171
188
 
172
189
  ### API Key Issues
173
190
  - Exa: Verify key at https://dashboard.exa.ai
174
- - GitHub: Ensure token has required scopes (repo, read:org)
175
- - Re-run `claude mcp add` with correct credentials if needed
191
+ - GitHub: Ensure token has required scopes
176
192
 
177
193
  ### Agents Still Using Built-in Tools
178
194
  - Restart Claude Code after configuration
179
195
  - The built-in websearch will be deprioritized when exa is configured
180
- - Run `claude mcp list` to confirm servers are active
181
-
182
- ### Removing or Updating a Server
183
- - Remove: `claude mcp remove <server-name>`
184
- - Update: Remove the old server, then add it again with new configuration
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "oh-my-claude-sisyphus",
3
- "version": "3.5.5",
3
+ "version": "3.5.6",
4
4
  "description": "Multi-agent orchestration system for Claude Code - Inspired by oh-my-opencode",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -9,7 +9,7 @@ Configure Model Context Protocol (MCP) servers to extend Claude Code's capabilit
9
9
 
10
10
  ## Overview
11
11
 
12
- MCP servers provide additional tools that Claude Code agents can use. This skill helps you configure popular MCP servers in your `~/.claude/settings.json`.
12
+ MCP servers provide additional tools that Claude Code agents can use. This skill helps you configure popular MCP servers using the `claude mcp add` command-line interface.
13
13
 
14
14
  ## Step 1: Show Available MCP Servers
15
15
 
@@ -55,95 +55,51 @@ Do you have a GitHub Personal Access Token?
55
55
  - Enter your token, or type 'skip' to configure later
56
56
  ```
57
57
 
58
- ## Step 3: Update settings.json
58
+ ## Step 3: Add MCP Servers Using CLI
59
59
 
60
- Read the current `~/.claude/settings.json` and add/update the `mcpServers` section.
60
+ Use the `claude mcp add` command to configure each MCP server. The CLI automatically handles settings.json updates and merging.
61
61
 
62
62
  ### Context7 Configuration:
63
- ```json
64
- {
65
- "mcpServers": {
66
- "context7": {
67
- "command": "npx",
68
- "args": ["-y", "@upstash/context7-mcp"]
69
- }
70
- }
71
- }
63
+ ```bash
64
+ claude mcp add context7 -- npx -y @upstash/context7-mcp
72
65
  ```
73
66
 
74
67
  ### Exa Web Search Configuration:
75
- ```json
76
- {
77
- "mcpServers": {
78
- "exa": {
79
- "command": "npx",
80
- "args": ["-y", "exa-mcp-server"],
81
- "env": {
82
- "EXA_API_KEY": "<user-provided-key>"
83
- }
84
- }
85
- }
86
- }
68
+ ```bash
69
+ claude mcp add -e EXA_API_KEY=<user-provided-key> exa -- npx -y exa-mcp-server
87
70
  ```
88
71
 
89
72
  ### Filesystem Configuration:
90
- ```json
91
- {
92
- "mcpServers": {
93
- "filesystem": {
94
- "command": "npx",
95
- "args": ["-y", "@modelcontextprotocol/server-filesystem", "<allowed-directories>"]
96
- }
97
- }
98
- }
73
+ ```bash
74
+ claude mcp add filesystem -- npx -y @modelcontextprotocol/server-filesystem <allowed-directories>
99
75
  ```
100
76
 
101
77
  ### GitHub Configuration:
102
- ```json
103
- {
104
- "mcpServers": {
105
- "github": {
106
- "command": "docker",
107
- "args": ["run", "-i", "--rm", "-e", "GITHUB_PERSONAL_ACCESS_TOKEN", "ghcr.io/github/github-mcp-server"],
108
- "env": {
109
- "GITHUB_PERSONAL_ACCESS_TOKEN": "<user-provided-token>"
110
- }
111
- }
112
- }
113
- }
114
- ```
115
-
116
- > Note: GitHub MCP requires Docker. Alternatively, configure as a remote URL: https://api.githubcopilot.com/mcp/
117
78
 
118
- ## Step 4: Merge Configuration
119
-
120
- When updating settings.json:
121
-
122
- 1. Read existing file: `~/.claude/settings.json`
123
- 2. Parse as JSON (handle comments with jsonc-parser if needed)
124
- 3. Merge new `mcpServers` entries with existing ones (don't overwrite user's other MCP servers)
125
- 4. Write back to file with proper formatting
79
+ **Option 1: Docker (local)**
80
+ ```bash
81
+ claude mcp add -e GITHUB_PERSONAL_ACCESS_TOKEN=<user-provided-token> github -- docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io/github/github-mcp-server
82
+ ```
126
83
 
84
+ **Option 2: HTTP (remote)**
127
85
  ```bash
128
- # Backup existing settings first
129
- cp ~/.claude/settings.json ~/.claude/settings.json.bak 2>/dev/null || true
86
+ claude mcp add --transport http github https://api.githubcopilot.com/mcp/
130
87
  ```
131
88
 
132
- Use the Edit tool or Write tool to update the settings file, preserving existing configuration.
89
+ > Note: Docker option requires Docker installed. HTTP option is simpler but may have different capabilities.
133
90
 
134
- ## Step 5: Verify Installation
91
+ ## Step 4: Verify Installation
135
92
 
136
93
  After configuration, verify the MCP servers are properly set up:
137
94
 
138
95
  ```bash
139
- # Check if settings.json has mcpServers
140
- grep -q "mcpServers" ~/.claude/settings.json && echo "MCP servers configured" || echo "Configuration may have failed"
141
-
142
- # List configured servers
143
- node -e "const s = require('$HOME/.claude/settings.json'); console.log('Configured MCP servers:', Object.keys(s.mcpServers || {}).join(', ') || 'none')"
96
+ # List configured MCP servers
97
+ claude mcp list
144
98
  ```
145
99
 
146
- ## Step 6: Show Completion Message
100
+ This will display all configured MCP servers and their status.
101
+
102
+ ## Step 5: Show Completion Message
147
103
 
148
104
  ```
149
105
  MCP Server Configuration Complete!
@@ -154,6 +110,7 @@ CONFIGURED SERVERS:
154
110
  NEXT STEPS:
155
111
  1. Restart Claude Code for changes to take effect
156
112
  2. The configured MCP tools will be available to all agents
113
+ 3. Run `claude mcp list` to verify configuration
157
114
 
158
115
  USAGE TIPS:
159
116
  - Context7: Ask about library documentation (e.g., "How do I use React hooks?")
@@ -162,11 +119,15 @@ USAGE TIPS:
162
119
  - GitHub: Interact with GitHub repos, issues, and PRs
163
120
 
164
121
  TROUBLESHOOTING:
165
- - If MCP servers don't appear, check ~/.claude/settings.json for syntax errors
166
- - Ensure you have Node.js 18+ installed for npx commands
122
+ - If MCP servers don't appear, run `claude mcp list` to check status
123
+ - Ensure you have Node.js 18+ installed for npx-based servers
124
+ - For GitHub Docker option, ensure Docker is installed and running
167
125
  - Run /oh-my-claudecode:doctor to diagnose issues
168
126
 
169
- To add more MCP servers later, run: /oh-my-claudecode:mcp-setup
127
+ MANAGING MCP SERVERS:
128
+ - Add more servers: /oh-my-claudecode:mcp-setup or `claude mcp add ...`
129
+ - List servers: `claude mcp list`
130
+ - Remove a server: `claude mcp remove <server-name>`
170
131
  ```
171
132
 
172
133
  ## Custom MCP Server
@@ -175,23 +136,50 @@ If user selects "Custom":
175
136
 
176
137
  Ask for:
177
138
  1. Server name (identifier)
178
- 2. Command to run (e.g., `npx`, `node`, path to executable)
179
- 3. Arguments (comma-separated)
180
- 4. Environment variables (optional, key=value pairs)
139
+ 2. Transport type: `stdio` (default) or `http`
140
+ 3. For stdio: Command and arguments (e.g., `npx my-mcp-server`)
141
+ 4. For http: URL (e.g., `https://example.com/mcp`)
142
+ 5. Environment variables (optional, key=value pairs)
143
+ 6. HTTP headers (optional, for http transport only)
144
+
145
+ Then construct and run the appropriate `claude mcp add` command:
146
+
147
+ **For stdio servers:**
148
+ ```bash
149
+ # Without environment variables
150
+ claude mcp add <server-name> -- <command> [args...]
151
+
152
+ # With environment variables
153
+ claude mcp add -e KEY1=value1 -e KEY2=value2 <server-name> -- <command> [args...]
154
+ ```
181
155
 
182
- Then add to mcpServers section accordingly.
156
+ **For HTTP servers:**
157
+ ```bash
158
+ # Basic HTTP server
159
+ claude mcp add --transport http <server-name> <url>
160
+
161
+ # HTTP server with headers
162
+ claude mcp add --transport http --header "Authorization: Bearer <token>" <server-name> <url>
163
+ ```
183
164
 
184
165
  ## Common Issues
185
166
 
186
167
  ### MCP Server Not Loading
187
168
  - Ensure Node.js 18+ is installed
188
169
  - Check that npx is available in PATH
189
- - Verify no JSON syntax errors in settings.json
170
+ - Run `claude mcp list` to verify server status
171
+ - Check server logs for errors
190
172
 
191
173
  ### API Key Issues
192
174
  - Exa: Verify key at https://dashboard.exa.ai
193
- - GitHub: Ensure token has required scopes
175
+ - GitHub: Ensure token has required scopes (repo, read:org)
176
+ - Re-run `claude mcp add` with correct credentials if needed
194
177
 
195
178
  ### Agents Still Using Built-in Tools
196
179
  - Restart Claude Code after configuration
197
180
  - The built-in websearch will be deprioritized when exa is configured
181
+ - Run `claude mcp list` to confirm servers are active
182
+
183
+ ### Removing or Updating a Server
184
+ - Remove: `claude mcp remove <server-name>`
185
+ - Update: Remove the old server, then add it again with new configuration