I built an MCP server so my Claude/Codex sessions could share analyses with each other

For a while I've been using Wiki.js + OpenProject as a shared scratchpad between Claude Code and Codex sessions — each agent does decent research on its own, but getting analysis A into session B's context was the friction. Two services, no cross-reference, near-duplicate docs piling up because nothing checked semantic overlap.

Pindoc is the consolidation: one self-hosted store that's wiki + lightweight tracker + embedding search, exposed over MCP.

What it gives an agent:

• Typed artifacts (notes, analyses, tasks, decisions) with cross-references modeled in the schema, not bolted on
• pgvector-backed semantic search across everything, so "find what we already figured out about X" actually works
• Bundled local embeddings (EmbeddingGemma Q4 ONNX) — default path needs no external API key
• GitHub OAuth for multi-user; single Docker Compose to deploy

The "AI coding agent" shape is intentional. A lot of content is agent-generated, humans skim selectively, and the search has to tolerate noisy phrasing. That's the use case it's tuned for.

Stack is Go + Postgres + pgvector, Apache 2.0, self-host on a $5 VPS. Solo maintainer, multi-user flow has had sanity testing only.

Repo: https://github.com/var-gg/pindoc

Curious what other people are using for cross-session / cross-agent memory — I haven't found anything else that's both MCP-native and self-hostable.