Your files
The board runs on a folder of markdown. Point it at a new folder or an Obsidian vault — that folder is the source of truth, no database in between.
How IntrynSync connects
Open by design — starting with the files you own.
IntrynSync doesn't lock your goals in a database. Everything is plain markdown in a folder on your machine, which means it already connects to the tools that read files, to AI agents through MCP, and to your phone through open notification channels. Richer app connectors are what comes next.
Connected today
AI agents (MCP)
A built-in MCP server lets Claude and other agents read and work your board under your intrynsync.md rules. They propose, you approve.
Notifications out
A daily digest and agent-proposal pings reach your phone via ntfy, any webhook (Slack, Discord), or a Telegram bot you can also chat with.
HTTP API
A token-protected API for cron jobs, n8n, and scripts — so anything that speaks HTTP can add goals or read your board.
On the roadmap
Each connector follows the same rule: it reads your intrynsync.md and turns outside activity into cards you approve — never actions taken behind your back.
Turn the messages that deserve follow-up into cards — your rules file decides what's card-worthy.
Calendar
Surface commitments as dated goals, and reflect goal due dates back onto your calendar.
Notes & wikis
Logseq, SilverBullet, and other markdown tools already work today; deeper two-way sync is planned.
CRM & work tools
For the managed workspace tier — pull client and project context into a governed board.