MCP Server Timeout issue

Describe the problem/error/question

My workflow was working fine till very recently. However, I have started to get timeout issue recently on the workflow. It works fine for the first time but the second request is failing with timeout error. Not sure what could be the issue,

What is the error message (if any)?

{
“errorMessage”: “Failed to execute operation: Failed to connect to MCP server: MCP error -32001: Request timed out”,
“errorDetails”: {},
“n8nDetails”: {
“time”: “6/23/2025, 11:47:22 AM”,
“n8nVersion”: “1.99.1 (Self Hosted)”,
“binaryDataMode”: “default”,
“cause”: {
“message”: “Failed to execute operation: Failed to connect to MCP server: MCP error -32001: Request timed out”,
“timestamp”: 1750693642515,
“name”: “NodeOperationError”,
“context”: {},
“cause”: {
“level”: “warning”,
“tags”: {}
}
}
}
}

Please share your workflow

(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.)

![image|690x298](upload://wGUAOkZaWTdDpxdwyQh3wNquIEY.png)

{
“nodes”: [
{
“parameters”: {
“options”: {
“allowFileUploads”: false
}
},
“type”: “@n8n/n8n-nodes-langchain.chatTrigger”,
“typeVersion”: 1.1,
“position”: [
-500,
-740
],
“id”: “9a551466-9cf5-4a33-9719-ef089568218c”,
“name”: “When chat message received”,
“webhookId”: “f0ea42f2-b846-4a08-87e8-2b132be988c7”,
“notesInFlow”: false
},
{
“parameters”: {},
“type”: “@n8n/n8n-nodes-langchain.memoryBufferWindow”,
“typeVersion”: 1.3,
“position”: [
-160,
-520
],
“id”: “b86a6265-3ebd-4671-bde5-7331439a4dc7”,
“name”: “Simple Memory”,
“disabled”: true
},
{
“parameters”: {},
“type”: “n8n-nodes-mcp.mcpClientTool”,
“typeVersion”: 1,
“position”: [
-40,
-520
],
“id”: “3d999fb7-1dd9-4639-87bc-bd26dc482449”,
“name”: “JIRA Tools”,
“notesInFlow”: false,
“executeOnce”: true,
“credentials”: {
“mcpClientApi”: {
“id”: “Fckc9074HWIY5dqq”,
“name”: “MCP Client (STDIO) account”
}
}
},
{
“parameters”: {
“respondWith”: “json”,
“options”: {}
},
“type”: “n8n-nodes-base.respondToWebhook”,
“typeVersion”: 1.2,
“position”: [
280,
-740
],
“id”: “c83f2069-a5aa-41a2-bd25-4390069566c4”,
“name”: “Respond to Webhook”
},
{
“parameters”: {
“descriptionType”: “manual”,
“toolDescription”: “This tool allows you to execute tools from Jira. Use this tool only if you know the exact name and description.”,
“operation”: “executeTool”,
“toolName”: “={{ $fromAI("toolName") }}”,
“toolParameters”: “={{ /n8n-auto-generated-fromAI-override/ $fromAI(‘Tool_Parameters’, ``, ‘json’) }}”
},
“type”: “n8n-nodes-mcp.mcpClientTool”,
“typeVersion”: 1,
“position”: [
80,
-520
],
“id”: “51436268-5ac2-40bd-ac2b-459e3148b673”,
“name”: “Jira Execute Tool”,
“notesInFlow”: false,
“executeOnce”: true,
“credentials”: {
“mcpClientApi”: {
“id”: “Fckc9074HWIY5dqq”,
“name”: “MCP Client (STDIO) account”
}
}
},
{
“parameters”: {
“promptType”: “define”,
“text”: “=You are a helpful agent with tools that helps the user to achive his goals.\nWhen user prompts for some task, first plan for your work. You use the available tools to plan for your work. You typically perform two tasks:\n1. List available tools in Jira\n2. Execute the selected tool from the previous workflow node. Do not guess.\n\nNext execute the selected tool without user confirmation, while using memory to understand your progress.\n\nUser request:\n{{ $json.chatInput }}”,
“options”: {
“maxIterations”: 5
}
},
“type”: “@n8n/n8n-nodes-langchain.agent”,
“typeVersion”: 1.9,
“position”: [
-188,
-740
],
“id”: “fb5ac0b5-d058-4a75-9545-05bc0fb67452”,
“name”: “JIRA Agent”,
“executeOnce”: true
},
{
“parameters”: {
“model”: {
“__rl”: true,
“mode”: “list”,
“value”: “gpt-4o-mini”
},
“options”: {
“maxTokens”: -1,
“temperature”: 0.7,
“timeout”: 60000,
“maxRetries”: 2
}
},
“type”: “@n8n/n8n-nodes-langchain.lmChatOpenAi”,
“typeVersion”: 1.2,
“position”: [
-280,
-520
],
“id”: “3575be16-9848-4c28-afe9-6d0dd8e72f02”,
“name”: “OpenAI LLM”,
“credentials”: {
“openAiApi”: {
“id”: “se9toHM1CJZJ2AQt”,
“name”: “OpenAi account”
}
}
}
],
“connections”: {
“When chat message received”: {
“main”: [
[
{
“node”: “JIRA Agent”,
“type”: “main”,
“index”: 0
}
]
]
},
“Simple Memory”: {
“ai_memory”: [
[
{
“node”: “JIRA Agent”,
“type”: “ai_memory”,
“index”: 0
}
]
]
},
“JIRA Tools”: {
“ai_tool”: [
[
{
“node”: “JIRA Agent”,
“type”: “ai_tool”,
“index”: 0
}
]
]
},
“Jira Execute Tool”: {
“ai_tool”: [
[
{
“node”: “JIRA Agent”,
“type”: “ai_tool”,
“index”: 0
}
]
]
},
“JIRA Agent”: {
“main”: [
[
{
“node”: “Respond to Webhook”,
“type”: “main”,
“index”: 0
}
]
]
},
“OpenAI LLM”: {
“ai_languageModel”: [
[
{
“node”: “JIRA Agent”,
“type”: “ai_languageModel”,
“index”: 0
}
]
]
}
},
“pinData”: {
“Simple Memory”: [
{
“isArtificialRecoveredEventItem”: true
}
],
“OpenAI LLM”: [
{
“isArtificialRecoveredEventItem”: true
}
]
},
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “9cc532cdccc1e0c1ad390d07f2c5b0399b28d4e035bff2e36acc57b0017209b8”
}
}

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 1.99.1
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: - ubuntu 12.4 LTS
1 Like

The error doesn’t point to any specific reason for the problem, but error wording suggests there could be a networking issue between the mcp client and the mcp server. “Request timed out” would happen if the client didn’t hear from the server in a pre-defined amount of time. Without having access to both sides and being able to capture traffic it is difficult to say why… Does mcp client send the request? Does mcp server receive the request? Does mcp server send the reply? Does mcp client (well, obviously the client doesn’t receive the response…).

Thanks for your response. As i said earlier, this started to happen very recently only. So not sure what would be the problem.
So could you please suggest, how to increase the timeout parameter or is there any other way to solve this problem?
Below is the mcp server that I am using.

Its an STDIO call.

Hey @albertnerikat,
sadly most of the time the timeout is not the problem (unless you really want to wait for 15 minutes to learn that you didn’t receive the response).

Similarly, how recent this started have little to do with the problem as this could be the problem with the “other side” or connectivity somewhere in between the host running the workflow and the destination server (a.k.a “in the Internets” :smile:).

If there is a support channel for mcp-atlassian, you could ask there as well, maybe they have a way to retrieve logs or know about any ongoing issues with reachability.

I have already reached out to them.
As i have mentioned in my original ticket. When I invoke the mcp-atlassian server for the first time, its reponding properly and executing the tool however, the second call is where the timeout happens. So is there anything else that I need to check.
I am using Docker over Easypanel setup. So is there something that I need to verify?

I tried to increase the server memory and also had 2 CPUs running and this resolved the issue. I guess still MCP servers need to improve on the memory leakages issues.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.