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

Argus Decision MCP

by commetversion 2.1.0i★ –iRuns on your computer
Registry nameio.github.commet/argus-decision-mcp

Install

Overview

Description from the maker (original English)

Preserve a user-authorized judgment and append later answers. No model verdict or human score.

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: ARGUS_TOKEN

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: ARGUS_DIR, ARGUS_TOKEN, ARGUS_TZ

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": {
    "argus-decision": {
      "command": "npx",
      "args": [
        "-y",
        "argus-decision-mcp"
      ],
      "env": {
        "ARGUS_DIR": "your-value",
        "ARGUS_TOKEN": "your-value",
        "ARGUS_TZ": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add argus-decision --env ARGUS_DIR=your-value --env ARGUS_TOKEN=your-value --env ARGUS_TZ=your-value -- npx -y argus-decision-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": {
    "argus-decision": {
      "command": "npx",
      "args": [
        "-y",
        "argus-decision-mcp"
      ],
      "env": {
        "ARGUS_DIR": "your-value",
        "ARGUS_TOKEN": "your-value",
        "ARGUS_TZ": "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": {
    "argus-decision": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "argus-decision-mcp"
      ],
      "env": {
        "ARGUS_DIR": "your-value",
        "ARGUS_TOKEN": "your-value",
        "ARGUS_TZ": "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

  • ARGUS_DIR env
    Directory for the append-only ledger (.argus). Set once and every tool falls back to it. Claude Code expands ${CLAUDE_PROJECT_DIR}; on other hosts use an absolute path.
  • ARGUS_TOKEN secret env
    Optional Argus account token. Set it and saved records can sync so Argus can return on the date you chose. Unset = fully local, no network.
  • ARGUS_TZ env
    Timezone that decides when a check-by date becomes today (e.g. Asia/Seoul). Unset = your machine's local timezone.

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 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account commet, 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 32696 servers in this category
  • Published to the registry more recently than 68% of the other 32696 servers in this category
  • Basic checks equal to or better than 100% of the other 32696 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 Argus Decision MCP 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: ARGUS_TOKEN

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 (2.1.0) reached the registry 17 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, LexPact UK Contracts

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 2 days ago
Install

Generate UK-law contracts: NDA, service, freelance, recruiter terms of business, IR35.

Runs on your computerUpdated 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.

Argus Decision MCP

English | 한국어

Argus carries a consequential decision across conversations: the user-adopted prediction, what reality should show, when to return, and what actually happened. The result becomes context for the next judgment. Argus never scores the person or invents a verdict.

Part of Argus · web app at argus.voyage · MIT licensed.

What using it looks like

You talk normally. Argus offers to keep one testable thing, then brings it back when reality can answer.

2026-08-19

you We're going with Postgres over DynamoDB — the join patterns kill us otherwise.

┌ Save this as a prediction? (your host renders the form) │ "Postgres handles our join patterns without a read-replica through Q4" │ check by 2026-10-01 └ accept as written · edit the wording or the date · decline

… six weeks later, in a different conversation …

2026-10-01 argus One check is due — you saved this on 2026-08-19: "Postgres handles our join patterns without a read-replica through Q4" What actually happened?

you We added a read replica in September. Analytics queries, not joins.

Recorded. The original sentence stays exactly as you wrote it, your answer is appended next to it, and nothing is scored.

Nothing is saved without you accepting it, and Argus never fills in the outcome for you.

Install

Requirements: Node.js 18 or newer — Node 20 LTS is the tested version (node --version; get it from nodejs.org). No API key and no account: records are local files from the first call.

Pick your host. Every path below installs the same server.

Claude Code

The plugin wires this server for you and adds the decision commands on top:

/plugin marketplace add commet/Argus

/plugin install argus@argus

Restart Claude Code, then /argus:settings doctor confirms the wiring.

Want the server alone, without the commands? Add it directly:

claude mcp add argus -- npx -y argus-decision-mcp          # this project only

claude mcp add -s user argus -- npx -y argus-decision-mcp # every project

claude mcp add defaults to the current project — use -s user if you want Argus everywhere.

Claude Desktop

Settings → Developer → Edit Config opens the file directly. It lives at:

  • macOS — ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows — %APPDATA%\Claude\claude_desktop_config.json

Add Argus to it, then quit Claude Desktop completely and reopen it (a window close is not enough):

{

"mcpServers": { "argus-decision": { "command": "npx", "args": ["-y", "argus-decision-mcp"], "env": { "ARGUS_DIR": "/absolute/path/to/where/records/should/live/.argus" } } } }

ARGUS_DIR is optional here too — a desktop app has no "current project", so records go to your personal home ledger (~/.argus) by default rather than scattering. Set it when you want them somewhere specific. On Windows, escape the backslashes ("C:\\Users\\you\\decisions\\.argus").

Windows: server does not appear

  • Run the command by hand first. npx -y argus-decision-mcp in a normal terminal prints a short help card and exits — that means the binary works (assistants launch it over a pipe, where it stays running as a server). A crash or error text instead of the card is the real problem.
  • npx failing while it works in your terminal usually means npm is not installed globally. Check that %APPDATA%\npm exists; if not, run npm install -g npm.
  • If the log mentions an unexpanded ${APPDATA}, add "APPDATA": "C:\\Users\\you\\AppData\\Roaming\\" to the env block above.
  • Logs: %APPDATA%\Claude\logs\mcp*.log (macOS: ~/Library/Logs/Claude).
Codex (CLI or app)
codex mcp add argus-decision -- npx -y argus-decision-mcp

codex mcp list # argus-decision should be listed and enabled

Restart Codex afterwards. A conversation opened before mcp add does not gain newly registered tools — quit and reopen the app, or start a new CLI session.

Codex: the confirmation form does not appear

Argus confirms a prediction with a one-tap form before saving it. Codex renders that form under its default approval policy. If yours is never, or approval_policy.granular.mcp_elicitations = false, Codex returns a protocol decline without ever showing the form. MCP supplies no marker that separates that policy response from a fast intentional decline, so Argus has to respect it as a decline. Enable MCP elicitations and retry if you want the form.

An AI-drafted premise has a chat fallback: when the confirm window cannot reach you, the draft comes back in the response, and once you approve it in conversation the assistant records it by calling again with chat_confirmed: true. Provenance stays ai_surfaced either way.

Any other MCP host
{

"mcpServers": { "argus-decision": { "command": "npx", "args": ["-y", "argus-decision-mcp"], "env": { "ARGUS_DIR": "/absolute/path/to/your/project/.argus" } } } }

Install once; there is nothing to update by hand. Leave the version off, as above — npx re-resolves a bare package name on every launch, so each session starts the current build.

Why no version range — and why that matters

Do not write a range like @^2. A range is satisfied by whatever already sits in the npx cache, so it never consults the registry again and the wire can stay frozen on an old build for weeks while everything looks healthy. Measured 2026-07-29, same spec string both times, cache holding an older version the range still allowed:

speclaunched
argus-decision-mcpthe current release
argus-decision-mcp@^2.0.0the stale cached build

An exact pin is correct but freezes there until someone edits it. argus_check_in reports the version actually running (data.server_version) if you ever need to confirm which build answered.

Where your records live

On your disk from the first call — nothing to set up.

ARGUS_DIR is optional. The default follows one rule — *project evidence decides where the ledger lives*:

  • the working directory is inside a git repo, or already has an .argus folder → /.argus (per-project isolation, unchanged)
  • otherwise (a temp folder, or an app that creates a fresh folder per conversation — the Codex desktop app does this) → the personal home ledger (~/.argus), so records accumulate across conversations instead of fragmenting into per-conversation orphans

A per-call absolute argus_dir overrides everything; ARGUS_DIR overrides the rule.

Argus never scans other projects. Existing home-level ledgers are not migrated or merged silently; point ARGUS_DIR at one explicitly if you need to inspect it.

Optional: account sync

Off until you turn it on. Nothing leaves the machine before you approve it in a browser:

npx argus-decision-mcp connect       # one browser approval, credential stored locally

npx argus-decision-mcp disconnect # revoke it here

Add --headless on a machine with no browser to get a device-code flow. For CI, set ARGUS_TOKEN to a sync token from the web app's settings page instead of running connect. With no credential, sync is a silent no-op — the local record is unaffected.

Your data

The records are plain append-only files under .argus/. They are yours: copy that folder to back it up, delete it to remove it. Uninstalling the server never touches it.

For the durable home that survives moves and worktrees, the CLI also has archive-export, archive-restore, and local-purge. Each one requires explicit arguments — --repository-id, an absolute --archive-dir, and a verbatim --confirm-repository before anything is deleted. That is deliberate: erasing judgment records should never be a one-word command. Run one without arguments and it names the argument it wants.

Tools

The complete callable surface is six tools:

ToolPurpose
argus_captureCapture a decision and its user-owned context.
argus_predictRecord one falsifiable claim and its check date.
argus_check_inRead records that need attention now.
argus_resolveAppend an outcome the user explicitly stated.
argus_patternsRead decisions, receipts, timelines, and patterns.
argus_settingsRead or update language, reminders, and explicit sync.

Names from pre-2.0 releases are not callable aliases. A cached call to one of them returns UNKNOWN_TOOL, so hosts cannot accidentally keep using obsolete contracts.

Design boundaries

  • Local-first, append-only records.
  • Project isolation by default.
  • User wording and AI-surfaced wording retain distinct provenance.
  • Recorded text is treated as untrusted data.
  • No verdict, grade, accuracy score, streak, or leaderboard.
  • Network sync is explicit; anonymous telemetry is off unless ARGUS_TELEMETRY=1.
  • Unexpected errors are logged server-side and returned as a generic message, avoiding path or stack disclosure to the model.

Development

npm install

npm run typecheck npm test npm run build npm pack --dry-run

The published package contains one bundled runtime entrypoint. Internal implementation and experimental modules are not shipped as separate callable or importable files.

See SECURITY.md for reporting and trust-boundary details.

Ask PopNx