nostrings
● Activeio.github.vpatel9202/nostrings
Computer use on your Mac and Android phone: JS scripts, accessibility diffs, background input.
Connect this server
One click to install, or copy the config below. Suits: Claude Desktop · Cursor.
Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):
{
"mcpServers": {
"nostrings": {
"command": "npx",
"args": [
"-y",
"nostrings@0.5.1",
"mcp"
]
}
}
}claude mcp add nostrings -- npx -y nostrings@0.5.1 mcpcodex mcp add nostrings -- npx -y nostrings@0.5.1 mcpcode --add-mcp '{"name":"nostrings","type":"stdio","command":"npx","args":["-y","nostrings@0.5.1","mcp"]}'Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.
A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.
- Category
- Developer Tools
- Version
- 0.5.1
- Registry
- active
- Published
- 11/19/2026
Is it safe? Is it maintained?
Serverdex check: Nov 22, 2026Looks healthy: nostrings is maintained, open source.
- Maintained
- Active
- Last commit 2 days ago (Nov 20, 2026), 0 open issues.
- Official registry
- Active
- Published as io.github.vpatel9202/nostrings in the official MCP registry, version 0.5.1.
- Source
- Open source, MIT
- Public repository under the MIT licence, 0 stars, 0 forks.
- Runs
- On your machine
- A local npm package started by your client; it can reach whatever your user account can.
- Credentials
- None declared
- The registry entry declares no required environment variables.
- Owner
- Unclaimed
- Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.
Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.
On GitHub
read Nov 21, 2026- Stars
- 0
- Forks
- 0
- Last push
- Nov 20, 2026
- License
- MIT
JavaScriptaccessibilityai-agentsautomationclaude-codecomputer-usemacosmcpmcp-server
From the README
nostrings Computer use for coding agents on your Mac and your Android phone: one JavaScript call per step, accessibility diffs instead of screenshots, and your screen stays yours. No strings attached. On the next call, calc is still bound. An agent writes a few lines per step instead of making one tool call per click, and reads what changed instead of a fresh picture of the window. • A script per step, not a tool call per click. Bindings and helper functions persist across calls, so one call can click, type, loop, and read. • Diffs, not screenshots. The default read is the accessibility tree as text, and later reads show only changes. Screenshots and pixel clicks are there when the tree is empty (Citrix, canvases). • Background by default. Keys, clicks, drags, and scrolls reach the app while you keep working in another one. Your cursor stays put, and a drawn cursor shows what the agent is doing. • Your phone too. ui.device() drives an Android phone or emulator over ADB from the same session. On Android 14+ apps run on a hidden screen, so the phone's own screen is left alone. In an author-run test of six setups on 12 macOS tasks (2 runs each), nostrings had the lowest total cost, $0.57 against $1.41 to $5.67, and the fewest round trips and the most passes. What to know first: the Mac side is tested on macOS 27 on Apple silicon. You need the Xcode command line tools to build a small helper app, and you grant it Accessibility and Screen Recording.…
Read the full README on GitHub →Alternatives to nostrings
All nostrings alternatives →Best Developer Tools servers →The most-starred Developer Tools servers in the index, with their live-check result.
| Server | Stars | Last push | Live check |
|---|---|---|---|
| REA | 466,935 | Nov 2026 | Local / not checked |
| GitHub | 34,658 | Nov 2026 | Needs sign-in |
| Repomix | 29,280 | Nov 2026 | Local / not checked |
| Compiler Explorer | 19,201 | Nov 2026 | Working |
| XERJ | 19,135 | Nov 2026 | Local / not checked |
nostrings: questions people ask
- Is nostrings a remote or a local MCP server?
- According to its entry in the official MCP registry, nostrings ships as a local package (npm) that your client starts on your machine.
- Is nostrings safe to use?
- Looks healthy: nostrings is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: On your machine; credentials: None declared. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
- Is nostrings still maintained?
- Active: the repository's last commit 2 days ago. Last push Nov 20, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 21, 2026.
- How do I add nostrings to Claude, Cursor or VS Code?
- Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
More Developer Tools servers
Browse all Developer Tools →Vercel OSS Registry
VrilLabs
Search all 138 projects funded by the Vercel Open Source Program: repos, descriptions, topics.
Cynicalsally
w1ckedxt
Brutally honest code reviews: scores, real issues, and usable fixes. CLI + MCP server.
RegexForge
walkojas-boop
Deterministic regex synthesis from labeled examples. Zero LLM, proof matrix, backtracking audit.
Zaoqiniaoer
wangjingjing1026uwh-hub
Free self-check list first, or pay a real person in China to go look and report what they saw.
Dr Strange
wangyingsm
Code graph for coding agents: who calls this, what a change reaches, in one round trip.
Reado
WatermelonBros
Your code review comments from Reado, the read-first IDE, as context and tools for your agent.
Add the badge to your site
Show visitors that nostrings is listed here — it’s also the link we check for a free listing.
HTML — for your website
<a href="https://serverdex.io/server/io-github-vpatel9202-nostrings?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="nostrings — listed on Serverdex" width="123" height="40" loading="lazy"></a>Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.
Markdown — for your README
[](https://serverdex.io/server/io-github-vpatel9202-nostrings?utm_source=badge)Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.
Install buttons — for your README
[](https://serverdex.io/install/cursor/io-github-vpatel9202-nostrings) [](https://serverdex.io/install/vscode/io-github-vpatel9202-nostrings) [](https://serverdex.io/install/claude-code/io-github-vpatel9202-nostrings)One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.
Install buttons — HTML for your docs
<a href="https://serverdex.io/install/cursor/io-github-vpatel9202-nostrings"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-vpatel9202-nostrings"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-vpatel9202-nostrings"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>Same buttons as plain links for a docs page or website.
Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).