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

Letswork

by saicharanrajojuversion 3.0.0i★ –iRuns on your computer
Registry nameio.github.saicharanrajoju/letswork

Install

Overview

Description from the maker (original English)

Real-time collaborative coding via MCP — two developers, one codebase

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: Developer tools

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": {
    "letswork": {
      "command": "uvx",
      "args": [
        "letswork"
      ]
    }
  }
}

Run this in your terminal

claude mcp add letswork -- uvx letswork

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "letswork": {
      "command": "uvx",
      "args": [
        "letswork"
      ]
    }
  }
}

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

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account saicharanrajoju, 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 Developer toolsi

  • More stars than 0% of the other 1391 servers in this category
  • Published to the registry more recently than 13% of the other 1391 servers in this category
  • Basic checks equal to or better than 100% of the other 1391 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 Letswork 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 (3.0.0) reached the registry 7 months 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: GitHub, Desktop Commander, Cloudflare MCP

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

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 3 days ago
Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 15 days ago
Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months 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.

LetsWork

Real-time collaborative coding via Claude Code — two developers, one codebase, each using their own Claude subscription.

One developer hosts the session. The other joins from anywhere. Both get a live Claude Code window connected to the same project — with file locking and an approval system to prevent conflicts.


How It Works

  1. Host runs letswork start inside their project folder
  2. A secure HTTPS tunnel is created automatically via Cloudflare
  3. A one-time URL + guest token is generated and printed
  4. Host shares the join command with the guest
  5. Guest runs letswork join --token on their machine
  6. Both developers now have Claude Code connected to the same codebase

Requirements

RequirementmacOSWindows (WSL)
Python 3.10+brew install pythonComes with Ubuntu WSL
cloudflaredbrew install cloudflaredSee WSL section below
Claude Codenpm install -g @anthropic-ai/claude-codenpm install -g @anthropic-ai/claude-code (inside WSL)
Node.jsbrew install nodesudo apt install nodejs npm (inside WSL)

macOS — Host Setup

The host is the developer who owns the project. You start the session and share the join command.

Step 1 — Install dependencies
brew install cloudflared

pip install letswork

Step 2 — Install Claude Code
npm install -g @anthropic-ai/claude-code
Step 3 — Start the session

Navigate to your project folder and run:

cd /path/to/your/project

letswork start

You will be asked for your display name, then a session box appears:

╔══════════════════════════════════════════════════════════════════════╗

║ 🤝 LetsWork Session Active ║ ║ ║ ║ Send this command to your collaborator: ║ ║ letswork join https://abc123.trycloudflare.com --token a1b2c3d4 ║ ║ ║ ║ Press Ctrl+C to stop. ║ ╚══════════════════════════════════════════════════════════════════════╝

Copy the full `letswork join ...` command and send it to your collaborator.

Two new terminal windows open automatically:

  • Claude Code — already connected to LetsWork
  • A chat window to communicate with your collaborator
Step 4 — Approve guest changes

When the guest edits a file, you'll see a notification in Claude Code. Ask Claude:

get_pending_changes

Then approve or reject:

approve_change <id>

reject_change

Step 5 — Stop the session

Press Ctrl+C in the terminal where you ran letswork start.


macOS — Guest Setup

The guest connects to the host's project. You need the join command from the host.

Step 1 — Install dependencies
brew install cloudflared

pip install letswork

Step 2 — Install Claude Code
npm install -g @anthropic-ai/claude-code
Step 3 — Join the session

Run the command the host sent you:

letswork join https://abc123.trycloudflare.com --token a1b2c3d4

You'll be asked for your display name. Then two windows open:

  • Claude Code — connected to the host's project
  • A chat window to communicate with the host
Step 4 — Edit files

Ask Claude to read and edit files normally. When you write a file, it goes into an approval queue — the host reviews it before it's written to disk. You'll get a notification when it's approved or rejected.


Windows — Guest Setup (WSL)

LetsWork runs inside WSL (Windows Subsystem for Linux). The guest experience is the same as macOS once WSL is set up.

Step 1 — Enable WSL and install Ubuntu

Open PowerShell as Administrator and run:

wsl --install

Restart your computer when prompted. Ubuntu will install automatically.

Open Ubuntu from the Start menu and set up your Linux username and password.

Step 2 — Install dependencies inside Ubuntu

Open Ubuntu and run these one by one:

# Update packages

sudo apt update && sudo apt upgrade -y

Install Python

sudo apt install python3 python3-pip -y

Install Node.js and npm

sudo apt install nodejs npm -y

Install cloudflared

curl -L https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64 -o cloudflared chmod +x cloudflared sudo mv cloudflared /usr/local/bin/

Install letswork

pip3 install letswork

Step 3 — Install Claude Code inside Ubuntu
npm install -g @anthropic-ai/claude-code
Step 4 — Join the session

Run the command the host sent you, inside Ubuntu:

letswork join https://abc123.trycloudflare.com --token a1b2c3d4

You'll be asked for your display name. Claude Code launches directly in the same terminal window.

Note for Windows users: Claude Code runs in the WSL terminal — not as a separate window. Everything else works identically to macOS.


MCP Tools Available

Both host and guest have access to these tools inside Claude Code:

ToolWho Can UseDescription
list_filesBothList files and directories with lock status
read_fileBothRead file contents (1MB limit, text files only)
write_fileBothSubmit a file change (guest changes need host approval)
lock_fileBothLock a file for exclusive editing
unlock_fileBothRelease your own file lock
get_statusBothShow session info, connected users, and active locks
get_notificationsBothQuick summary of what needs attention
pingBothVerify connection to the host MCP server
set_display_nameGuest onlySet your display name for the session
my_pending_changesGuest onlyView your submitted changes awaiting approval
get_pending_changesHost onlyView all changes awaiting approval with diffs
approve_changeHost onlyApprove a pending change and write it to disk
reject_changeHost onlyReject a pending change
force_unlockHost onlyForce-release a stuck file lock

Approval Flow

Guest file writes do not go directly to disk — they go through the host's approval queue:

  1. Guest asks Claude to edit a file → write_file submits the change
  2. Host sees: 📝 guest submitted change to server.py (ID: a1b2c3)
  3. Host asks Claude: get_pending_changes — sees a full diff
  4. Host approves: approve_change a1b2c3 → file is written to disk
  5. Or rejects: reject_change a1b2c3 → guest is notified

Security

  • Random Cloudflare subdomain — URL is unguessable
  • Cryptographic token — second auth layer on top of the URL
  • All traffic encrypted via HTTPS
  • Path traversal prevention — guest cannot access files outside the project root
  • File locks auto-expire after 30 minutes
  • No accounts, no signup, no persistent credentials — session ends when host stops

Constraints

  • Maximum 2 users per session (Host + 1 Guest)
  • Text files only — binary files not supported
  • 1MB file size limit per read/write operation
  • Guest has no shell access — file operations only
  • cloudflared must be installed on the host machine (guest does not need it on macOS, but WSL guests do)

CLI Reference

letswork start [--port PORT] [--debug]   # Start a session (default port: 8000)

letswork join --token # Join a session as guest


Architecture

Host Machine:

[Project Files] ← [MCP Server :8000] ← [Cloudflare Tunnel] ← HTTPS URL ↑ Guest connects here via stdio proxy + secret token

The guest connects through a stdio proxy rather than directly over HTTP — this avoids Cloudflare SSE reliability issues and gives stable MCP connectivity.


License

MIT — see LICENSE


Built with the Model Context Protocol.

Ask PopNx