Create Your First API Key

MCP API keys allow AI clients like Claude Desktop to connect to your n8n instance through the MCP server.

Prerequisites

Before creating an API key, ensure you have:

1. Signed in to the n8n MCP Bridge dashboard
2. n8n instance running (self-hosted or cloud)
3. n8n API key from your n8n instance

Get Your n8n API Key

For Self-Hosted n8n

1. Open your n8n instance
2. Go to Settings → API
3. Click Create API Key
4. Give it a name (e.g., "MCP Bridge")
5. Copy the API key immediately (you won't see it again)

For n8n Cloud

1. Log in to n8n.cloud
2. Go to Settings → API
3. Generate a new API key
4. Copy the key

Create MCP API Key

Step 1: Navigate to Dashboard

1. Sign in to n8n MCP Bridge at http://localhost:3000
2. Click Dashboard in the navigation
3. You'll see the Overview tab by default

Step 2: Add n8n Connection

If you don't have an n8n connection yet:

1. Click Add n8n Connection button
2. Enter the following details:
   • Connection Name: A friendly name (e.g., "My n8n Instance")
   • n8n URL: Your n8n instance URL (e.g., https://n8n.example.com)
   • n8n API Key: Paste the API key from n8n
3. Click Test Connection to verify
4. Click Create Connection

Step 3: Create API Key

1. Navigate to the API Keys tab
2. Click Create API Key
3. Fill in the form:
   • API Key Name: Descriptive name (e.g., "Claude Desktop - MacBook")
   • Select n8n Connection: Choose the connection you created
4. Click Create API Key

Step 4: Save Your API Key

The MCP API key will be displayed only once:

mcp_abc123xyz456def789ghi012jkl345

Important: Copy this key immediately and store it securely. You won't be able to see it again.

Verify Your API Key

Test that your API key works:

1. The dashboard shows a connection status indicator
2. Click Test Connection next to your API key
3. You should see: "Connection successful ✓"

If the test fails, check:

• n8n instance is accessible
• n8n API key is valid
• Network connectivity

API Key Details

Your API key entry shows:

• Name: The descriptive name you provided
• Connection: Which n8n connection it uses
• Created: When the key was created
• Last Used: When it was last accessed
• Status: Active or inactive

Security Best Practices

Keep Your Keys Secure

• Never commit API keys to version control
• Don't share keys with others
• Use separate keys for different clients/devices
• Rotate keys regularly for enhanced security

Revoke Compromised Keys

If an API key is compromised:

1. Go to the API Keys tab
2. Find the compromised key
3. Click the trash icon to delete it
4. Create a new API key immediately
5. Update all clients using the old key

API Key Format

MCP API keys follow this format:

mcp_[random-characters]

• Prefix: mcp_
• Length: 32+ characters
• Characters: Alphanumeric

Usage Limits

Current limitations:

• No usage limits by default
• Usage is tracked for analytics
• Can be configured per-key in the future

Next Steps

Now that you have an API key, connect it to Claude Desktop:

Connect to Claude Desktop →

Managing Multiple Keys

You can create multiple API keys for:

• Different devices: Separate keys for laptop, desktop, etc.
• Different clients: Claude Desktop, VS Code, Cursor
• Team members: Individual keys for team collaboration
• Testing: Separate keys for development and production

To create additional keys, repeat the process above.

API Key Metadata

Each API key stores:

• Connection details: Which n8n instance it connects to
• Access logs: When and how it was used
• Memory settings: Associated memory items (optional)

View this information in the dashboard under API Keys tab.