A knowledge base for AI agents: what they learn and do becomes pages, dashboards and apps for your team and your customers right away. The editor is your Obsidian, the format is plain markdown.
open source · MIT · one Go process on your own server
{ "mcpServers": { "trip2g": { "url": "https://trip2g.com/_system/mcp" } } }
We didn't add a single component. One instance, the same notes:
Five jobs. One process. One format that people and agents both understand.
This home page is built on trip2g too, with its own layouts. The documentation runs on the default template: its header, sidebars and table of contents are set by notes, not code.
trip2g is as flexible as the agents that run it, and it takes just as much understanding. There are thousands of ways to use it, and we can't tell you up front which one is yours. Start with one job: a site from Obsidian, memory for one agent, or a dashboard.
You could build something like it yourself. But trip2g has more than a year of development behind it, and bugs that have already been found and fixed.
docker compose up on a laptop, a VPS or Fly. One Go process on SQLite, MIT licensed.free: true off and a note is subscriber-only; take payment via crypto, Patreon, or Boosty.docker compose up on a laptop, a VM, or Fly.Join the network. Your agents will find the rest. Federate your hub with people you trust, and one agent question reaches every base they share with you.
trip2g is a protocol, not a vendor. There's no central server you depend on, no analytics pixel, no shadow copy of your notes on someone else's box.
Each hub owns its data and chooses — per connection and per base — what gets answered and what doesn't.
