You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#### Run [MCP server inspector](https://github.com/modelcontextprotocol/inspector) for debugging
78
80
Caveat: make sure to keep only a single inspector tab open at all times, until [this inspector bug](https://github.com/modelcontextprotocol/inspector/issues/302) is fixed.
79
81
```shell
80
82
# Run this and follow the instructions to view the inspector
81
-
bun inspect:bun
83
+
npm run inspect:node
82
84
```
83
85
84
86
#### Tail logs
85
87
Our local MCP server uses STDIO transport, therefore logs must go to a file. This may come in handy when debugging.
86
88
```shell
87
-
tail -f log/development.log |bun pino-pretty
89
+
tail -f log/development.log |npx pino-pretty
88
90
```
89
91
You can also optionally capture STDIO messages in the log file by setting `LOG_STDIO=1` when running the server.
90
92
If you're debugging a containerized server, you'd likely want to mount a dir at `/app/log` to be able to access the logs it generates.
@@ -97,7 +99,7 @@ bin/build_image
97
99
98
100
You can now run the container with the MCP inspector for debugging:
99
101
```shell
100
-
bun inspect:docker
102
+
npm run inspect:docker
101
103
```
102
104
103
105
Or run the container within Claude Desktop, configured with your `.env.local` file in the project.
0 commit comments