Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Let AI agents use any website you're logged in to. Sessions stay encrypted on your machine.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Descargar el archivo .mcpb del creador
El enlace lleva al archivo del propio creador; no lo alojamos ni lo reempaquetamos. Abre el archivo y Claude Desktop lo instalará.
Ejecuta esto en tu terminal
Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub romaklym, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.4.0) llegó al registro hace 4 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas MCPB en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Dechonet MCP
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
30 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Let your AI agent use any website you're logged in to.
Log in once. Your session stays encrypted on your machine. Claude, Codex, Cursor and any MCP client can then browse, click, type and read for you.
Quick start · Connect your client · Tools · Security · FAQ
You: Check my LinkedIn messages and summarize anything from recruiters.
Agent: open_session("linkedin") → click "Messaging" → read_text … You have 3 recruiter messages. The most recent is from Dana at Acme, about a Senior QA role …
Most sites have no API, or one that can't do what you need. Assertify gives your agent a real browser that is already logged in as you, without ever handing it your password.
navigator.webdriver flag.[e12] button "Send"), not raw HTML.flowchart LR
U(["👤 You"]) -- "log in once per account" --> L["Login window real browser, 2FA works "] L -- "named by email" --> V K[["🔑 OS keychain macOS · Windows · Linux "]] -. key .-> V
subgraph V["🔒 Encrypted vault"] direction LR P1["personal@gmail.com"] P2["work@gmail.com"] P3["shop@gmail.com"] P4["you@company.com LinkedIn "] end
V -- decrypt --> S["⚙️ Assertify server asks before send · buy · delete "] A(["🤖 AI agent"]) <-- "pick one account or all at once" --> S S -- "side by side" --> B
subgraph B["Headless browsers, logged in"] direction LR H1["Gmail · personal@"] H2["Gmail · work@"] H3["Gmail · shop@"] end
classDef person fill:#eef2ff,stroke:#6366f1,color:#1e1b4b classDef safe fill:#ecfdf5,stroke:#10b981,color:#064e3b classDef live fill:#fff7ed,stroke:#f97316,color:#7c2d12 class U,A,L,S person class P1,P2,P3,P4,K safe class H1,H2,H3 live style V fill:#f0fdf4,stroke:#10b981 style B fill:#fffbeb,stroke:#f59e0b
Log in once per account; each one is saved under its email. Your agent then opens one account by name, or every account for a site at once, each in its own logged-in browser. Everything above runs on your computer, on macOS, Windows or Linux.
You need uv:
curl -LsSf https://astral.sh/uv/install.sh | shpowershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"git clone https://github.com/romaklym/assertify.git
cd assertify uv sync uv run assertify setup
setup downloads the browser (Chromium, about 300 MB, once), checks your keychain, and prints the exact command to connect your AI client. If you skip it, Assertify downloads the browser on first use, or falls back to your installed Chrome or Edge.
Linux notes
sudo uv run playwright install-deps chromium.ASSERTIFY_PASSPHRASE instead.~/.assertify-mcp over (with the same passphrase), or use ssh -X.Then save your first login:
uv run assertify login github https://github.com/login
A browser window opens. Sign in, then close the window (or press Enter in the terminal). Done. Your agent can now use GitHub as you.
[!TIP]
You can also just ask your agent: *"log me in to Notion"*. It calls
start_login, the window opens, and the session saves when you close it.
Replace /path/to/assertify with where you cloned it (assertify setup prints the exact line for you).
Claude Code
claude mcp add -s user assertify -- uv --directory /path/to/assertify run assertify serve
Claude Desktop
Easiest: download assertify.mcpb and double-click it. Claude Desktop installs it with its icon and handles Python for you.
Or add it to claude_desktop_config.json by hand:
{
"mcpServers": { "assertify": { "command": "uv", "args": ["--directory", "/path/to/assertify", "run", "assertify", "serve"] } } }
</details>
Codex
codex mcp add assertify -- uv --directory /path/to/assertify run assertify serve
or in ~/.codex/config.toml:
[mcp_servers.assertify]
command = "uv" args = ["--directory", "/path/to/assertify", "run", "assertify", "serve"]
</details>
Cursor
~/.cursor/mcp.json:
{
"mcpServers": { "assertify": { "command": "uv", "args": ["--directory", "/path/to/assertify", "run", "assertify", "serve"] } } }
</details>
VS Code (Copilot)
.vscode/mcp.json:
{
"servers": { "assertify": { "type": "stdio", "command": "uv", "args": ["--directory", "/path/to/assertify", "run", "assertify", "serve"] } } }
</details>
Gemini CLI, Grok, Windsurf, Zed and others
Any client that runs local (stdio) MCP servers works. Use this command:
uv --directory /path/to/assertify run assertify serve
For JSON configs, use the mcpServers block shown under Cursor.
| Tool | What it does | |
|---|---|---|
list_profiles(site?) | Your saved logins (name, account email, site), optionally only one site's | |
start_login(url, profile?) / complete_login | Open a window for you to log in, then encrypt and save the session. No name: it's named after the account's email | |
rename_profile · delete_profile | Rename or remove a saved login | |
open_session(profile, url?, screenshots?) | Start a logged-in headless browser; returns a session_id and a page outline | |
| `open_sessions(site? \ | profiles?)` | Open several logins at once (e.g. every Gmail account), one session_id each |
snapshot | URL, title and interactive elements as [e12] button "Save"; pop-ups first, warnings for CAPTCHAs and sign-in pages | |
find(query) | Search the whole page for elements by label | |
click · type_text · select_option · press_key · scroll · back · navigate · wait_for | Act by ref or by visible text (click(text="Messages")), so small redesigns don't break a flow; each returns a fresh outline | |
| `upload_files(paths, ref? \ | text?)` | Attach files or whole folders: through the site's file dialog (text="Photo/video"), its upload field, or drag-and-drop. Only attaches; posting is a separate, confirmed click |
dismiss_popup | Close the pop-up on top with its close / "Not now" button | |
handoff(reason?) | Open the current page in a window for you (CAPTCHA, 2FA, expired login); the session picks up your fresh login | |
read_text | The visible text of the page, marked as untrusted website content | |
screenshot(ref?, full_page?) | Screenshot of the page or one element, shown to the agent and saved to a file | |
set_screenshots(enabled) | Attach a screenshot to every step (great for watching a run) | |
switch_tab | Popups become the active tab automatically; this switches back | |
save_session / close_session | Write refreshed cookies back to the vault (closing saves by default) | |
evaluate | Run JavaScript in the page. Off unless ASSERTIFY_ALLOW_EVAL=1 |
Ask *"show me a screenshot"* or *"open my GitHub session with screenshots on so I can follow along"*. Images appear in the chat in clients that show them, and every one is saved to ~/.assertify-mcp/screenshots/ /NNN- .jpg. The folder is private to you and cleared after 7 days.
Log in once per account. Leave the name out and Assertify names each login after the email address it finds on the page (falls back to google.com-1, google.com-2… when a site doesn't show one):
assertify login https://mail.google.com # sign in as you@gmail.com -> saved as "you@gmail.com"
assertify login https://mail.google.com # sign in as work@gmail.com -> saved as "work@gmail.com" assertify login work https://mail.google.com # or pick the name yourself assertify list google.com # just the Google logins assertify rename google.com-1 side-project
Then just ask:
open_sessions(site="google.com") and gets one session per account, which it can work through side by side.Each account lives in its own encrypted file and its own isolated browser, so cookies never mix. On sites that restrict automation, avoid running the same action on many accounts at once.
Tell your agent what to upload and where:
*"Post the photos in ~/Pictures/trip to my Facebook with the caption 'Back home'"*
The agent opens the composer, calls upload_files(paths=["~/Pictures/trip"], text="Photo/video"), writes the caption, then asks you before pressing Post. Under the hood:
Solo se muestra el principio; lee el resto en el repo