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

ai-dev-workspace

by Alenroyfeildversion 0.1.0b7i★ –iRuns on your computer
Registry nameio.github.Alenroyfeild/ai-dev-workspace

Install

Overview

Description from the maker (original English)

Local Markdown task memory shared by Claude Code and Codex over stdio MCP.

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: Docs, sheets & office work

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

  • PyPIPython’s uv installed (for the uvx 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": {
    "ai-dev-workspace": {
      "command": "uvx",
      "args": [
        "ai-dev-workspace"
      ]
    }
  }
}

Run this in your terminal

claude mcp add ai-dev-workspace -- uvx ai-dev-workspace

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "ai-dev-workspace": {
      "command": "uvx",
      "args": [
        "ai-dev-workspace"
      ]
    }
  }
}

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": {
    "ai-dev-workspace": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "ai-dev-workspace"
      ]
    }
  }
}

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 Alenroyfeild, 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 Docs, sheets & office worki

  • More stars than 0% of the other 2174 servers in this category
  • Published to the registry more recently than 91% of the other 2174 servers in this category
  • Basic checks equal to or better than 100% of the other 2174 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 ai-dev-workspace 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.1.0b7) reached the registry 2 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

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

Agent-Native Google Calendar - manage events, sync, and public booking

Runs in the cloud★ 7,620MITUpdated 2 months ago
Install

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 6 days ago
Install

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Runs on your computer★ 847MITUpdated 3 days ago
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.

AI Dev Workspace

Your assistant remembers work between sessions in Markdown you own. Shared, durable task memory for developers who switch between Claude Code, Codex, and other assistants.

Quick start

Try offline before connecting a repo: ws demo · 5-minute tutorial · Claude Code + Codex guide · remove it

pipx install ai-dev-workspace --pip-args='--pre'  # beta; omit --pip-args after a stable release

cd ~/code/myapp && ws start

No pipx? brew install pipx, or python3 -m venv ~/.ws && ~/.ws/bin/pip install --pre ai-dev-workspace; put its bin directory on PATH before ws start.

Prefer a Claude Code plugin? Preview. Not yet listed in Anthropic's official plugin directory; install from our GitHub marketplace:

/plugin marketplace add Alenroyfeild/ai-dev-workspace

/plugin install ai-dev-workspace@ai-dev-workspace

Live-checked on beta.5 (2026-10-22). See the [plugin preview](docs/ADVANCED.md#claude-code-plugin-preview).

ws start previews every file and writes nothing until you confirm. Generated assistant hooks and configs stay local (.git/info/exclude), task memory lives outside the repo in ~/.ai-dev-workspace/ , and ws start --undo cleanly removes repo wiring.

Watch (videos for 0.1.0b6)

Use cases

  • Switch Claude Code ↔ Codex mid-task: Start in Claude Code, save a checkpoint, and continue in Codex with the exact same brief and task memory (guide).
  • Resume tomorrow without re-explaining: Inject active tasks, recent decisions, and blockers directly into context at session start (tutorial).
  • Stop retrying failed approaches: Dead ends appear under Do not redo: in every fresh session brief (guide).
  • Keep verified corrections: Record decisions or constraints with ws remember so fresh sessions follow earlier rulings (commands).
  • Block risky commands and leaks: Opt-in guards pack denies dangerous shell operations and secrets in commands or written files (packs).
  • Share domain notes with a team (preview): Share approved knowledge via private git repository with consent-based previews (team).

Example

Session 1 — You: “Empty email returns missing_email; leave signup unchanged.”

Assistant: “I’ll trace login and keep the decision with this task.” You: “Save a checkpoint and stop here.”

Session 2 — You: “Continue the login fix.” Assistant: “The saved note says return missing_email and leave signup unchanged.” You: “Yes, continue.”

Features

FeatureStatusWhat it doesDocs link
Session briefStableInjects bounded task memory, decisions, and blockers at session startOverview
Decisions & handoffsStableSaves status, next action, and explicit rulings (ws checkpoint, ws remember)Commands
Dead endsStableRecords failed approaches and displays them as Do not redo:Concepts
LessonsStableCaptures reusable cross-task takeaways and guidance (ws lesson)Commands
ws lesson reviewStableRead-only list of lessons with old date stamps (--days N); changes or deletes nothingCommands
MCP serverStableExposes 7 core tools by default; others by name on request via stdioMCP
Guards packStablePreToolUse hook denies risky commands and secrets before execution; beta.7 reads git push option grammar (abbreviations, --prune, --mirror); a safety net, not a security boundaryPacks
Discipline packStableAdvisory nudge when the same command fails repeatedly in a sessionPacks
ws digestStableCompresses verbose terminal output into focused markdown notesCommands
Native importsStableReads existing Claude and Codex memory files (ws import native)Commands
ws import claude-memPreviewFixture-tested SQLite copy import; newer upstream schemas may not importAdvanced
ws auditStableRead-only stack/wiring suggestions from bounded local manifests; no login or live-client proofCommands
ws demoStableCreates an isolated sandbox repo to test commands safelyTutorial
Claude Code pluginPreviewHooks + MCP; needs CLI + ws start; not in Anthropic directory; Windows untestedAdvanced
Codex pluginPreviewHooks need a trusted manual desktop install; no MCP; hooks not live-testedAdvanced
Cursor pluginPreviewFixture-tested only; not submitted; no verified install commandAdvanced
Codex SessionStart catch-upPreviewRecovers changed transcript content for the claimed task; fixture-tested, not live-tested with Codex resumeAdvanced
MCP plugin roots discoveryPreviewPlugin server finds a ws start repo from client roots; Codex offers no rootsAdvanced
Worker fallback chainPreviewOnly declared providers and read-only roles run; timeout is a failed attemptAdvanced
Gateway providerPreviewLocal fake-server tests only; sends a redacted brief to configured base_url, without toolsAdvanced
Compact MCP recallStableBounded note cards and explicit untrusted detail; CLI snippets unchangedAdvanced
Lesson promotionStableRepeated-note similarity suggests a draft; no automatic rule installationAdvanced
digest_file MCP toolPreviewOpt-in size-only advice; scoped file summaries, no automatic compressionPacks
Behavior packStableOpt-in engineering guidelines; advice, not enforcement or learned session patternsPacks
Skills packagingStableFormat checked; third-party installer not verified; CLI and setup still requiredSkills
Team sharingPreviewPrivate git-backed knowledge repo with consent-based pulls and previewsTeam
MCP RegistryPreviewPre-configured server.json catalog entry for MCP client discoveryMCP

How it works

Claude Code / Codex / Cursor / Copilot / Gemini / Antigravity

│ (session startup & capture hooks) ▼ ~/.ai-dev-workspace/ / (private, outside repo) ├── workspace.json (settings, active task, packs) └── vault/ ├── Tasks/ .md (status, next action, decisions, blockers) └── Learnings.md (reusable cross-task lessons & dead ends) ▲ │ (MCP stdio connection: 7 core tools by default; others by name) Local Assistant (MCP client)

Memory storage makes no background model calls. ws delegate --run starts only declared assistant CLIs or sends a redacted brief to an explicitly configured gateway; output is unverified. Task memory is plain Markdown you own.

Results

Measured in bench/README.md across independent paired investigations (Codex gpt-6-luna, n=5 per cohort):

ArmPass (October 11)Pass (October 10)
Fresh baseline (no memory)0/50/5
Workspace (automatic brief)2/51/5
Plain Markdown handoff5/54/5

The latest controlled runs show the plain Markdown handoff beating the workspace (5/5 and 4/5 against 2/5 and 1/5), with the automatic-capture release gate still unmet. The win for the workspace is structure, cross-assistant handoff, and avoiding manual file management. Details and earlier runs: bench/README.md and docs/MEASUREMENTS.md.

Compared with

  • Built-in memory files (CLAUDE.md, AGENTS.md): Plain instructions per assistant; ai-dev-workspace adds cross-assistant handoffs, active task state, and Do not redo: constraints.
  • A plain HANDOFF.md: Works well for manual notes (and beat automatic workspace capture in latest benchmark cohorts: 5/5 vs 2/5); ai-dev-workspace adds cross-assistant automation, structured brief injection, and staleness warnings.
  • claude-mem: Captures tool use through hooks and compresses it with AI into SQLite + vector search (upstream docs), providing automatic memory capture without explicit commands; ai-dev-workspace keeps explicit Markdown you own, makes no background model calls for memory (explicit delegation can call declared CLIs or a configured gateway), and focuses on durable handoffs with next steps and dead ends (guide).

Compatibility

AssistantStatusTest proof
Claude Codesupported, tested live on macOSCI-tested
Codexsupported, tested live on macOSCI-tested
Cursorsupported, fixture-tested; live reports welcomeCI-tested
Copilot (VS Code)supported, fixture-tested; live reports welcomeCI-tested
Gemini CLIsupported, fixture-tested; live reports welcomeCI-tested
AntigravityPreview, fixture-tested; rules, MCP, SessionStart/PreToolUse hooks; no automatic captureCI-tested

Testers on Cursor, Copilot (VS Code), Gemini CLI, or Antigravity: please share problems through Something broke.

Known limits

  • Client coverage: Claude Code and Codex are live-tested on macOS; Linux and Windows are CI-tested only. Cursor, Copilot (VS Code), Gemini CLI, and Antigravity are fixture-tested.
  • Capture is best-effort: Explicit CLI commands (ws remember, ws checkpoint) are deterministic; automatic transcript cue-word capture is best-effort.
  • Guards are a safety net: Pattern matching blocks common risky commands and secrets in commands or written files, bu

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

Ask PopNx