- Create 3-day plan to fix critical issues only - Focus on deployment, search, and deduplication - Remove overengineered 4-week plan versions - Add rollback strategy and test endpoints - Total new code: ~62 lines instead of enterprise architecture Ship the fixes, not the framework. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
146 lines
3.5 KiB
Markdown
146 lines
3.5 KiB
Markdown
# Immediate Deployment Action Plan
|
|
|
|
## 🚀 Quick Fix: Test if Tools are Actually Working
|
|
|
|
Based on the analysis, your implemented tools ARE working but the Docker image is outdated. Here's how to verify and fix:
|
|
|
|
## Option 1: Local Testing (Fastest)
|
|
|
|
```bash
|
|
# 1. Stop current Docker container
|
|
docker compose down
|
|
|
|
# 2. Run locally with npm
|
|
cd /Users/romualdczlonkowski/Pliki/n8n-mcp/n8n-mcp
|
|
npm run build
|
|
npm run start:http
|
|
|
|
# 3. Test with curl
|
|
curl -X POST http://localhost:3000/mcp \
|
|
-H "Content-Type: application/json" \
|
|
-d '{
|
|
"jsonrpc": "2.0",
|
|
"method": "tools/list",
|
|
"id": 1
|
|
}'
|
|
```
|
|
|
|
You should see all 12 tools including:
|
|
- get_node_essentials
|
|
- search_node_properties
|
|
- get_node_for_task
|
|
- list_tasks
|
|
- validate_node_config
|
|
- get_property_dependencies
|
|
|
|
## Option 2: Update Docker Image
|
|
|
|
```bash
|
|
# 1. Build new image with latest code
|
|
docker build -t ghcr.io/czlonkowski/n8n-mcp:v2.4.0 .
|
|
docker build -t ghcr.io/czlonkowski/n8n-mcp:latest .
|
|
|
|
# 2. Test locally
|
|
docker run -p 3000:3000 -e USE_FIXED_HTTP=true ghcr.io/czlonkowski/n8n-mcp:latest
|
|
|
|
# 3. Push to registry (if you have access)
|
|
docker push ghcr.io/czlonkowski/n8n-mcp:v2.4.0
|
|
docker push ghcr.io/czlonkowski/n8n-mcp:latest
|
|
```
|
|
|
|
## Option 3: Quick Local Docker Test
|
|
|
|
```bash
|
|
# 1. Update docker-compose.yml to build locally
|
|
cat > docker-compose.override.yml << 'EOF'
|
|
services:
|
|
n8n-mcp:
|
|
build: .
|
|
image: n8n-mcp:local
|
|
EOF
|
|
|
|
# 2. Rebuild and start
|
|
docker compose build
|
|
docker compose up -d
|
|
|
|
# 3. Check health
|
|
curl http://localhost:3000/health
|
|
```
|
|
|
|
## Claude Desktop Testing
|
|
|
|
After updating:
|
|
|
|
1. **Completely quit Claude Desktop** (not just close window)
|
|
2. **Clear any cache**:
|
|
```bash
|
|
# macOS
|
|
rm -rf ~/Library/Caches/com.anthropic.claude*
|
|
```
|
|
3. **Restart Claude Desktop**
|
|
4. **Test the new tools**:
|
|
- "List all available MCP tools"
|
|
- "Use get_node_essentials for HTTP Request"
|
|
- "Use get_node_for_task to configure a post_json_request"
|
|
|
|
## Diagnostic Script
|
|
|
|
```bash
|
|
# Save this as test-mcp-tools.sh
|
|
#!/bin/bash
|
|
|
|
echo "Testing MCP Tools Availability..."
|
|
|
|
# Test tool list
|
|
curl -s -X POST http://localhost:3000/mcp \
|
|
-H "Content-Type: application/json" \
|
|
-d '{"jsonrpc":"2.0","method":"tools/list","id":1}' | \
|
|
jq '.result.tools[].name' | sort
|
|
|
|
echo -e "\nTesting get_node_essentials..."
|
|
curl -s -X POST http://localhost:3000/mcp \
|
|
-H "Content-Type: application/json" \
|
|
-d '{
|
|
"jsonrpc":"2.0",
|
|
"method":"tools/call",
|
|
"params":{
|
|
"name":"get_node_essentials",
|
|
"arguments":{"nodeType":"nodes-base.httpRequest"}
|
|
},
|
|
"id":2
|
|
}' | jq '.result.content[0].text' -r | jq '.requiredProperties, .commonProperties' | head -20
|
|
```
|
|
|
|
## Expected Results
|
|
|
|
If everything is working, you should see:
|
|
1. **12 tools** in the tool list
|
|
2. **get_node_essentials** returns ~6 properties (not 200+)
|
|
3. **No errors** about missing tools
|
|
|
|
## If Tools Still Don't Appear
|
|
|
|
1. **Check which server file is being used**:
|
|
```bash
|
|
grep -n "from './server" dist/mcp/index.js
|
|
```
|
|
Should show: `from './server-update'`
|
|
|
|
2. **Verify the tools are in the compiled code**:
|
|
```bash
|
|
grep -c "get_node_essentials" dist/mcp/tools-update.js
|
|
```
|
|
Should show: 3 or more
|
|
|
|
3. **Check if there's a caching issue**:
|
|
- Add `?v=2` to your MCP URL in Claude Desktop config
|
|
- Or change the server name temporarily
|
|
|
|
## Next Steps
|
|
|
|
Once you confirm the tools are working:
|
|
1. Document the deployment process that worked
|
|
2. Update CI/CD to automate image builds
|
|
3. Proceed with V2 improvements (deduplication, etc.)
|
|
|
|
The tools ARE implemented - we just need to get the latest code deployed! |