What this error means
Claude only accepts OAuth, but n8n only provides an Access Token is a Claude Code failure pattern reported for developers trying to developer connects n8n instance mcp server to claude code; claude code requires oauth flow but n8n only provides access tokens, creating an incompatibility that blocks integration. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.
Why this happens
Found on n8n Community forum (community.n8n.io, post #296356, posted ~21 hours ago). Active discussion with solutions provided. Represents a growing category of AI agent integration friction between workflow automation platforms and Claude Code MCP. Category: AI Coding Tools per mapping rules.
Common causes
- Found on n8n Community forum (community.n8n.io, post #296356, posted ~21 hours ago). Active discussion with solutions provided. Represents a growing category of AI agent integration friction between workflow automation platforms and Claude Code MCP. Category: AI Coding Tools per mapping rules.
Quick fixes
- Confirm the exact error signature matches
Claude only accepts OAuth, but n8n only provides an Access Token. - Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
- Verify the account session, API key, provider settings, and environment where the failing tool is running.
Platform/tool-specific checks
- Verify the command, editor, extension, or API client that produced the error.
- Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
- Avoid deleting credentials, local model data, or project settings until the failing scope is clear.
Step-by-step troubleshooting
- Capture the exact error message and the command, editor action, or request that triggered it.
- Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
- Review the source evidence below and compare it with your environment.
- Apply one change at a time and rerun the smallest failing action.
- Keep the working fix documented for the team or deployment environment.
How to prevent it
- Keep provider/tool configuration documented.
- Record non-secret diagnostics such as tool version, provider name, model name, and command path.
- Add a lightweight check before CI or production workflows depend on the tool.