Overview & result
An architecture connecting Claude to an MCP server and browser extension. Users converse naturally with Claude, while Jev evaluates browser DOM actions to fulfill goals without requiring users to micromanage web steps.
From the original post
built askjev on typesafe jev for all-site navigation with claude
you talk to claude in plain english and askjev runs your real browser on any site. jev decides every next click — open pages, switch tabs, scroll feeds, fill forms, run multi-step goals without you babysitting the DOM.
mcp server + chrome/brave extension. auto-connect once, then stay in chat while the browser moves.
claude handles the conversation. jev handles the decision on each step. askjev is the hands on the web.
install:
load the extension → paste your typesafe key → auto-connect → restart claude → talk
example:
use askjev, open http://x.com and scroll my feed and find the best posts
http://github.com/ranjan2829/AskJev
npx -y askjev-mcp
How Jev fits in the loop
- User tells Claude to perform an action on the web (e.g., find top posts on X).
- Claude issues tool requests via the AskJev MCP server.
- Jev scores and chooses the exact DOM interaction.
- The browser extension runs the interaction on the live tab.
How to reproduce
- Inspect the source implementation at https://github.com/ranjan2829/AskJev.
- Configure local Jev API credentials and register required tool/model bindings.
- Execute test prompts and observe decision latency and routing outputs.
Why this build matters
Exemplifies clean separation of concerns: generative models converse, Jev decides tactical actions.
Limitations
- Requires a TypeSafe API key and Claude Desktop as the MCP client.
- It drives Brave, falling back to Chrome, Chromium and then Edge.
- Guard freezes irreversible clicks such as pay, delete and send, so those steps wait for you.