whistler-mcp 1.0.0 → 1.0.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +14 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -31,7 +31,20 @@ To use this server locally with Claude Desktop, add the following to your `claud
|
|
|
31
31
|
|
|
32
32
|
*Note: You do not need to provide a JWT token in the config. Try asking Claude a Whistler-related question, and it will prompt you to securely log in directly within the chat interface!*
|
|
33
33
|
|
|
34
|
+
## Local Testing & Debugging
|
|
35
|
+
|
|
36
|
+
If you want to test the server without an AI client, you can use the official MCP Inspector:
|
|
37
|
+
|
|
38
|
+
```bash
|
|
39
|
+
npx -y @modelcontextprotocol/inspector npx -y whistler-mcp
|
|
40
|
+
```
|
|
41
|
+
|
|
42
|
+
This will open a local web debugger at `http://localhost:5173` where you can manually run and inspect each tool.
|
|
43
|
+
|
|
44
|
+
## Distribution
|
|
45
|
+
This folder is a completely standalone Node.js package. It has its own internal dependencies and maps to the Whistler API over HTTP. You can safely move this folder anywhere on your computer (or even to a brand new repository) and it will continue to function perfectly as long as your `API_URL` is accessible.
|
|
46
|
+
|
|
34
47
|
## Local Development
|
|
35
48
|
1. Clone the repository.
|
|
36
|
-
2. Run `npm install` inside the `/mcp` folder.
|
|
49
|
+
2. Run `npm install` inside the `/whistler-mcp` folder.
|
|
37
50
|
3. Test locally using the `node server.js` command.
|