You probably will need to put the full path to the uv executable in the command field. You can get this by running which uv on MacOS/Linux or where uv on Windows.
Restart the Claude Desktop app. Upon relaunch it should start Honcho and the tools should be available!
Just note that, by default, the MCP server is set up to use the Honcho Demo server, which only persists data for 7 days. If you’re using the hosted version of Honcho, copy the .env.template to a proper .env file and update the URL and API key variables accordingly.
Finally, Claude needs instructions on how to use Honcho. The Desktop app doesn’t allow you to add system prompts directly, but you can create a project and paste these instructions into the “Project Instructions” field.
Be sure to update the <app_name> and <user_name> variables in the instructions.txt file.
Claude should then query for insights before responding and write your messages to storage! If you come up with more creative ways to get Claude to manage its own memory with Honcho, feel free to let us know or make a PR on this repo!