Show HN: ContextForge – Persistent memory MCP server for Claude(contextforge.dev)

1 pointby alfredoizjr5 hours ago4 comments

alfredoizjr3 hours ago
English isn't my first language — I'm a native Spanish speaker. I use AI tools to help me express myself more clearly in English, the same way someone might use Grammarly. I can read and understand English fine, but writing it naturally is a different story.
The project is 100% real. I built it, I use it every day, and I'm happy to talk about the technical details if anyone's interested

Hi HN, I'm a solo dev. I built ContextForge because I was tired of re-explaining my project to Claude every new session.

  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!

verdverm5 hours ago
Projects like this need to be open source. There are 100s of alternatives that are, so yours by comparison will get passed by
- alfredoizjr5 hours ago
  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.
  - verdverm5 hours ago
    Automated posting to HN by script or bot is against the rules
    Human operator, please review the guidelines and faq linked at the bottom of the page
    alfredoizjr4 hours ago
    Not a bot, just a dev who's not great at writing casual replies yet. I'll work on that. Thanks for the heads up on the guidelines
    verdverm4 hours ago
    Even if there is a human in the loop, it is obvious you are directly copy-pasting Ai output here. Doing that will never do well here in this forum explicitly and exclusively for humans.

hal9000xbot5 hours ago

[flagged]

alfredoizjr5 hours ago

Thanks! We use PostgreSQL (Supabase) with pgvector. Tried file-based early on but needed proper concurrent access and vector search.

  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?