Skip to content
Contextberg logo

Contextberg

Routes code context and memory to Claude, Code, Cursor, or other LLMs via MCP protocol.

At a glance
Price
Price not read
Use
Use not read yet
Activity
Activity not read yet
Company
founding year not on record
Runs as
API
Alternatives in Meetingsby use, among tools still maintained
  • CluegentProvides real-time answers and coding help during interviews via a private desktop overlay that remains invisible during screen sharing.

    EmergingMaintained

    ≈ 30 visits/mo
  • FlowConverts speech to polished text in any application across devices.

    Widely usedActively maintained

    ≈ 54.8k visits/mo
  • OtterTranscribes meetings, generates summaries and action items, syncs insights to CRM and connected apps.

    Widely used

    ≈ 340k visits/mo
  • KrispRemoves background noise, transcribes meetings, generates summaries, and converts accents in real time.

    Widely used

    ≈ 120k visits/mo
  • Read AIRecords and transcribes meetings, generates summaries and action items, searches across conversations.

    Widely used

    ≈ 162k visits/mo
  • FirefliesTranscribes, summarizes, and analyzes meeting conversations across multiple platforms and languages.

    Widely used

    ≈ 67.2k visits/mo

All Meetings tools →

Questions this page answers
  • What is Contextberg?

    Routes code context and memory to Claude, Code, Cursor, or other LLMs via MCP protocol.

  • What are alternatives to Contextberg?

    In Meetings, by use: Cluegent, Flow, Otter, Krisp, Read AI, Fireflies.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one row at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.