Hermes connected to his own tasks after fifteen days
Marc Bara installed Hermes Agent and added more than 50 capabilities in fifteen days, including his own MCP for tasks, projects, clients and invoices. He kept a daily log.
Done with HermesAdvanced
What was done
On 13 September 2026 Marc Bara writes that he installed Hermes Agent from Nous Research 15 days earlier. What started as chat became a layer over work, research, personal organisation and family logistics. He added more than 50 capabilities: email triage, daily briefings, calendar and tasks, meeting notes, research, code, local models, publishing and family errands. He built an MCP server so Hermes can use his system for tasks, projects, clients and invoices. The timeline is at fifteen-days-hermes.pages.dev. The profile says Barcelona.
How it went
He describes it as use over fifteen days, not a demo. The post does not say how many invoices were sent, or how many mistakes the MCP made.
Worth knowing
An MCP for clients and invoices can read more than you expect if the permissions are wide. His log is the source for what was actually added each day.
How to do it
- Connect the agent to one system first, with read access.
- Write down what it was allowed to do each day, so you can see what was added.
- Give write access to invoices only for the step you have read.
Try it with Hermes
Read [task system] with read access. Make a note for today: meetings, what is waiting, and invoices that have not been sent. Do not send an invoice. Do not write to clients.
Replace text in brackets with your own.
Done when. The note has been read, and no invoice or client email has been sent.
Safety rule. Read access first. No message to clients and no invoice without a separate yes.
Read the original
Read the original · Marc Bara on X ·