trip2g
About
Self-hosted MCP server over your markdown notes: hybrid search and note reading with sourced answers. The same vault is also a website, so the agent's memory is readable, git-diffable markdown. Single Go binary + SQLite, MIT.
Details
- Author
- trip2g
- Categories
- Database, Other, Productivity, Developer Tools
Jump to
Setup
Install trip2g in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/trip2g/trip2g
Follow the installation instructions in the repository README, then restart your MCP client.
Publish your Obsidian vault as a website. Self-hosted MCP memory for AI agents.
Write in Obsidian, press Sync, your notes are live. The same self-hosted hub serves readers a website and serves agents an MCP endpoint, publishes to Telegram, and gates paid content. Under the hood it is a Markdown Operating System: every note is a file, and one note is both a web page for a human and a tool call for an agent.
- Your notes work twice.One markdown file renders as a page for readers and answerssearch/note_htmlcalls from any MCP client. No export step, no copy of your knowledge locked in a vector store you can't read.
- Your data stays yours.Plain markdown, a git-cloneable vault, every edit a readable diff. No SaaS in the middle, and you can move out any time withgit clone.
- One process to run.A single Go binary on SQLite. It starts the same on a laptop, a small VM, or a container. MIT licensed.
See it work in 30 seconds.Add the public knowledge hub to any MCP client and ask it a question. It searches all connected bases and answers with sources:
{ "mcpServers": { "trip2g": { "url": "https://trip2g.com/_system/mcp" } } }
git clone https://github.com/trip2g/trip2g && cd trip2g/quickstart docker compose up
Prefer no terminal? Get afree cloud instance. All the options (single binary, Docker Compose behind TLS, fly.io) are in theself-host guide.
Docs·Getting started·MCP tools·Self-host·Contributing
Unix made everything a file. trip2g makes everything a note.
One global namespace, path-addressed, shared by humans and agents. A note is a markdown file: the frontmatter is its metadata, the body is its content. The same note is served as a web page (the display server) and over MCP (the agent's syscall surface), and every edit is snapshotted intonote_versionsand mirrored to git. So the history is a readable diff, not a binary blob.
human A human B human C │ │ │ ▼ ▼ ▼ agent A agent B agent C │ │ │ ▼ ▼ ▼ ┌────────┐ MCP ┌────────┐ MCP ┌────────┐ │ hub A │ ◄───► │ hub B │ ◄───► │ hub C │ └────────┘ └────────┘ └────────┘ ▲ ▲ ▲ └─── humans browse · agents query ──┘
The same hub serves the human (a website with subscriptions, RSS, Telegram) and the agent (MCP). Your data stays in plain markdown you can move out any time.
trip2g borrows the operating-system vocabulary because the primitives line up. Each row is tagged by how real it is:shippedis running code onmain,branchis running code onfeat/agent-runtime,plannedis a design doc.
Built into every hub. An agent never touches the database directly. It calls a small set oftools over MCP, and access is scoped to the caller's subscription.
Custom tools can be defined in note frontmatter (mcp_method:).
graph LR O[Obsidian vault] --> H[your hub] T[Telegram] --> H H <-->|MCP federation| H2[peer hub] H2 --> B[their bases] H -->|/_system/mcp| A[agent] H2 -->|/_system/mcp| A
Each hub is itself a Markdown OS, so the network is a mesh between operating systems, the way the internet is a network between computers. The rows below are common shapes, not the only ones. The protocol does not assume a topology, so you can build any of them.
Process dispatch & scheduler: webhook agents
The kernel-side mechanism that runs an agent. Shipped onmain.
- Change webhooks.A note create/update/remove POSTs to an agent, and the agent writes notes back via the API. Glob filtering picks which notes fire it, HMAC signs the delivery, andmax_depthstops recursion.
- Cron webhooks.Run an agent on a schedule (0 9 ). Anext_run_atcolumn plus a per-minute system cron drive it, and goqite worker pools give per-queue concurrency and priority. Sync or async, with optional instruction context.
The agent itself can live anywhere. These webhooks just deliver the event and accept note writes back.
In development onfeat/agent-runtime, not yet onmain.
The core idea: a note edit spawns a scoped, server-side agent run. Unlike a local editor or a static builder, the agent runs on the hub, scoped to the note's glob patterns, not on your laptop.
An agent is a note. Its frontmatter is the config:model,tools,read_patterns/write_patterns,trigger_on,for_each,max_depth,timeout_seconds. Its body is the instruction, a Jet template that can reference the changed note(s). Afleetdaemon watches an agents folder, parses each role note, and registers it as a change webhook pointed back at itself. Drop a note to install an agent, remove the note to uninstall it.
graph LR E[note edited] --> W[change webhook fires] W --> F[fleet /deliver] F --> R[agentruntime loop] R -->|search / read_note| KB[(knowledge base)] R -->|write_note / patch_note| KB KB -.re-trigger.-> E
When a watched note changes, trip2g fires the webhook and the fleet runs a scoped loop (agentruntime): the model gets the instruction plus in-scope context and callssearch/read_note/write_note/patch_note. Reads and writes are enforced against the role's glob patterns, a non-overridable token-and-step cap limits the run, andmax_depthbreaks re-trigger loops. trip2g stays a plain event source. The instruction, scope, and triggers all live in the note.
The plumbing this rides on (change/cron webhooks, scoped tokens, delivery jobs) is shipped onmain. The in-note LLM executor (agentruntime) and the fleet reconciler (internal/fleet,cmd/fleet) are whatfeat/agent-runtimeadds.
The kanban layout (docs/_layouts/kanban.html) and the standalonekanban_templateship onmain. Wiring a board to the fleet is part offeat/agent-runtime.
A. Default template(no code, frontmatter only). Compose pages from widgets and content blocks:
--- header: "[[Navigation]]" left_sidebar: [TOC, inlinks] content: [selfcontent, magazine] magazine_include_files: "blog//.md" footer: "[[Footer]]" ---
Rendered through quicktemplate. Notes can also render as HTML, JSON, or RSS viacontent_typefrontmatter.
B.Custom Jet templates(full control). Drop your own.htmlfiles into a layouts folder and switch vialayout: path/to/template. Templates get the markdown AST, so you can iterate sections, render specific parts, and customize down to HTML. Built on theJet template engine.
On top of either path sit renderer extensions that the backend loads per note, only when a note asks for them:mermaiddiagrams and adatachartwidget that turns a referenced CSV into a chart (via ECharts). A note declares what it needs, and the page ships only those scripts.
The same notes publish to a Telegram channel, on a schedule or instantly. trip2g keeps the links intact: a wikilink to a note that has its own post points at that post, and a note that is not posted yet falls back to its page on the website, so nothing dangles. Edit the note and re-sync, and the channel post updates itself.Full guide →
A note can collect input, not just show it. Put aform:block in the frontmatter and trip2g renders a form on the page, accepts submissions through the GraphQL API, and stores each one against the note.
--- title: Say hello form: fields: - name: email type: email required: true - name: message type: text max_length: 2000 ---
Field types and validators live in the frontmatter, Cloudflare Turnstile guards public forms by default, andcan_submitlimits who may post. Submissions land in the admin panel and a GraphQL API, and each one emails the vault admins. Define a spec once and reuse it withform_ref:, or attach a form to a whole folder with frontmatter patches. In OS terms, this is the note's standard input.Full guide →
trip2g serves the whole knowledge base over git Smart HTTP at/_system/git. Clone it, pull it, and push to it like any repository. The database is canonical; the git tree is not a checkout sitting on disk,gitapimaterializes it on demand at the moment you interact with the endpoint, and a push is applied back into the notes. So you can back up the vault withgit clone(the full history comes down with it) and script changes with a commit instead of the API.
Group notes into paid products withsubgraph paywalls, while free notes stay public. Payments go through crypto (NowPayments), Patreon, or Boosty.
cd quickstart && docker compose up
trip2g runs as one process on SQLite, with no database server to stand up, so a hub starts the same on a laptop, a small VM, or a container. When you need high availability, add read-only replicas that scale reads horizontally while a single leader takes the writes (on thefeat/read-replicabranch).
The OS framing is adapted fromMarkdown as an Operating Systemand from Unix'severything is a file. Three lines we took to heart:
- Markdown is the universal substrate.One file every tool and every model already reads; render the website, the feed, and the git history from it.
- The file is the interface between processes.An agent writing a note fires the next agent, so coordination needs no separate queue API.
- Human-readable diffs are the audit log.**Every edit is anote_versionand a commit you can read in five seconds and revert.
An MCP server that equips your AI coding assistant with live, verified Android knowledge — so it builds from official sources, not from memory.
Allows AI assistants to interact with the GitHub API for repository management, code collaboration, and other development tasks.
Generat 22 types mermaid architecture diagrams with natural language description
Access and analyze Overleaf projects and LaTeX files through Git integration.
Provides database access, supporting SQLite, SQL Server, PostgreSQL, and MySQL.
Creates commit messages from staged files in a local git repository.
Anchor is local repo and org memory for AI coding agents. It indexes GitHub PR history, current code, tests, regressions, architecture, and cross-repo impact locally, then exposes concise cited context through MCP and CLI workflows. Local-first. Read-only GitHub access. No CLI telemetry. No SaaS. No remote LLM calls.
An MCP server for interacting with the AtomGit API for version control and code hosting.
Design system MCP server — query tokens, components, icons, and WCAG contrast data from Git-backed design systems.
Paid remote MCP for AI browser purchase approval checks, spend thresholds, merchant evidence, risk notes, and audit receipts.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
