I’ve tried to set it up, and well, I’ve run into the early adopters’ problems 
BTWm this isn’t anything you did wrong, or a reflection on the quality of the tool. It’s just the state of the very early tooling in general
Runing in WSL2 on Windows:
-
npx -y @smithery/cli@latest install @bradleygolden/hexdocs-mcp --client cursordoes nothing even though it says it did something -
setting config by default fails with then fais to start the client with
[info] -mcp: Starting new stdio process with command: npx -y hexdocs-mcp@0.4.1 [error] -mcp: Client error for command spawn npx ENOENT [error] -mcp: Error in MCP: spawn npx ENOENT [info] -mcp: Client closed for command [error] -mcp: Error in MCP: Client closed [error] -mcp: Failed to reload client: MCP error -32000: Connection closed [info] -mcp: Handling ListOfferings action [error] -mcp: No server info found [info] -mcp: Handling ReloadClient action [info] -mcp: Starting new stdio process with command: npx -y hexdocs-mcp@0.4.1Running
npx -y hexdocs-mcp@0.4.1in the terminal works just fine
Though I really want this to work 
Sorry for the abundance of smileys. View this as my eye twitching.
