ros/n8n-mcp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

claude setup update

Browse Source
This commit is contained in:
czlonkowski
2025-06-13 12:12:20 +02:00
parent 00a6f700ed
commit d2c9c8c555
1 changed files with 4 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
README_CLAUDE_SETUP.md
View File

@@ -21,7 +21,7 @@
"n8n-documentation": { "n8n-documentation": {
"command": "node", "command": "node",
"args": [ "args": [
"/Users/romualdczlonkowski/Pliki/n8n-mcp/n8n-mcp/dist/mcp/index.js" "/Users/johndoe/projects/n8n-mcp/dist/mcp/index.js"
], ],
"env": { "env": {
"NODE_ENV": "production" "NODE_ENV": "production"
@@ -33,8 +33,6 @@
**Note**: Update the path in `args` to match your actual installation directory. **Note**: Update the path in `args` to match your actual installation directory.
> **New in v2.3**: The project now automatically handles Node.js version mismatches. If Claude Desktop uses a different Node.js version, the database adapter will automatically fall back to a pure JavaScript implementation (sql.js) that works with any version.
4. **Restart Claude Desktop** to load the new configuration. 4. **Restart Claude Desktop** to load the new configuration.
## Available Tools ## Available Tools
@@ -76,20 +74,14 @@ Once configured, you'll have access to these tools in Claude:
1. **If the server doesn't appear in Claude:** 1. **If the server doesn't appear in Claude:**
- Check that the path in `args` is absolute and correct - Check that the path in `args` is absolute and correct
- Ensure you've run `npm run build` and `npm run rebuild` - Ensure you've run `npm run build` and `npm run rebuild`
- Check Claude Desktop logs: `~/Library/Logs/Claude/mcp*.log` - Check `~/.n8n-mcp/logs/` for error logs
2. **If tools return errors:** 2. **If tools return errors:**
- Ensure the database exists: `data/nodes.db` - Ensure the database exists: `data/nodes.db`
- Run `npm run validate` to check the database - Run `npm run validate` to check the database
- Rebuild if necessary: `npm run rebuild` - Rebuild if necessary: `npm run rebuild`
3. **Node.js version issues:** 3. **For development/testing:**
- **No action needed!** The project automatically detects version mismatches
- If better-sqlite3 fails, it falls back to sql.js (pure JavaScript)
- You'll see a log message indicating which adapter is being used
- Both adapters provide identical functionality
4. **For development/testing:**
You can also run with more verbose logging: You can also run with more verbose logging:
```json ```json
{ {
@@ -106,9 +98,4 @@ Once configured, you'll have access to these tools in Claude:
} }
} }
} }
``` ```
5. **Checking which database adapter is active:**
Look for these log messages when the server starts:
- `Successfully initialized better-sqlite3 adapter` - Using native SQLite
- `Successfully initialized sql.js adapter` - Using pure JavaScript fallback