Very cool, I've been interested in getting an e-ink notebook for a while now, so would definitely be interested in your experience once you get it, especially if you integrate it into a workflow with silverbullet.
If you're willing, I'd definitely be up for reviewing a PR with mcp support and some of your other changes. I haven't looked too closely at the changes yet, but proper mcp support has been on my wishlist for a while now.
Created an “initial” PR at Migrate build to Node.js/npm + bug fixes (Mistral, security, agent panel) by ddulic · Pull Request #104 · justyns/silverbullet-ai · GitHub
I had issues with the deno build, so had to migrate to using node based on Migration from Deno to Node.js
This is yet to include the MCP client, which I managed to get working 
I have left the version as 0.6.5, but you might want to bump it to 0.7.0 given the migration.
Depending on the MCP server, sending over all the RAG context might not make it not work as expected, so I added extra flags to disable RAG on a per-agent basis and there are some fixes in there to fix the chat panel from not refreshing the state.
A few fixes in there for the build system, which makes it easier for forks to test changes by adding their repo as a library to SilverBullet.
I use Mistral, so there are a few fixes related to that as well.
Not sure how best to test this, fork the branch to another temporary repo? Is it possible in SilverBullet Library Manager to pull from a branch? If so, might be worth adding this to the contribution documentation.
Disclosure that this was heavily written by AI (I don’t know a lick of ts 
) same for cherry-picking the changes to push to your upstream, as my repo is now very different (hoping to get it synced).
We can continue the chat on the PR.
Just released 0.8.0 today with MCP client (header-only auth, no oauth or stdio) support. Also totally forgot to post about 0.7.x that had some of @Rockeer 's fixes in it.
If anyone tries the mcp support, let me know if you run into any issues with it.
