n8n - 💡(How to fix) Fix Unable to connect Claude to instance MCP [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28277Fetched 2026-04-10 03:44:24
View on GitHub
Comments
2
Participants
3
Timeline
8
Reactions
0
Author
Timeline (top)
commented ×2mentioned ×2subscribed ×2closed ×1

Error Message

Describe the problem/error/question

What is the error message (if any)?

  • error: all

Code Example

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

We are unable to connect any Claude version to our instance MCP. This worked well until a couple of weeks ago, and has been broken ever since.

What is the error message (if any)?

Couldn't reach the MCP server. You can check the server URL and verify the server is running. If this persists, share this reference with support: "ofid_8d93906d3da8fc3f"

Please share your workflow/screenshots/recording

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

No nodes - this is core.

Share the output returned by the last node

<!-- If you need help with data transformations, please also share your expected output. -->

No nodes, no workflow, this is settings.

Debug info

core

  • n8nVersion: 2.15.0
  • platform: docker (cloud)
  • nodeJsVersion: 24.13.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 200
  • license: enterprise (production)

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 720 hours
  • maxCount: 25000 executions

client

  • userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/146.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-04-09T21:41:48.506Z

extent analysis

TL;DR

  • Verify the MCP server URL and ensure the server is running to resolve the connection issue.

Guidance

  • Check the MCP server URL for any typos or incorrect configurations.
  • Ensure the MCP server is running and accessible from the instance where Claude is being used.
  • Review the network connectivity and firewall settings to ensure they are not blocking the connection to the MCP server.
  • Consider checking the instance's logs for any error messages related to the MCP connection.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue seems to be related to a configuration or connectivity problem rather than a code issue, so a code snippet is not applicable.

Recommendation

  • Apply workaround: Verify the MCP server URL and ensure the server is running, as this is the most likely cause of the issue and a straightforward step to take before escalating to further support.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING