n8n 2.31.0 adds MCP OAuth support
n8n 2.31.0 adds an MCP OAuth base-URL variable for split-hostname setups, custom AWS Bedrock endpoints, IAM Assume Role auth, and tighter credential rules.
n8n released version 2.31.0 on July 14. The headline addition for self-hosted and multi-domain setups is a new N8N_MCP_BASE_URL environment variable, which lets MCP OAuth flows complete correctly when the MCP endpoint and the main n8n instance sit on different hostnames, a split-hostname deployment that previously broke the OAuth handshake.
AWS integrations get two additions: the AWS Bedrock Chat Model node now supports custom endpoints, useful for VPC or PrivateLink deployments that cannot reach the public Bedrock API, and the Cognito and IAM nodes add Assume Role authentication.
On the editor side, 2.31.0 adds agent favorites and a workflow reviews toggle under Security & policies. Credential handling tightens too: private credentials are now enabled by default and renamed to end-user credentials, and creating one is now limited to owner, admin, and project admin roles.
Two node changes worth noting: the Notion node migrates to a new API and is overhauled, and the Excel node is renamed to Microsoft Excel (OneDrive).
What it means
If you run n8n behind a reverse proxy or in a VPC, the MCP base-URL variable and the Bedrock custom endpoint option are the two settings to check before your next deploy. The credential-creation restriction is worth a look too, since it changes who on a team can wire up new integrations without an admin. The guide on automating the boring parts covers how to scope automation permissions like this.