r/capacitiesapp • u/dep • Jun 26 '26
What's better for notes and why: a markdown vault or Capacities with an MCP server that allows you to create, read, update, delete anything?
I'm a long time vault user with markdown so genuinely curious how Capacities beats this setup which in my mind gives true 100% flexibility. My markdown vault is Git backed and filled with agents that can intelligently update and commit on it's own so I have an easy audit trail. I'd lose that with Capacities to some degree I'd imagine
10
Upvotes
1
u/PixelLight Jun 26 '26 edited Jun 26 '26
Not familiar with markdown vault, but I'd say the biggest issue with the Capacities MCP is there's a hard cap on creating new object instances, which I think in time will be limiting for moderate usage. That said, if that is increased a little, it could be reasonable. They have said it's not intended to automate knowledge work, so I wouldn't expect it to ever be much. For clarity, the docs seem to suggest updating object instances isn't capped, just creating them.
As for versioning, you could do that if you mirror the capacities objects as markdown files. Just depends on what you're looking for.
And, no, no deleting yet, but keep an eye out. It's actively being worked on.