Connect to Claude Desktop
Configure Claude Desktop to use your MCP server
Connect to Claude Desktop
Connect Claude Desktop to your n8n MCP Bridge to enable AI-powered workflow automation.
Prerequisites
Before you begin:
- Claude Desktop installed - Download from claude.ai
- MCP API key created - From the previous step
- n8n MCP Bridge running - Services should be running on ports 3000 and 3001
Configuration Steps
Step 1: Locate Claude Desktop Config
Claude Desktop stores its configuration in different locations depending on your OS:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
Windows:
%APPDATA%\Claude\claude_desktop_config.json
Linux:
~/.config/Claude/claude_desktop_config.json
Step 2: Get Your Configuration
From the n8n MCP Bridge dashboard:
- Go to the API Keys tab
- Find your API key
- Click Show Configuration
- Copy the JSON configuration
Example configuration:
{
"mcpServers": {
"n8n": {
"url": "http://localhost:3001/mcp?apiKey=mcp_abc123xyz456"
}
}
}
Step 3: Update Claude Desktop Config
- Open the Claude Desktop config file in a text editor
- If the file doesn't exist, create it
- Add or update the
mcpServerssection - Save the file
Complete example:
{
"mcpServers": {
"n8n": {
"url": "http://localhost:3001/mcp?apiKey=mcp_abc123xyz456def789"
}
}
}
Step 4: Restart Claude Desktop
- Quit Claude Desktop completely
- Restart the application
- The MCP server will be loaded automatically
Verify Connection
Check MCP Server Status
In Claude Desktop, you should see:
- A small indicator showing MCP servers are loaded
- In settings, the n8n MCP server should be listed as "Connected"
Test with a Query
Ask Claude to test the connection:
Can you ping my n8n instance?
Claude should respond with:
I'll ping your n8n instance using the ping_n8n tool...
Connection successful! ✓
n8n version: 1.x.x
Troubleshooting
MCP Server Not Loading
If Claude doesn't load the MCP server:
-
Check the config file format:
- Must be valid JSON
- No trailing commas
- Proper quotation marks
-
Verify the URL:
- Should be
http://localhost:3001/mcp - Include
?apiKey=parameter with your key - No spaces or special characters in URL
- Should be
-
Check Claude Desktop logs:
- macOS:
~/Library/Logs/Claude/ - Windows:
%APPDATA%\Claude\logs\ - Look for MCP-related errors
- macOS:
Connection Failed
If Claude can connect to MCP but not to n8n:
-
Verify MCP server is running:
curl http://localhost:3001/healthShould return:
{"status":"ok"} -
Check API key is valid:
- Go to dashboard → API Keys
- Click Test Connection
- Should show "Connected ✓"
-
Verify n8n is accessible:
- Open your n8n instance in a browser
- Ensure it's reachable from your machine
Invalid API Key
If you see "Invalid API key" errors:
- Verify the API key in the config matches the one in your dashboard
- Ensure the key hasn't been deleted or revoked
- Create a new API key if needed
Advanced Configuration
Multiple MCP Servers
You can connect to multiple MCP servers:
{
"mcpServers": {
"n8n-production": {
"url": "http://localhost:3001/mcp?apiKey=mcp_prod_key"
},
"n8n-development": {
"url": "http://localhost:3002/mcp?apiKey=mcp_dev_key"
}
}
}
Remote MCP Server
To connect to a remote n8n MCP Bridge:
{
"mcpServers": {
"n8n": {
"url": "https://mcp.example.com/mcp?apiKey=mcp_your_key"
}
}
}
Note: Ensure the remote server has HTTPS enabled and is publicly accessible.
Security Considerations
Keep Your API Key Secure
The claude_desktop_config.json file contains your API key in plaintext:
- File permissions: Ensure only you can read this file
- Don't share: Never share this config file
- Backup safely: If you back up this file, encrypt it
- Revoke if exposed: If the file is compromised, revoke the API key immediately
Network Security
When using remote MCP servers:
- Always use HTTPS, never HTTP in production
- Verify SSL certificates
- Use VPN if connecting to internal servers
- Monitor API key usage in the dashboard
Next Steps
Congratulations! You've successfully connected Claude Desktop to n8n MCP Bridge.
Explore Available Tools
Learn about all the MCP tools available:
Set Up Memory System
Configure persistent context for your AI conversations:
Advanced Guides
Example Usage
Try these commands with Claude:
# Test connectivity
Can you ping my n8n instance?
# List available workflows (coming soon)
What workflows do I have in n8n?
# Execute a workflow (coming soon)
Run my "Send Email" workflow
Getting Help
If you're still having issues:
- Check the Troubleshooting Guide
- View GitHub Issues
- Review the API Reference