-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Open
Description
I ran into this issue of request timing out.
N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE is set to true on n8n instance environment which is run on a host in a docker container.

The command above work if run on a local machine. Again, my host is set up correctly, as to a point where it works with all other MCP Servers.
Also npx n8n-mcp
is working perfectly fine when set up with JSON configs on clients like Claude Desktop.
I have tried running with environment variables, all separated by a comma (,) too, which resulted negative.

Complete log is found below:
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
[2025-09-23T13:37:20.978Z] [n8n-mcp] [WARN] Protocol version negotiated: client requested 2025-06-18, server will use 2025-03-26 {
reasoning: 'Client requested unsupported version 2025-06-18, using standard version'
}
Transport error: Unexpected token 'c', " clientVers"... is not valid JSON
Transport error: Unexpected token 'c', " clientCapa"... is not valid JSON
MCP client connection error: MCP error -32001: Request timed out
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
[2025-09-23T13:40:22.429Z] [n8n-mcp] [WARN] Protocol version negotiated: client requested 2025-06-18, server will use 2025-03-26 {
reasoning: 'Client requested unsupported version 2025-06-18, using standard version'
}
Transport error: Expected ',' or ']' after array element in JSON at position 5 (line 1 column 6)
Transport error: Unexpected token 'c', " clientVers"... is not valid JSON
MCP client connection error: MCP error -32001: Request timed out

Q: What is the issue and how do we address it?
Metadata
Metadata
Assignees
Labels
No labels