2025-10-01T07:17:44.707Z [info] [genesys-cloud] Client transport closed
2025-10-01T07:17:44.710Z [info] [genesys-cloud] Server transport closed
2025-10-01T07:17:44.710Z [info] [genesys-cloud] Client transport closed
2025-10-01T07:17:44.711Z [info] [genesys-cloud] Server transport closed unexpectedly, this is likely due to the process exiting early. If you are developing this MCP server you can add output to stderr (i.e. `console.error('...')` in JavaScript, `print('...', file=sys.stderr)` in python) and it will appear in this log.
Interesting. The error `McpError: MCP error -32001: Request timed out` suggests a tool is taking too long to complete and exceeding a time limit imposed by the MCP SDK I'm using.
Which tool where you using when it timed out? I'm assuming the Conversation Transcription one, as that naturally takes some time due to Genesys's underlying requirement of unarchiving transcripts etc.
After following the step i see below errors in mcp.log..
2025-10-01T07:16:44.027Z [info] [genesys-cloud] Initializing server...
2025-10-01T07:16:44.135Z [info] [genesys-cloud] Using MCP server command: C:\WINDOWS\System32\cmd.exe with args and path: {
args: [
'/C',
'C:\\Program Files\\nodejs\\npx.cmd',
'-y',
'@makingchatbots/genesys-cloud-mcp-server',
[length]: 4
],
paths: [
'C:\\Program Files\\nodejs',
'C:\\Program Files\\OpenSSL-Win64\\bin',
'C:\\WINDOWS\\system32',
'C:\\WINDOWS',
'C:\\WINDOWS\\System32\\Wbem',
'C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\',
'C:\\WINDOWS\\System32\\OpenSSH\\',
'C:\\Program Files\\Git\\cmd',
'C:\\Program Files\\dotnet\\',
'C:\\Program Files\\nodejs\\',
'',
'C:\\Program Files\\Docker\\Docker\\resources\\bin',
'C:\\Users\\Admin\\AppData\\Local\\Microsoft\\WindowsApps',
'C:\\Users\\Admin\\AppData\\Local\\GitHubDesktop\\bin',
'C:\\Users\\Admin\\AppData\\Local\\Microsoft\\WinGet\\Links',
'C:\\Users\\Admin\\AppData\\Roaming\\npm',
'C:\\Users\\Admin\\AppData\\Local\\Programs\\Microsoft VS Code\\bin',
[length]: 17
]
}
2025-10-01T07:16:44.158Z [info] [genesys-cloud] Server started and connected successfully
2025-10-01T07:16:44.571Z [info] [genesys-cloud] Message from client: {"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"claude-ai","version":"0.1.0"}},"jsonrpc":"2.0","id":0}
2025-10-01T07:17:44.706Z [info] [genesys-cloud] Message from client: {"jsonrpc":"2.0","method":"notifications/cancelled","params":{"requestId":0,"reason":"McpError: MCP error -32001: Request timed out"}}
2025-10-01T07:17:44.707Z [info] [genesys-cloud] Client transport closed
2025-10-01T07:17:44.710Z [info] [genesys-cloud] Server transport closed
2025-10-01T07:17:44.710Z [info] [genesys-cloud] Client transport closed
2025-10-01T07:17:44.711Z [info] [genesys-cloud] Server transport closed unexpectedly, this is likely due to the process exiting early. If you are developing this MCP server you can add output to stderr (i.e. `console.error('...')` in JavaScript, `print('...', file=sys.stderr)` in python) and it will appear in this log.
2025-10-01T07:17:44.712Z [error] [genesys-cloud] Server disconnected. For troubleshooting guidance, please visit our [debugging documentation](https://modelcontextprotocol.io/docs/tools/debugging)
2025-10-01T07:18:09.654Z [info] [genesys-cloud] Server transport closed
2025-10-01T07:18:09.655Z [info] [genesys-cloud] Client transport closed
Interesting. The error `McpError: MCP error -32001: Request timed out` suggests a tool is taking too long to complete and exceeding a time limit imposed by the MCP SDK I'm using.
Which tool where you using when it timed out? I'm assuming the Conversation Transcription one, as that naturally takes some time due to Genesys's underlying requirement of unarchiving transcripts etc.
I will take heed of the suggestion in the error message to increase logging, and investigate this further under the GitHub issue: https://github.com/MakingChatbots/genesys-cloud-mcp-server/issues/36
Thank you for letting me know about it. Would you be up for testing it again once I've made improvements?
Its not working after following exact steps
Hey, are you seeing any error messages?