Letswork
Turns your Claude Code session into a two-person workspace where one developer hosts a project and another joins remotely through a Cloudflare tunnel. The guest connects via stdio proxy with a one-time token and gets read/write access to the same codebase, but all their file edits go into an approval queue the host reviews with diffs before committing to disk. File locking prevents simultaneous edits to the same file. Built-in chat window keeps you coordinated. Exposes tools like list_files, read_file, write_file, lock_file, get_pending_changes, and approve_change. Host needs cloudflared installed, guest just needs the CLI. Useful when pair programming across machines without standing up a full dev server or dealing with Git conflicts in real time.
- tools
- 14
- transport
- STDIO
- last updated
- Apr 8, 2026
Tools
14 toolsPublic tool metadata for what this MCP can expose to an agent.
list_filesList files and directories with lock status
List files and directories with lock status
No parameter schema in public metadata yet.
read_fileRead file contents (1MB limit, text files only)
Read file contents (1MB limit, text files only)
No parameter schema in public metadata yet.
write_fileSubmit a file change (guest changes need host approval)
Submit a file change (guest changes need host approval)
No parameter schema in public metadata yet.
lock_fileLock a file for exclusive editing
Lock a file for exclusive editing
No parameter schema in public metadata yet.
unlock_fileRelease your own file lock
Release your own file lock
No parameter schema in public metadata yet.
get_statusShow session info, connected users, and active locks
Show session info, connected users, and active locks
No parameter schema in public metadata yet.
get_notificationsQuick summary of what needs attention
Quick summary of what needs attention
No parameter schema in public metadata yet.
pingVerify connection to the host MCP server
Verify connection to the host MCP server
No parameter schema in public metadata yet.
set_display_nameSet your display name for the session
Set your display name for the session
No parameter schema in public metadata yet.
my_pending_changesView your submitted changes awaiting approval
View your submitted changes awaiting approval
No parameter schema in public metadata yet.
get_pending_changesView all changes awaiting approval with diffs
View all changes awaiting approval with diffs
No parameter schema in public metadata yet.
approve_changeApprove a pending change and write it to disk
Approve a pending change and write it to disk
No parameter schema in public metadata yet.
reject_changeReject a pending change
Reject a pending change
No parameter schema in public metadata yet.
force_unlockForce-release a stuck file lock
Force-release a stuck file lock
No parameter schema in public metadata yet.
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageReadme
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
- Host runs
letswork startinside their project folder - A secure HTTPS tunnel is created automatically via Cloudflare
- A one-time URL + guest token is generated and printed
- Host shares the join command with the guest
- Guest runs
letswork join <url> --token <token>on their machine - Both developers now have Claude Code connected to the same codebase
Requirements
Details
- Repository
- github.com/saicharanrajoju/letswork-mcp
- Package
letswork- Transport
- STDIO
- Registry
- MCP registry, active