rea
Reverse engineer anything with agents, from app behavior down to native binaries.
Recall from your own past coding agent sessions, kept on your machine.
Skills that teach the AI this kind of work; they work alongside this one
Reverse engineer anything with agents, from app behavior down to native binaries.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 18/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 30/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: 30 (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Oars. Follow https://mcp.popnx.com/i/manyoars-oars.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Oars for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "oars": { "command": "npx", "args": [ "-y", "@manyoars/oars", "sessions", "recall" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Oars tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"oars": {
"command": "npx",
"args": [
"-y",
"@manyoars/oars",
"sessions",
"recall"
]
}
}
}Use Oars and tell me what you can do for me, then show me one thing✓ If Claude says it is using Oars or shows a Oars tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Oars yet
Oars runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Oars
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Oars for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user oars -- npx -y @manyoars/oars sessions recall 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Oars tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user oars -- npx -y @manyoars/oars sessions recallYou should see Oars listed as connected
Use Oars and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Oars or shows a Oars tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Oars for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "oars": { "command": "npx", "args": [ "-y", "@manyoars/oars", "sessions", "recall" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Oars tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Oars and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Oars or shows a Oars tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Oars for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "oars": { "type": "stdio", "command": "npx", "args": [ "-y", "@manyoars/oars", "sessions", "recall" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Oars tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Oars and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Oars or shows a Oars tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user oars -- npx -y @manyoars/oars sessions recallClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"oars": {
"command": "npx",
"args": [
"-y",
"@manyoars/oars",
"sessions",
"recall"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"oars": {
"command": "npx",
"args": [
"-y",
"@manyoars/oars",
"sessions",
"recall"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"oars": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@manyoars/oars",
"sessions",
"recall"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
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 19, 2026
The registry name was verified with the GitHub account manyoars, which owns the repo
Code last changed yesterday
Uses Apache-2.0
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for @manyoars/oars@0.5.5
Checks only this package version, not every dependency · checked Nov 15, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/manyoars-oars)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed yesterday, and the latest version (0.5.5) reached the registry 5 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP servers
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one Oars | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | Apache-2.0 | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
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.
oars keeps a local, searchable record of your coding agent sessions, across Claude Code, Cursor, Codex, and other harnesses. Ask it about an error and it shows how many past sessions hit it, when, and which tools came next. More at manyoars.com.
npm install --global @manyoars/oars
Node 22.23.4 or later. ESM only. Local recall needs no account.
Or run it once without installing:
npx @manyoars/oars sessions try
Sample output (made-up sessions, from oars sessions try):
$ oars sessions recall --error "unexpected EOF while looking for matching quote"
Bash | bash: -c: line : unexpected EOF while looking for matching quote 3 sessions, 3 errors, first 2026-10-06T10:00:15.000Z, last 2026-10-20T10:00:27.000Z harness 2.1.300; followed by Bash x2, Read x1, Write x1; an edit followed 1 times
$ oars sessions recall --context --cwd C:\work\demo oars recall: errors that recur in this repository's earlier sessions. Check these before retrying:
No coding-agent history yet? oars sessions try runs recall, books, and the hook line over made-up sessions in a throwaway store under your temp folder, labeled synthetic and deleted on exit, and never touches your own store.
oars --help lists the commands below (oars help shows one command's flags). oars --version prints the version.
These flags work on every command:
--json prints one JSON document on stdout instead of text (see below).--api-url sets the platform API. The default is OARS_API_URL, else https://api.manyoars.com.--idempotency-key is the base of the idempotency key (default: a fresh UUID). Rerun a failed command with the same key to replay it.Signs in with your browser (RFC 8628 device flow) and stores the login.
Accounts are not open yet: oars login uses the Many Oars issuer by default, and until Many Oars sign-in at login.manyoars.com is deployed it exits 2 with an error that names login.manyoars.com.
--no-browser prints the link and code without opening a browser.--issuer-url is the Keycloak realm URL. The default is OARS_ISSUER_URL. With neither, login uses the built-in Many Oars issuer, https://login.manyoars.com/realms/aor; nothing has to be switched on first. When the built-in issuer does not answer discovery (it may not be deployed yet), with no --issuer-url or OARS_ISSUER_URL, the command prints "Cannot reach Many Oars sign-in at login.manyoars.com (it may not be deployed yet). Pass --issuer-url or set OARS_ISSUER_URL to use another issuer." and exits 2.Revokes the stored login and deletes it.
oars keys manages the API keys of your account.
oars keys create --name creates a key and prints its secret once; the platform keeps no copy. The default authorities are AGENT_OPERATE and AGENT_READ; --authority (repeatable) sets others, and --expires-in-days sets an expiry. --expires-in-days takes 1 to 365; without it the platform sets the expiry, and oars keys list shows it. Replace a key before it expires.--workload limits the key to one workload you created. Such a key may carry only AGENT_OPERATE and AGENT_READ (more is a 400, API_KEY_WORKLOAD_SCOPE_EXCEEDS_CAP), and it works on that workload only.--idempotency-key returns no secret: the command exits 5 and names the key, and you revoke it and create another.OARS_API_KEY set, any API key gets 403 HUMAN_SESSION_REQUIRED (exit 3) and logging in again does not help: unset it and use the oars login session.oars keys list lists the keys with their prefix, scope, and expiry. A secret never comes back.oars keys revoke ends a key at once. There is no rotate: revoke the key and create another. /oars/telemetry/, with counts, sizes, and closed words. It never holds session content, prompt text, a file path, a URL, or an argument.OARS_POOL_URL if you set one, else to the Many Oars pool (https://pool.manyoars.com), which is live. A per-install random id is in each event. Telemetry is off, with no prompt, on a machine whose time zone is in the EU, the EEA, or the UK (no switch overrides that); everywhere else, Many Oars Co. may license Usage Data, the events oars sends, as the first-run notice states.oars telemetry status says whether it is on and why; oars telemetry show prints the spool as stored; oars telemetry report prints your own numbers from it.oars telemetry off stops recording and sending; oars telemetry on resumes it. OARS_TELEMETRY=0 or DO_NOT_TRACK=1 turns it off for the process and wins over on.oars card --text # your week as a table, sized for a screenshot
oars card --month # the last 30 days as a picture: oars-card-month.png and .svg in this folder oars card --year --out me.png # the last 365 days, saved as me.png and me.svg oars card --week --text # a short plain-text receipt of your last 7 local days, to paste
oars card makes a share-ready card of your own week (the default, the last 7 days), month, or year across every harness, read from the local session store only. It shows your sessions and active days, the harnesses and models you used, tokens by model, tool calls, failed calls and how many were followed by a different next step, how often an edit was verified, commits and how many survived, and cost only where the harness recorded one. A count under the same floor oars sessions books uses prints too few. The depositor row reads ashore: run oars pool join until you sign in; signed in, it reads the number of weeks in which this machine sent a deposit, from the local sent record, and says it is this machine's.
Once a week, the first command you run in a terminal on or after Friday prints one line to stderr, Your week: N sessions, M strokes. \oars card --text\ for the table., never with --json, from a hook, from the MCP server, from a recall, from oars sessions try, or from oars card itself, and only when the week has a session. About one install in ten never sees it; card-line.json in the session store folder records the week and whether it was shown, held, or not_due, and card-line-id holds the id the holdback hashes, copied once from the telemetry install id when there is one, else random, so the arm never changes.
Nothing is uploaded and nothing is sent anywhere: the command makes no network call and prints one prefilled x.com link whose text is the card's own numbers, for you to post if you choose. The card carries no folder name, path, prompt or response text, repository name, or long-tail tool or model name, and posting it unlocks nothing. The picture is a byte-stable SVG and a PNG drawn from it with a built-in font; --text prints the table and writes nothing. --no-cost leaves the cost row out of the picture, the table, and --json.
oars card --week --text (both flags together, with no --month, --year, or --out) prints a different, shorter thing: a receipt of your last seven local days, at most twelve lines of plain text, none over 80 columns with no color. It shows the window's dates, sessions and active days, the harnesses, and two outcome counts only where the store can back them: failed tool calls (counted once per call, so a replayed result is not counted twice), and passing runs, the share of edited prompts with a runner recorded whose last build or test runner passed (only prompts whose verify is passed, failed, or masked are in the count; verify none and na are left out). Codex sessions are left out of both outcome counts, because the Codex reader loses shell outcomes on Codex 0.166 and later, and the receipt says so (a week of only Codex sessions prints outcomes Codex sessions not counted). It carries no path, repository, prompt text, tool or model name, cost, rank, or account row, and an empty week prints a one-line empty receipt and exits 0. Nothing is uploaded; you copy the text yourself.
oars sessions receipt [--out ] prints a Markdown review receipt for one session you choose: the verification commands it ran (tests, builds, linters, and type and format checks, matched against a fixed list in VERIFICATION_FAMILIES), in order, with the result each showed (exit 0, exit , failed, or not recorded), and a count of the other commands, which are not listed. These are commands the session ran and the results it observed on the author's machine; it is not proof the change is correct, and it maps to no pull request. It reads the local store only and sends nothing; it carries no prompt or assistant text, command output, or path (a home or absolute path prints as , and a command is cut to its first line). Commands run in a subagent are left out, and a Codex session's results print not recorded. With no id it lists your five most recent session ids and their dates. You copy the receipt yourself.
oars statusline # one line: oars 7d: 12 sessions, 4 active days
oars statusline --color # the same line with the identifier in bold
oars statusline prints one short line of your own last seven local days, for a terminal status line. It reads the local session store only, ignores stdin, makes no network call, sends no telemetry event, and writes nothing. It never edits your settings: you paste the snippet yourself. If the store cannot be read, it prints the identifier alone and exits 0.
To show it in Claude Code, add this to ~/.claude/settings.json (see the Claude Code status line docs):
{
"statusLine": { "type": "command", "command": "oars statusline" } }
Sample output:
oars 7d: 12 sessions, 4 active days
oars is the identifier.7d means the window is your last seven local days, today included.12 sessions is the sessions with a prompt in that window.4 active days is the distinct local dates with a prompt in that window.The line has no path, repository, prompt text, model or tool name, or cost. These are the same counts, with the same rules, as oars card --week --text; its definitions are the ones to read.
oars sessions keeps a local, deterministic memory of your own coding-agent sessions. The session commands make no model call and no network call, except gold arms, which sends redacted text through your own Claude subscription. oars also records telemetry events (a command's path, its flag names, how long it took, its exit code, and its error class, with a random install id, the oars version, the OS, and the time; never session content, prompts, paths, URLs, or argument values), which oars sends in batches to the pool server in OARS_POOL_URL, else to the Many Oars pool (live) (what telemetry records and how to turn it off).
What it captures: by default, the sessions of every Claude Code project folder and the sessions of Cursor, Codex, Copilot CLI, Gemini CLI, Grok Build, OpenCode, Pi, and VS Code Copilot Chat, plus OpenTelemetry GenAI agent traces (OTLP JSON files) fro