How to connect Cursor to n8n
Connect Cursor to an n8n test instance with OAuth and verify read access by finding one known workflow.
Free guide · Updated
Based on official documentation · Checked
Ask your agent
Copy the prompt and paste it into your assistant.
Quick answer
Enable instance-level MCP in a test n8n instance, choose Cursor in the connection dialog, and sign in with OAuth. Grant workflow read access for the first test and have Cursor search for a known workflow by name.
Prepare n8n and choose a test workflow
An instance owner or admin can enable MCP under Settings → Instance-level MCP. Pick a workflow that contains no customer records and whose title is easy to match. If the exercise needs the full workflow, mark that workflow Available in MCP. Workflow search can still return previews for other workflows the authenticated user can see, so use a test account with appropriate project access.
Connect Cursor with OAuth
In the n8n connection dialog, choose the OAuth tab, select Cursor and use One-click setup on n8n 2.33 or later. Cursor opens the connection and sends you to n8n for approval. Review the permission list and grant only workflow read access for this exercise.
For manual setup, copy the Server URL supplied by your n8n instance. Add the following entry to Cursor’s MCP configuration and complete OAuth from Cursor. Replace the example host. Merge the entry into your existing mcpServers object if you already have other tools.
{
"mcpServers": {
"n8n": {
"type": "streamable-http",
"url": "https://n8n.example.com/mcp-server/http"
}
}
}Practice
Find the workflow without running it
- Give Cursor the exact workflow name, for example Academy MCP sandbox.
- Ask Cursor to use the n8n search_workflows tool and return only the matching workflow’s name and ID. Leave the workflow idle and ask it to finish after the read.
- Compare the name and ID in the n8n editor. Under Connected clients, confirm that Cursor was granted the permissions you intended.
Output: The matching workflow name and ID, with the OAuth grant checked in n8n.
Fix a missing server or an empty search
If Cursor does not show n8n tools, check that the remote URL ends in /mcp-server/http and that Cursor finished the OAuth redirect. If search is empty, check the workflow name, the user and the project. A search preview only verifies discoverability. Full details and execution have separate access requirements.
To disconnect, open Connected clients in n8n and revoke the Cursor grant. Remove or disable the MCP entry in Cursor when you no longer need it.
Sources