Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Codeman

by Ark0Nversion 1.48.0i★ –iRuns on your computer
Registry nameio.github.Ark0N/codeman

Install

Overview

Description from the maker (original English)

Start, prompt and read AI coding agent sessions (Claude Code, Codex, Gemini CLI and more) in Codeman

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

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
  • You need to fill in: CODEMAN_API_URL, CODEMAN_PASSWORD

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).
  • You fill in yourself: CODEMAN_API_URL, CODEMAN_PASSWORD

Values marked secret are keys to your account. Never share them or paste them into a chat.

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": {
    "codeman": {
      "command": "npx",
      "args": [
        "-y",
        "aicodeman",
        "mcp"
      ],
      "env": {
        "CODEMAN_API_URL": "your-value",
        "CODEMAN_PASSWORD": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add codeman --env CODEMAN_API_URL=your-value --env CODEMAN_PASSWORD=your-value -- npx -y aicodeman mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "codeman": {
      "command": "npx",
      "args": [
        "-y",
        "aicodeman",
        "mcp"
      ],
      "env": {
        "CODEMAN_API_URL": "your-value",
        "CODEMAN_PASSWORD": "your-value"
      }
    }
  }
}

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.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "codeman": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "aicodeman",
        "mcp"
      ],
      "env": {
        "CODEMAN_API_URL": "your-value",
        "CODEMAN_PASSWORD": "your-value"
      }
    }
  }
}

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.

Values you fill in

  • CODEMAN_API_URL required env
    Where your Codeman server runs, for example https://127.0.0.1:3000. Never guessed.
  • CODEMAN_PASSWORD secret env
    Codeman's HTTP Basic password, when the server has one.

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 Ark0N, 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 95% 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 Codeman 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?

You need to fill in: CODEMAN_API_URL, CODEMAN_PASSWORD

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 (1.48.0) reached the registry yesterday.

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

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

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.

Mission control for AI coding agents

Claude Code • OpenCode • Codex • Antigravity • Gemini • Pi • Grok • DeepSeek • OMP • Copilot • Terminal - One Dashboard • Any Device

English • 简体中文

Codeman is a self-hosted mission control for AI coding agents. It spawns Claude Code, OpenCode, Codex, Antigravity, Gemini, Pi, Grok, DeepSeek Harness, OMP, or GitHub Copilot CLI inside persistent tmux sessions, streams the real terminal to any browser, and keeps agents productive after you walk away: it re-prompts on idle, resumes when a usage limit resets, runs scheduled jobs, and shows every background agent working in real time.

Get started in one line (macOS & Linux, Windows via WSL):

curl -fsSL https://getcodeman.com/install | bash
codeman web

Open http://localhost:3000 and start your first session

The installer asks before every system change, and re-running the same line updates in place. Full details: Quick Start - Installation.

  • One dashboard, ten CLIs - run Claude Code, OpenCode, Codex, Antigravity, Gemini, Pi, Grok, DeepSeek, OMP, or GitHub Copilot per session (plus plain shell), locally, in Docker, or over SSH, with your own dashboards open as web tabs beside them
  • Truly phone-friendly - a touch-optimized terminal with instant local echo, QR login, swipe navigation, and push notifications
  • Runs while you sleep - idle detection + respawn cycling and auto-resume when a subscription limit resets, for 24+ hour unattended runs
  • See your agents think - live floating windows for every subagent and teammate, with real-time transcripts
  • Agents can drive it too - the codeman skill (for every agent CLI), codeman agent and an MCP server let one agent start workers in any CLI, prompt them, wait for them and collect their answers
  • Nothing gets lost - tmux persistence across restarts and network drops, exactly-once input delivery, full-scrollback replay
  • Self-hosted and private - loopback-only by default, MIT licensed, no telemetry, runs entirely on your machine

Quick Start - Installation

curl -fsSL https://getcodeman.com/install | bash

This installs Node.js, tmux and a build toolchain if missing (node-pty ships no Linux prebuilds, so it compiles from source), clones Codeman to ~/.codeman/app, and builds it. It looks at what is already on the machine, asks at most three questions, then does all the work unattended and ends on the URL with a QR code for your phone. A few things worth knowing:

  • Three questions, all up front. How the dashboard is reached, optionally what to call this machine on your tailnet, and whether to run Codeman as a background service (systemd/launchd, auto-start on boot; Enter says yes). Everything that needs you, including one consent for all missing packages, one sudo password, and the Tailscale login, happens before the build, so you can walk away while it compiles.
  • How it's reachable, your choice. Tailscale (loopback bind fronted by tailscale serve, so you get https:// . .ts.net with a real certificate and your tailnet as the login, no password needed), any device on your network (0.0.0.0, with a strongly recommended password prompt), or this machine only (127.0.0.1, safest). Skipping the password on a network bind requires an explicit confirmation and ends with a loud warning. The highlighted default reflects what is already on the machine (Tailscale when it is already connected, your existing binding on a re-run), and a bare Enter never pulls in new software. If another app already owns :443 on your node, Codeman goes under https:// . .ts.net/codeman or on a second port instead of replacing it. A bare codeman web started by hand still defaults to loopback.
  • The name is yours to choose. By default the URL uses the machine's existing tailnet name. Answering yes to the second question renames the machine to codeman- (which also renames it for SSH, so the default is no); install.sh name does it later.
  • Re-run to update. The same one-liner updates a finished install in place: local changes in ~/.codeman/app are stashed (never discarded), and a running service is restarted and verified. If a first install was interrupted, re-running resumes the full setup instead. install.sh status prints the URLs and the QR code again; install.sh update, install.sh tailscale and install.sh uninstall also exist.
  • Flags for the impatient. curl -fsSL https://getcodeman.com/install | bash -s -- --tailscale --service answers the questions from the command line (--lan, --local, --run, --no-start, --name , --port , --yes too). CI / headless: without a terminal attached, steps that would change your system abort with instructions instead of running silently; set CODEMAN_NONINTERACTIVE=1 to approve them for automation.

You'll need at least one AI coding CLI installed — Claude Code, OpenCode, Codex, Antigravity, Gemini CLI, Pi, Grok Build, DeepSeek Harness, OMP, or GitHub Copilot CLI (any combination works; Gemini CLI is enterprise-only since Google's consumer cutover, and Antigravity is its successor). The installer detects whichever of the ten is present; if none is found, it offers to install any of them from a menu (DeepSeek excepted, since its npm package installs only a launcher with no runnable profile), or you can skip and install one yourself later. After install:

codeman web

Open http://localhost:3000 and start your first session

Sharing with a small team? Start it in multi-user mode instead: each person gets their own login and workspace.

codeman users add alice --admin      # create the first admin account

codeman web --multiuser # named logins + per-user case spaces

Prefer Docker Compose? A local-image Compose deployment ships in docker/: copy docker/.env.example to docker/.env, set CODEMAN_PASSWORD, then run bash docker/Start-Codeman.sh on Linux. Codeman runs in a container and spawns Docker cases as sibling containers through the host socket. After updating, run the script again rather than a plain docker compose up, so the rebuilt image, refreshed volumes and entrypoint arrive together. See the Docker deployment guide for direct Compose commands, storage and networking options.

Details in Multi-User Mode below.

Keep it running in the background

To outlive the shell you started it in, without setting anything up:

codeman web -d          # detach; logs to ~/.codeman/web.log

codeman web --status # is it up, and on which pid codeman web --stop # graceful SIGTERM; agents keep running in tmux

-d waits until the server actually answers before reporting success, and refuses to start a second one on the same data dir (two servers sharing a tmux socket attach to each other's sessions).

To have it come back after a reboot, install it as a service instead. The installer's final menu does this for you (option 2); codeman service is the equivalent for an npm i -g aicodeman install:

codeman service install     # systemd user unit (Linux) or LaunchAgent (macOS)

codeman service status codeman service uninstall

service install writes the unit with your current PATH baked in, which matters more than it sounds: launchd hands a job /usr/bin:/bin:/usr/sbin:/sbin, so a Homebrew or nvm node, tmux or claude is invisible to a hand-written plist. It never copies CODEMAN_PASSWORD into the unit file; add that yourself if the service needs auth.

To write the unit by hand instead:

Linux (systemd):

mkdir -p ~/.config/systemd/user

cat > ~/.config/systemd/user/codeman-web.service << EOF [Unit] Description=Codeman Web Server After=network.target

[Service] Type=simple ExecStart=$(which node) $HOME/.codeman/app/dist/index.js web Restart=always RestartSec=10

[Install] WantedBy=default.target EOF systemctl --user daemon-reload systemctl --user enable --now codeman-web loginctl enable-linger $USER

macOS (launchd):

mkdir -p ~/Library/LaunchAgents

cat > ~/Library/LaunchAgents/com.codeman.web.plist << EOF <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

Label com.codeman.web ProgramArguments

$(which node) $HOME/.codeman/app/dist/index.js web

RunAtLoad KeepAlive StandardOutPath /tmp/codeman.log StandardErrorPath /tmp/codeman.log

Only the beginning is shown; read the rest in the repo

Ask PopNx