MCP sentry server fails to connect with claud Desktop client

[vansh132]

2025-03-04T09:00:46.747Z [sentry] [info] Initializing server...
2025-03-04T09:00:46.761Z [sentry] [error] spawn python ENOENT {"context":"connection","stack":"Error: spawn python ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T09:00:46.761Z [sentry] [error] spawn python ENOENT {"stack":"Error: spawn python ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T09:00:46.768Z [sentry] [info] Server transport closed
2025-03-04T09:00:46.768Z [sentry] [info] Client transport closed
2025-03-04T09:00:46.769Z [sentry] [info] 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-03-04T09:00:46.769Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T09:00:50.254Z [sentry] [info] Initializing server...
2025-03-04T09:00:50.300Z [sentry] [error] spawn python ENOENT {"context":"connection","stack":"Error: spawn python ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T09:00:50.301Z [sentry] [error] spawn python ENOENT {"stack":"Error: spawn python ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T09:00:50.303Z [sentry] [info] Server transport closed
2025-03-04T09:00:50.303Z [sentry] [info] Client transport closed
2025-03-04T09:00:50.303Z [sentry] [info] 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-03-04T09:00:50.303Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T09:01:57.210Z [sentry] [info] Initializing server...
2025-03-04T09:01:57.224Z [sentry] [error] spawn python ENOENT {"context":"connection","stack":"Error: spawn python ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T09:01:57.224Z [sentry] [error] spawn python ENOENT {"stack":"Error: spawn python ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T09:01:57.229Z [sentry] [info] Server transport closed
2025-03-04T09:01:57.229Z [sentry] [info] Client transport closed
2025-03-04T09:01:57.230Z [sentry] [info] 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-03-04T09:01:57.230Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T09:02:01.156Z [sentry] [info] Initializing server...
2025-03-04T09:02:01.189Z [sentry] [error] spawn python ENOENT {"context":"connection","stack":"Error: spawn python ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T09:02:01.189Z [sentry] [error] spawn python ENOENT {"stack":"Error: spawn python ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T09:02:01.190Z [sentry] [info] Server transport closed
2025-03-04T09:02:01.190Z [sentry] [info] Client transport closed
2025-03-04T09:02:01.190Z [sentry] [info] 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-03-04T09:02:01.190Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T09:08:18.578Z [sentry] [info] Initializing server...
2025-03-04T09:08:18.591Z [sentry] [error] spawn python ENOENT {"context":"connection","stack":"Error: spawn python ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T09:08:18.591Z [sentry] [error] spawn python ENOENT {"stack":"Error: spawn python ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T09:08:18.596Z [sentry] [info] Server transport closed
2025-03-04T09:08:18.596Z [sentry] [info] Client transport closed
2025-03-04T09:08:18.597Z [sentry] [info] 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-03-04T09:08:18.597Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T09:08:21.085Z [sentry] [info] Initializing server...
2025-03-04T09:08:21.119Z [sentry] [error] spawn python ENOENT {"context":"connection","stack":"Error: spawn python ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T09:08:21.119Z [sentry] [error] spawn python ENOENT {"stack":"Error: spawn python ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T09:08:21.120Z [sentry] [info] Server transport closed
2025-03-04T09:08:21.121Z [sentry] [info] Client transport closed
2025-03-04T09:08:21.121Z [sentry] [info] 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-03-04T09:08:21.121Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T09:14:39.106Z [sentry] [info] Initializing server...
2025-03-04T09:14:39.126Z [sentry] [info] Server started and connected successfully
2025-03-04T09:14:39.192Z [sentry] [info] Message from client: {"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"claude-ai","version":"0.1.0"}},"jsonrpc":"2.0","id":0}
2025-03-04T09:14:41.690Z [sentry] [info] Initializing server...
2025-03-04T09:14:41.710Z [sentry] [info] Server started and connected successfully
2025-03-04T09:14:41.718Z [sentry] [info] Message from client: {"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"claude-ai","version":"0.1.0"}},"jsonrpc":"2.0","id":0}
Usage: mcp-server-sentry [OPTIONS]
Try 'mcp-server-sentry --help' for help.

Usage: mcp-server-sentry [OPTIONS]
Try 'mcp-server-sentry --help' for help.

Error: No such option: -m
Error: No such option: -m
2025-03-04T09:14:45.559Z [sentry] [info] Server transport closed
2025-03-04T09:14:45.560Z [sentry] [info] Client transport closed
2025-03-04T09:14:45.560Z [sentry] [info] 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-03-04T09:14:45.560Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T09:14:45.561Z [sentry] [info] Client transport closed
2025-03-04T09:14:45.561Z [sentry] [info] Server transport closed
2025-03-04T09:14:45.561Z [sentry] [info] Client transport closed
2025-03-04T09:14:45.561Z [sentry] [info] 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-03-04T09:14:45.561Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T09:14:45.561Z [sentry] [info] Client transport closed
2025-03-04T09:22:57.197Z [sentry] [info] Initializing server...
2025-03-04T09:22:57.213Z [sentry] [error] spawn uvx ENOENT {"context":"connection","stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T09:22:57.213Z [sentry] [error] spawn uvx ENOENT {"stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T09:22:57.220Z [sentry] [info] Server transport closed
2025-03-04T09:22:57.220Z [sentry] [info] Client transport closed
2025-03-04T09:22:57.220Z [sentry] [info] 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-03-04T09:22:57.220Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T09:23:00.892Z [sentry] [info] Initializing server...
2025-03-04T09:23:00.924Z [sentry] [error] spawn uvx ENOENT {"context":"connection","stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T09:23:00.924Z [sentry] [error] spawn uvx ENOENT {"stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T09:23:00.925Z [sentry] [info] Server transport closed
2025-03-04T09:23:00.925Z [sentry] [info] Client transport closed
2025-03-04T09:23:00.925Z [sentry] [info] 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-03-04T09:23:00.925Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T09:26:33.237Z [sentry] [info] Initializing server...
2025-03-04T09:26:33.252Z [sentry] [info] Server started and connected successfully
2025-03-04T09:26:33.259Z [sentry] [info] Message from client: {"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"claude-ai","version":"0.1.0"}},"jsonrpc":"2.0","id":0}
Usage: mcp-server-sentry [OPTIONS]
Try 'mcp-server-sentry --help' for help.

Error: Got unexpected extra argument (mcp-server-sentry)
2025-03-04T09:26:36.445Z [sentry] [info] Server transport closed
2025-03-04T09:26:36.445Z [sentry] [info] Client transport closed
2025-03-04T09:26:36.446Z [sentry] [info] 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-03-04T09:26:36.446Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T09:26:36.446Z [sentry] [info] Client transport closed
2025-03-04T09:26:36.575Z [sentry] [info] Initializing server...
2025-03-04T09:26:36.598Z [sentry] [info] Server started and connected successfully
2025-03-04T09:26:36.606Z [sentry] [info] Message from client: {"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"claude-ai","version":"0.1.0"}},"jsonrpc":"2.0","id":0}
Usage: mcp-server-sentry [OPTIONS]
Try 'mcp-server-sentry --help' for help.

Error: Got unexpected extra argument (mcp-server-sentry)
2025-03-04T09:26:37.381Z [sentry] [info] Server transport closed
2025-03-04T09:26:37.381Z [sentry] [info] Client transport closed
2025-03-04T09:26:37.381Z [sentry] [info] 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-03-04T09:26:37.381Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T09:26:37.381Z [sentry] [info] Client transport closed
2025-03-04T10:01:17.057Z [sentry] [info] Initializing server...
2025-03-04T10:01:17.104Z [sentry] [error] spawn . EACCES {"context":"connection","stack":"Error: spawn . EACCES\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:01:17.111Z [sentry] [error] spawn . EACCES {"stack":"Error: spawn . EACCES\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:01:17.598Z [sentry] [info] Server transport closed
2025-03-04T10:01:17.598Z [sentry] [info] Client transport closed
2025-03-04T10:01:17.599Z [sentry] [info] 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-03-04T10:01:17.599Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T10:01:19.854Z [sentry] [info] Initializing server...
2025-03-04T10:01:19.916Z [sentry] [error] spawn . EACCES {"context":"connection","stack":"Error: spawn . EACCES\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:01:19.917Z [sentry] [error] spawn . EACCES {"stack":"Error: spawn . EACCES\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:01:19.918Z [sentry] [info] Server transport closed
2025-03-04T10:01:19.918Z [sentry] [info] Client transport closed
2025-03-04T10:01:19.918Z [sentry] [info] 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-03-04T10:01:19.918Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T10:04:49.292Z [sentry] [info] Initializing server...
2025-03-04T10:04:49.311Z [sentry] [error] spawn uvx ENOENT {"context":"connection","stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:04:49.323Z [sentry] [error] spawn uvx ENOENT {"stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:04:49.325Z [sentry] [info] Server transport closed
2025-03-04T10:04:49.326Z [sentry] [info] Client transport closed
2025-03-04T10:04:49.326Z [sentry] [info] 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-03-04T10:04:49.326Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T10:04:50.914Z [sentry] [info] Initializing server...
2025-03-04T10:04:51.002Z [sentry] [error] spawn uvx ENOENT {"context":"connection","stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:04:51.003Z [sentry] [error] spawn uvx ENOENT {"stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:04:51.043Z [sentry] [info] Server transport closed
2025-03-04T10:04:51.043Z [sentry] [info] Client transport closed
2025-03-04T10:04:51.043Z [sentry] [info] 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-03-04T10:04:51.044Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T10:08:20.064Z [sentry] [info] Initializing server...
2025-03-04T10:08:20.078Z [sentry] [error] spawn uvx ENOENT {"context":"connection","stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:08:20.078Z [sentry] [error] spawn uvx ENOENT {"stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:08:20.086Z [sentry] [info] Server transport closed
2025-03-04T10:08:20.086Z [sentry] [info] Client transport closed
2025-03-04T10:08:20.086Z [sentry] [info] 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-03-04T10:08:20.086Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T10:08:24.532Z [sentry] [info] Initializing server...
2025-03-04T10:08:24.569Z [sentry] [error] spawn uvx ENOENT {"context":"connection","stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:08:24.569Z [sentry] [error] spawn uvx ENOENT {"stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:08:24.576Z [sentry] [info] Server transport closed
2025-03-04T10:08:24.576Z [sentry] [info] Client transport closed
2025-03-04T10:08:24.577Z [sentry] [info] 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-03-04T10:08:24.577Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T10:08:43.743Z [sentry] [info] Initializing server...
2025-03-04T10:08:43.766Z [sentry] [error] spawn uvx ENOENT {"context":"connection","stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:08:43.767Z [sentry] [error] spawn uvx ENOENT {"stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:08:43.774Z [sentry] [info] Server transport closed
2025-03-04T10:08:43.774Z [sentry] [info] Client transport closed
2025-03-04T10:08:43.775Z [sentry] [info] 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-03-04T10:08:43.775Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T10:08:45.439Z [sentry] [info] Initializing server...
2025-03-04T10:08:45.480Z [sentry] [error] spawn uvx ENOENT {"context":"connection","stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:08:45.480Z [sentry] [error] spawn uvx ENOENT {"stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:08:45.481Z [sentry] [info] Server transport closed
2025-03-04T10:08:45.481Z [sentry] [info] Client transport closed
2025-03-04T10:08:45.481Z [sentry] [info] 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-03-04T10:08:45.481Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T10:09:08.879Z [sentry] [info] Initializing server...
2025-03-04T10:09:08.886Z [sentry] [error] spawn uvx ENOENT {"context":"connection","stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:09:08.887Z [sentry] [error] spawn uvx ENOENT {"stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:09:08.889Z [sentry] [info] Server transport closed
2025-03-04T10:09:08.889Z [sentry] [info] Client transport closed
2025-03-04T10:09:08.889Z [sentry] [info] 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-03-04T10:09:08.889Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T10:17:06.293Z [sentry] [info] Initializing server...
2025-03-04T10:17:06.310Z [sentry] [error] spawn uvx ENOENT {"context":"connection","stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:17:06.311Z [sentry] [error] spawn uvx ENOENT {"stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:17:06.314Z [sentry] [info] Server transport closed
2025-03-04T10:17:06.314Z [sentry] [info] Client transport closed
2025-03-04T10:17:06.315Z [sentry] [info] 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-03-04T10:17:06.315Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-04T10:17:07.831Z [sentry] [info] Initializing server...
2025-03-04T10:17:07.880Z [sentry] [error] spawn uvx ENOENT {"context":"connection","stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:17:07.880Z [sentry] [error] spawn uvx ENOENT {"stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-04T10:17:07.881Z [sentry] [info] Server transport closed
2025-03-04T10:17:07.881Z [sentry] [info] Client transport closed
2025-03-04T10:17:07.881Z [sentry] [info] 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-03-04T10:17:07.881Z [sentry] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}