☰
Grok BotObsidianProductivity & Email2026-10-15

Give a team of Grok Bots one shared Obsidian vault

@fine_grain_sol's diagram 'Grok Bot + Obsidian: Shared Vault', headed Fine Grain Solutions / Lab Notes and marked Live, always on. A top bar reads: Source of truth, GrokBot.md: shared rules / bot roster / vault conventions / maintained by Obsidian Director. A row of four boxes is joined by two-way arrows: Phone + PC (Obsidian apps; reads daily note, writes notes), joined by Obsidian Sync to a home server, always on (Obsidian runs 24/7 + Local REST API plugin; a vault with DailyNotes/ for brief + notes, Unsorted/ as inbox and GrokBot.md as shared rules), joined by Cloudflare Access to a connector, the user-obsidian MCP server (read, search, write, patch, append), joined by MCP tools to the Grok Bot fleet (AI agents, one per job; every bot reads GrokBot.md for shared context). Below, four bot boxes: Chief of Staff, 7:52 AM (writes the morning brief into today's daily note under Agent notes and sends a link to it; an arrow notes it updates the daily note with key info); Obsidian Director, 8:20 AM (owns vault structure, triages Unsorted, keeps #todo tasks tidy, edits GrokBot.md, checks the brief landed); Receptionist (collects 'make a note' asks and files them under Typed notes in today's daily note); and Every bot (reads GrokBot.md for shared rules, writes only under Agent notes in the daily note). A footer lists Obsidian Sync, Local REST API, Cloudflare Access, MCP and NixOS.
Image: @fine_grain_sol

@fine_grain_sol shared how they give a team of Grok Bots one Obsidian vault (Oct 15). Their diagram shows Obsidian running 24/7 on a home server with the Local REST API plugin, synced to their phone and PC with Obsidian Sync. An Obsidian MCP server, reached through Cloudflare Access, lets the bots read, search, write and append notes. Every bot follows one shared rules file, GrokBot.md. A chief of staff bot writes the morning brief into the daily note at 7:52 AM. At 8:20 AM an "Obsidian Director" bot triages the unsorted inbox, keeps to-dos tidy and checks that the brief landed.

Try it yourself

What you get

One Obsidian vault your Grok Bots can read and write, with shared rules for every bot and a morning brief in your daily note.

Tools

  • Grok Bot
  • Obsidian + Obsidian Sync
  • Obsidian Local REST API plugin
  • An Obsidian MCP server
  • Cloudflare Access

Steps

  1. Run Obsidian 24/7 on an always-on home server with the Local REST API plugin, and keep your phone and PC in sync with Obsidian Sync, as their diagram shows.
  2. Connect your Grok Bots to the vault through an Obsidian MCP server reached through Cloudflare Access, so they can read, search, write and append notes.
  3. Keep one shared rules file in the vault that every bot reads first (theirs is GrokBot.md): the rules, the bot roster and the vault conventions.
  4. Give each bot one job and one time, like their 7:52 AM morning brief and 8:20 AM inbox triage, and have bots write only under an Agent notes section of the daily note.

Watch out: This is one person's setup. Bots with write access can change or delete notes, so keep version history or backups, and keep the vault behind access control like the Cloudflare Access step in their diagram.

Proof / source

Self-reported Author's public X post with a diagram of the setup (Oct 15, 2026). The post itself says only that the bot reaches the vault over Obsidian Sync; the server, MCP, Cloudflare Access, GrokBot.md and schedule details are from the diagram. Self-reported.

In their words

Here’s how I give my Grok Bot access to my Obsidian vault over Obsidian Sync

— @fine_grain_sol on X

Read the original source ↗

Added · How we verify · Report an error

Related