Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
OTPilot
Overview
Description from the maker (original English)
Use your OTPilot accounts (passwords, 2FA codes) to sign in and run commands, without seeing them.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"otpilot": {
"command": "npx",
"args": [
"-y",
"@otpilot/mcp"
]
}
}
}Run this in your terminal
claude mcp add otpilot -- npx -y @otpilot/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"otpilot": {
"command": "npx",
"args": [
"-y",
"@otpilot/mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"otpilot": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@otpilot/mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account OTPilot, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32403 servers in this category
- Published to the registry more recently than 64% of the other 32403 servers in this category
- Basic checks equal to or better than 100% of the other 32403 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is OTPilot safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 21 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, LickityClick
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
LickityClick
by lickity.click
Create, edit and track LickityClick short links, campaigns and click stats from your AI assistant.
Computer or cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
OTPilot for AI agents (@otpilot/mcp)
Let Claude Code, Codex, Cursor or any MCP agent sign in to websites and run commands with your passwords and 2FA codes — without the agent ever seeing them. You choose which accounts each agent may use, in the OTPilot browser extension.
npx -y @otpilot/mcp@latest connect- It shows a verification code and opens a page to sign in to OTPilot (a free account works).
- In the extension, Agents shows the agent: approve it if the code matches.
- Allow it some accounts (Agents → + Add account), or let it ask for them as it works.
Claude Code plugin (the MCP server plus a skill that teaches Claude to use it):
/plugin install otpilot --marketplace OTPilot/OTPilot(Before Claude Code 2.1.275: /plugin marketplace add OTPilot/OTPilot, then /plugin install otpilot@otpilot.)
then connect it once: npx -y @otpilot/mcp@latest connect --name "Claude Code".
Or add the server to your agent yourself (connect prints these for you):
| Agent | |
|---|---|
| Claude Code | claude mcp add otpilot -- npx -y @otpilot/mcp@latest |
| Codex | ~/.codex/config.toml: [mcp_servers.otpilot] command = "npx" args = ["-y", "@otpilot/mcp@latest"] |
| Cursor | ~/.cursor/mcp.json: { "mcpServers": { "otpilot": { "command": "npx", "args": ["-y", "@otpilot/mcp@latest"] } } } |
For Codex and other agents that read AGENTS.md, add a line so they reach for it: *"For passwords, 2FA codes, API keys or any login, use the otpilot MCP tools (list_accounts, browser_login, run); never ask me to paste a secret."*
Each agent is its own identity, approved on its own: connect Claude Code and Codex separately (connect --name Codex), and add --profile as connect shows.
On a server or VPS
Run it where the agent runs — your laptop, a VPS, a container. On a server without a browser, skip the opener and open the printed link on any device signed in to OTPilot, then approve it in the extension if the codes match:
npx -y @otpilot/mcp@latest connect --name VPS --no-opennpx -y @otpilot/mcp@latest --profile vps # what the agent runs npx playwright install --with-deps chromium # only for browser_login without Chrome
With no keychain (a bare Linux box) the credentials go to ~/.config/otpilot/mcp- .json (0600): the accounts you allow are opened on that machine, so connect only machines you trust — whoever has root there can use them.
Tools
| Tool | What the agent gets |
|---|---|
list_accounts | The accounts it may use, by name and site |
request_access(query, reason) | Asks you for another account; you pick it in the extension |
browser_login(account, url?) | OTPilot signs in (username, password, 2FA — only on the account's own site) and returns a Playwright storageState file with the session |
run(command, env) | Runs the command with secrets in its environment ({ "PGPASSWORD": "Staging DB/password" }, …/totp for a fresh 2FA code); output comes back with every secret removed |
check_request(request_id) | Whether you answered a request that was still waiting |
No tool returns a password, a 2FA code or any other value.
Security
- The agent's own key.
connectcreates an ECDH P-256 keypair; the private key stays in your OS keychain. Each account you allow is a copy, holding only what you chose (just the 2FA code, the sign-in, or chosen fields), encrypted for that key in the extension. OTPilot's servers only see ciphertext. - Two approvals. Connecting an agent gives it nothing; each account is allowed per agent. The verification code is derived from the agent's public key on every side, so a swapped key shows a different code.
- Limits you set: for a while or until revoked, "ask me every time", and "only with these commands":
runthen accepts only that program, called by name and resolved on the server's PATH (never from the working or temp directory), as a single command with no chaining or redirection — a guard against mistakes and simple tricks, not against an agent that can plant its own binary on your PATH. - Only over HTTPS (plain HTTP just for local hosts), and every secret is scrubbed from what comes back — before the output is cut, so none is left half-removed. A timeout kills the command and everything it started.
- Only on the right site.
browser_loginfills only on pages the account's saved sites cover. - Activity and revoke in the extension's Agents view.
- The honest limit: an agent that runs commands decides what they do and could try to reveal a secret on purpose. OTPilot scrubs secrets from what it returns; for sensitive accounts allow only the 2FA code, limit the commands, or turn on "ask me every time".
Commands
otpilot-mcp connect [--name "Claude Code"] [--profile p] [--no-open]otpilot-mcp status [--profile p] # name, verification code, allowed accounts otpilot-mcp disconnect [--profile p] # forget the credentials here (revoke it in the extension too) otpilot-mcp [serve] [--profile p] # the MCP server (stdio) — what your agent runs
browser_login uses your installed Google Chrome (or Edge); without one, run npx playwright install chromium. Sessions are saved to .otpilot/ in the working directory: keep it out of git.
License: GPL-3.0. Source: github.com/OTPilot/OTPilot.