Fair point. The MCP client package is open source and on npm (contextforge-mcp). The backend and
dashboard are closed source for now since it's a hosted service — similar to how Mem0 or Ragie
handle it.
That said, I hear you. It's something I'm considering as the project matures. Indexing is hybrid — pgvector for semantic search, full-text search for exact matches.
For lifecycle, we keep it simple: users organize knowledge into "spaces" per project. Git spaces
auto-sync commits/PRs. No automatic eviction — snapshots let you save/restore state.
Cross-conversation context: we don't carry over conversation state. Each session, Claude just
queries stored knowledge for what's relevant. No identity leaking between sessions, just
searchable context on demand.
Curious — have you run into specific challenges with memory lifecycle in your own work? It's an MCP server that gives Claude persistent memory — semantic search, GitHub integration, task
tracking, and team collaboration. There's a web dashboard to manage everything.
Works with Claude Code, Cursor, Windsurf, and any MCP client.
Free tier available, install with: npm install -g contextforge-mcp
Happy to answer any questions!