Files

czlonkowski 7606566c4c fix: resolve root cause of user switching failure in Docker

This fixes the fundamental issue causing persistent test failures.

Root Cause:
- The entrypoint script's user switching was broken
- Used 'exec $*' which fails when no arguments provided
- Used 'printf %q' which doesn't exist in Alpine Linux
- User switching wasn't actually working properly

Fixes:
1. Added su-exec package to Dockerfile
   - Proper tool for switching users in containers
   - Handles signal propagation correctly
   - No intermediate shell process

2. Rewrote user switching logic
   - Uses su-exec with fallback to su
   - Fixed command injection vulnerability in su fallback
   - Properly handles case when no arguments provided
   - Exports environment variables before switching

3. Added security improvements
   - Restricted permissions on AUTH_TOKEN_FILE
   - Added comments explaining su-exec benefits

This explains why tests kept failing - we were testing around a broken implementation rather than fixing the actual broken code.

2025-07-31 15:27:34 +02:00

docker-entrypoint.sh

fix: resolve root cause of user switching failure in Docker

2025-07-31 15:27:34 +02:00

n8n-mcp

fix: resolve Docker integration test failures in CI

2025-07-31 14:08:21 +02:00

parse-config.js

fix: resolve Docker integration test failures in CI

2025-07-31 14:08:21 +02:00

README.md

fix: add Docker configuration file support (fixes #105 )

2025-07-31 11:48:31 +02:00

README.md

Docker Usage Guide for n8n-mcp

Running in HTTP Mode

The n8n-mcp Docker container can be run in HTTP mode using several methods:

Method 1: Using Environment Variables (Recommended)

docker run -d -p 3000:3000 \
  --name n8n-mcp-server \
  -e MCP_MODE=http \
  -e AUTH_TOKEN=your-secure-token-here \
  ghcr.io/czlonkowski/n8n-mcp:latest

Method 2: Using docker-compose

# Create a .env file
cat > .env << EOF
MCP_MODE=http
AUTH_TOKEN=your-secure-token-here
PORT=3000
EOF

# Run with docker-compose
docker-compose up -d

Method 3: Using a Configuration File

Create a config.json file:

{
  "MCP_MODE": "http",
  "AUTH_TOKEN": "your-secure-token-here",
  "PORT": "3000",
  "LOG_LEVEL": "info"
}

Run with the config file:

docker run -d -p 3000:3000 \
  --name n8n-mcp-server \
  -v $(pwd)/config.json:/app/config.json:ro \
  ghcr.io/czlonkowski/n8n-mcp:latest

Method 4: Using the n8n-mcp serve Command

docker run -d -p 3000:3000 \
  --name n8n-mcp-server \
  -e AUTH_TOKEN=your-secure-token-here \
  ghcr.io/czlonkowski/n8n-mcp:latest \
  n8n-mcp serve

Important Notes

AUTH_TOKEN is required for HTTP mode. Generate a secure token:
```
openssl rand -base64 32
```
Environment variables take precedence over config file values
Default mode is stdio if MCP_MODE is not specified
Health check endpoint is available at http://localhost:3000/health

Troubleshooting

Container exits immediately

Check logs: docker logs n8n-mcp-server
Ensure AUTH_TOKEN is set for HTTP mode

"n8n-mcp: not found" error

This has been fixed in the latest version
Use the full command: node /app/dist/mcp/index.js as a workaround

Config file not working

Ensure the file is valid JSON
Mount as read-only: -v $(pwd)/config.json:/app/config.json:ro
Check that the config parser is present: docker exec n8n-mcp-server ls -la /app/docker/