ContextMesh - MCP Server That Gives Claude Your Full Browser and Research History as Live Context

You spent 4 hours reading 30 tabs of research, then open Claude and type from scratch like it never happened. ContextMesh is an MCP server that indexes your browser history, bookmarks, and reading time data and exposes it as live searchable context to Claude in Cursor or Claude Desktop. Claude now knows what you already read.

𝕏 Post Reddit HN

Difficulty

intermediate

What is it?

Developers and researchers using Claude or Cursor constantly re-explain context that already exists in their browser history — the Stack Overflow thread they read at 2am, the GitHub issue they bookmarked last week, the blog post that had the exact answer. ContextMesh solves this by running a local MCP server using the MCP SDK that reads Chrome or Firefox browser history and bookmarks via their SQLite databases, indexes the page content using lightweight local embeddings, and exposes a search_research_history tool to Claude Desktop or Cursor. When Claude needs to understand a problem, it can call this tool and retrieve the exact pages you already read — with timestamps and reading duration as relevance signals. This is purely local, privacy-preserving, and buildable in one weekend with the MCP Python SDK and SQLite.

Why now?

Anthropic's MCP SDK reached stable v1.0 in early 2026, Claude Desktop now has a built-in MCP server configuration UI, and the developer community is actively hunting for MCP tools that solve real daily friction — the distribution channel exists and is hungry.

▸MCP server that exposes a search_research_history tool Claude can call to find relevant pages the user has visited.
▸Semantic search over browser history using local sentence-transformers embeddings — no data leaves the machine.
▸Reading time and recency weighting so recently-read and deeply-read pages rank higher in results.
▸Simple CLI setup wizard that auto-detects Chrome and Firefox history file paths on macOS, Windows, and Linux.

Target Audience

Developers, researchers, and power users who use Claude Desktop or Cursor daily and do heavy browser research — estimated 500k+ Claude Desktop active users as of April 2026.

Example Use Case

A developer asks Claude in Cursor to help debug a Rust async issue. Claude calls search_research_history, finds the three relevant Rust async articles the developer read last Tuesday, and synthesizes advice grounded in exactly the material the developer already studied.

User Stories

▸As a developer using Claude Desktop, I want Claude to search my browser history automatically, so that I do not have to re-paste research context I already read.
▸As a researcher, I want semantic search over my bookmarks and visited pages, so that Claude can find relevant sources I forgot about.
▸As a power user working on multiple machines, I want cloud sync for my history index, so that my context follows me between my laptop and desktop.

Acceptance Criteria

MCP Tool Registration: done when Claude Desktop shows search_research_history as an available tool without errors. Semantic Search: done when a query returns the most relevant visited page within 500ms on a 10k history entry index. Setup Wizard: done when cli_setup.py outputs a valid Claude Desktop config JSON on macOS, Windows, and Linux without manual path editing. Payment Gate: done when purchasing a Lemon Squeezy license unlocks the advanced features flag in the local config.

Is it worth building?

$29 one-time x 500 sales in month 1 via ProductHunt = $14,500. Cloud sync tier $5/month x 200 subscribers = $1k MRR by month 3. Realistic for a niche dev tool with strong word-of-mouth.

Unit Economics

CAC: $0 via GitHub and community posts. LTV: $29 one-time plus $60 cloud sync (12 months at $5/month) = $89 blended. Payback: immediate. Gross margin: 96%.

Business Model

One-time purchase — $29 lifetime license via Gumroad or Lemon Squeezy. Optional $5/month cloud sync tier for cross-device history.

Monetization Path

One-time purchase removes rate limits. Cloud sync upsell converts power users who work across multiple machines.

Revenue Timeline

First dollar: day 3 via Gumroad link in GitHub README. $5k total revenue: week 3 via ProductHunt. $1k MRR: month 3 via cloud sync tier.

Estimated Monthly Cost

Lemon Squeezy fees: ~$30 on $1k revenue, GitHub free, no hosting required for local server. Total ongoing: under $30/month.

Profit Potential

Modest but fast — $10k–$20k one-time revenue in first 2 months from ProductHunt launch. MRR grows slowly via cloud sync.

Scalability

Medium — the local-first model limits scale but maximizes privacy. Cloud sync tier is the expansion path.

Success Metrics

500 GitHub stars in week 1. 200 paid licenses in month 1. 50 cloud sync subscribers by month 2.

Launch & Validation Plan

Post a 60-second demo GIF on Twitter and r/ClaudeAI showing Claude finding a browser history article mid-conversation, collect 100 GitHub stars before charging anything.

Customer Acquisition Strategy

First customer: post demo GIF on r/ClaudeAI and r/LocalLLaMA showing the exact Claude Desktop config — developer communities will self-serve from a README faster than any landing page. Ongoing: GitHub open-source the core with paid license for advanced features, ProductHunt launch, Hacker News Show HN post.

What's the competition?

Competition Level

Low

What's the roadmap?

Feature Roadmap

V1 (launch): Chrome and Firefox history indexing, semantic search MCP tool, CLI setup wizard. V2 (month 2-3): cloud sync cross-device, Safari support, bookmark tagging. V3 (month 4+): auto-summarize visited pages, Cursor IDE plugin, team shared research index.

Milestone Plan

Phase 1 (Week 1): MCP server with Chrome history search working in Claude Desktop locally. Phase 2 (Week 2): Firefox support, setup wizard, README, Lemon Squeezy link, GitHub public launch. Phase 3 (Month 2): 200 paid licenses, ProductHunt launch, cloud sync beta.

How do you build it?

Tech Stack

MCP Python SDK for server, SQLite for reading Chrome and Firefox history databases, sentence-transformers for local embedding and semantic search, FastAPI as optional local HTTP bridge, Claude Desktop as MCP host — build entirely with Cursor for backend Python logic.

Suggested Frameworks

MCP Python SDK, sentence-transformers, SQLite3

Time to Ship

1 week

Required Skills

MCP Python SDK server development, SQLite database reading, sentence-transformers local embedding, Chrome and Firefox history file path handling across OS platforms.

Resources

Anthropic MCP Python SDK docs, Chrome history SQLite schema reference, sentence-transformers quickstart, Lemon Squeezy API docs.

MVP Scope

mcp_server.py with search_research_history tool, chrome_history_reader.py, firefox_history_reader.py, local_embedder.py using sentence-transformers, cli_setup.py for path auto-detection, README with Claude Desktop config snippet, Lemon Squeezy payment link.

Core User Journey

Clone repo -> run setup wizard -> add MCP config to Claude Desktop -> ask Claude a question -> Claude finds your browser research automatically.

Architecture Pattern

Claude Desktop calls search_research_history tool -> MCP server reads Chrome SQLite history DB -> sentence-transformers encodes query -> cosine similarity search over pre-indexed page embeddings -> top 5 results returned as tool response to Claude.

Data Model

BrowserPage has URL, title, visit timestamp, total reading time, and local embedding vector. EmbeddingIndex stores all page vectors for cosine similarity search. UserConfig stores history file paths and indexing preferences.

Integration Points

MCP Python SDK for Claude Desktop tool registration, Chrome and Firefox SQLite history databases for data source, sentence-transformers for local embeddings, Lemon Squeezy for payment links.

V1 Scope Boundaries

V1 excludes: cloud sync, Safari support, reading content extraction beyond page titles and URLs, team sharing, mobile support.

Success Definition

A developer installs ContextMesh in under 5 minutes, asks Claude a coding question, and Claude surfaces a relevant page from their browser history they had forgotten about — without any manual context pasting.

Challenges

Distribution is the core challenge — MCP tools require Claude Desktop or Cursor, which limits the audience to power users willing to configure a local server, meaning ProductHunt and developer Twitter are the only real acquisition channels.

Avoid These Pitfalls

Do not build a cloud sync feature before validating that users will pay for the local version — cloud sync adds auth, GDPR, and server costs that kill the solo-founder model. Do not index all history blindly — users with 50k history entries will see slow embedding generation on first run, which feels broken. Finding first 10 paying customers requires active community posting, not passive GitHub SEO.

Security Requirements

No auth required for local-only tier — all data stays on device. Lemon Squeezy license key validation via local config file. Cloud sync tier uses Supabase Auth with Google OAuth and encrypted history vectors in transit.

Infrastructure Plan

No hosting required for local server. Lemon Squeezy for payments. GitHub for distribution. Cloud sync tier: Supabase Postgres on free tier initially. Sentry optional for crash reporting in future versions.

Performance Targets

10k history entries indexed in under 60 seconds on first run. Semantic search returns results in under 500ms. MCP tool call latency under 1 second end-to-end.

Go-Live Checklist

☐MCP server tested in Claude Desktop on macOS and Windows
☐Payment link tested end-to-end on Lemon Squeezy
☐README setup guide validated by 3 non-technical beta testers
☐GitHub repo public with MIT license for core
☐Privacy policy page live explaining local-only data handling
☐Demo GIF recorded and ready
☐r/ClaudeAI post drafted
☐Hacker News Show HN post drafted
☐Rollback to previous version documented via git tags.

How to build it, step by step

1. Install MCP Python SDK and scaffold a basic MCP server with mcp_server.py. 2. Write chrome_history_reader.py that reads the Chrome SQLite history database and returns recent visits with timestamps and visit counts. 3. Write firefox_history_reader.py with equivalent logic for Firefox places.sqlite. 4. Install sentence-transformers and write local_embedder.py that embeds page titles and URLs into vectors stored as a local numpy file. 5. Implement the search_research_history MCP tool that takes a query string, embeds it, and returns top 5 cosine-similar pages. 6. Write cli_setup.py that auto-detects Chrome and Firefox history paths on macOS, Windows, and Linux and outputs the Claude Desktop config JSON snippet. 7. Add reading time weighting so pages with longer visit duration rank higher in results. 8. Write a comprehensive README with a 30-second setup guide and Claude Desktop config snippet. 9. Set up Lemon Squeezy product for $29 lifetime license and add payment link to README. 10. Post demo GIF to r/ClaudeAI, r/LocalLLaMA, and Hacker News Show HN.

Generated

April 8, 2026

Model

claude-sonnet-4-6

← Back to All Ideas