MCP.Market

Dejo MCP server

by dejohq·io.github.dejohq/dejo-mcp·v0.2.0·6 stars

A browser your AI agent remembers. Learn a site once, replay it in one call, zero model calls.

A91/100grade A
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

6 stars384 downloads/wk

Reviews

Write one

Nobody has reviewed Dejo yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Dejo tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Dejo compares

Against every graded Scraping and browsing MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 80% of 807 Scraping and browsing servers
GitHub stars
6
more than 75% of 553 Scraping and browsing servers
Downloads a week
384
more than 82% of 295 Scraping and browsing servers with a package

Install Dejo in Claude Code, Cursor or VS Code

claude mcp add dejo-mcp -- uvx dejo-mcp
Add to Cursor

What the publisher says

From the Dejo repository's README, as published. We do not edit it. Read it on GitHub

Dejo

A browser your AI agent remembers. It learns a website once. Every run after that is one tool call, with zero model calls.

Website · Install · Benchmark · Tools · What it can do · Contributing

Your AI can use websites. But it forgets how, every single time. Dejo makes it remember.

Dejo gives Claude Code, Codex, Cursor or any MCP client a browser with a memory. Your agent walks a website once: signing in, clicking, reading. Dejo writes down the route. Every run after that follows the route instead: one tool call, no page reading, zero model calls. When the site changes, Dejo repairs the one step that moved and keeps the rest.

Install

Python 3.11 or newer.

pip install dejo-mcp
playwright install chromium      # the browser, a separate download of about 150 MB

Then connect it to your agent:

Dejo is one stdio server with no arguments, so any agent that can run an MCP server can use it.

No API key, no account. Dejo never calls a model. Your agent does the thinking, and the memory is a local file on your machine.

Check the install at any time. It names anything missing and the command that fixes it:

dejo doctor

Quick start

Ask your agent for something on a website, in your own words:

Go to github.com/microsoft/playwright and tell me how many open issues it has.

The first time, your agent learns it: Dejo opens the page and shows it, one line per control, and your agent sends the steps back in one call (click link "Issues", then read ... as open issues). The read is what Dejo saves. Ask again tomorrow, in a brand-new chat, and it is one call:

done: "count open issues" on github.com (profile default), 2 steps replayed in 1391 ms, no page reading.
open issues = 117
next: report the answer exactly as read and stop. Every step was checked as it ran.

Prefer a terminal? Everything works without an MCP client:

dejo sites                                            # what it remembers
dejo run "count open issues" --site github.com        # replay, no model involved
dejo run "count open issues" --site github.com --json # one JSON line, for cron and scripts
dejo show github.com                                  # the route, step by step
dejo forget --site github.com                         # make it forget

How it works

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Dejo: common questions

Is Dejo MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the Dejo safety report
How do I install Dejo?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Dejo need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Dejo maintained?
The last commit was 2 days ago (2026-10-23). The latest release is v0.2.0.
What can I use instead of Dejo?
Servers from other publishers that do the same job: Tap MCP server, Unbrowse MCP server and Safari MCP server. Compare all Dejo alternatives.
How does Dejo compare with other Scraping and browsing MCP servers?
safety score 91/100 (higher than 80% of 807 Scraping and browsing servers); github stars 6 (more than 75% of 553 Scraping and browsing servers); downloads a week 384 (more than 82% of 295 Scraping and browsing servers with a package). Full comparison.

Alternatives to Dejo

Same job from other publishers: the closest match first, then the best rated.

All Dejo alternatives →
  • Tap
    Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.
    B
  • Unbrowse
    Websites as APIs: read pages, run site tasks via learned APIs, cloud browser with saved logins.
    A
  • Safari
    Native Safari browser automation for AI agents — 98 tools, zero Chrome overhead.
    C
  • FableCut
    Zero-dependency browser video editor AI agents drive via a JSON timeline over MCP; ffmpeg export.
    A
  • Cdpilot
    Zero-dependency browser automation over raw CDP — no Puppeteer, Playwright, or Selenium.
    B