mysid

A small, fast code-intelligence tool for LLM agents and developers. One Rust binary that works as a command line and as an MCP server. It answers questions about a codebase in a few lines instead of dumping files, edits safely, builds, and keeps an audit trail, so an agent spends tokens on the task and not on the tooling.

Install

Windows (PowerShell), prebuilt binary, no Rust needed:

irm https://raw.githubusercontent.com/bypreetham/mysid-mcp/main/install.ps1 | iex

macOS and Linux, prebuilt binary, no Rust needed:

curl -fsSL https://raw.githubusercontent.com/bypreetham/mysid-mcp/main/install.sh | sh

Then open a new terminal and run mysid help. Both put mysid on your PATH and register the MCP server for Claude Code, Claude Desktop and Antigravity/Gemini when they are installed. INSTALL.md has the options, how to check it, and a fix for each failure. From a clone, .\install.ps1 builds from source when Rust is installed.

MCP clients (Claude Desktop, Antigravity/Gemini, Cursor, Cline): { "mcpServers": { "mysid": { "command": "mysid", "args": [] } } }

For agents: let Claude install it

Copy everything in the box below into Claude Code (or any assistant that can run commands). It downloads the latest prebuilt mysid for this system from GitHub Releases (no Rust, no clone), puts it on PATH, registers the MCP server and checks that it works.

Install mysid on this machine and set it up. The latest build is published at
https://github.com/bypreetham/mysid-mcp/releases/tag/latest

1. If `mysid help` already runs, skip to step 3.
2. Install, by system (the details and every failure fix are in https://github.com/bypreetham/mysid-mcp/blob/main/INSTALL.md):
   - Windows (PowerShell):
       irm https://raw.githubusercontent.com/bypreetham/mysid-mcp/main/install.ps1 | iex
     It copies mysid.exe to %LOCALAPPDATA%\mysid\bin and adds that folder to my user PATH.
   - macOS or Linux:
       curl -fsSL https://raw.githubusercontent.com/bypreetham/mysid-mcp/main/install.sh | sh
     It picks the build for this system (Linux or macOS, x86_64 or arm64), checks its checksum, copies it to ~/.local/bin
     and adds that folder to my shell profile when it is not on PATH.
   Both scripts check that the download runs before replacing anything, and register the MCP server for Claude Code, Claude
   Desktop and Antigravity/Gemini when they are installed. Without the `claude` command they edit ~/.claude.json (if it exists,
   after a backup). If Claude Code still does not list mysid, run:  claude mcp add --scope user mysid -- mysid
3. Check it in a NEW terminal (this one has the old PATH): `mysid help` must print "mysid: code intelligence for LLM agents"
   and a numbered command list. If the command is not found, tell me which folder it was installed to and fix PATH.
4. Other MCP clients: add { "mcpServers": { "mysid": { "command": "mysid", "args": [] } } } to their config.
5. Tell me to restart the client, and that inside a project folder the first command is `mysid set .`, then `mysid help`.

Rules: change only what these steps say. Do not commit, push or edit any project. Do not touch my other MCP servers or
settings. Do not add yourself as an author or co-author anywhere. Report each step as done or failed, with the error text.

If there is no prebuilt file for a system (the installer says so), build from source: clone the repository, run cargo build --release in rust-mcp, and copy target/release/mysid to a folder on PATH.

To update later, run the same installer again (it replaces the running copy safely) and reload the MCP client. Every file on the release has its checksum in SHA256SUMS.

Related MCP server: agentmako

The usual flow

Run it from inside the project folder. mysid finds the project from there, so several agents can work on several projects at once. mysid set <path> is optional.

mysid list src/ui                 what is in a folder
mysid overview Player.kt          the outline: types and signatures, no code
mysid read Player.kt              the code (first 120 lines);  Player.kt#L121-240 for more;  or a symbol name
mysid search "retries" --types kt where is it
mysid graph StreamResolver        who calls it, what it calls  (no argument: where the code lives)
mysid apply  /  mysid patch ...   edit: many changes at once, or one exact replacement
mysid write src/New.kt --file x   new file (no shell quoting: stdin or --file)
mysid check  /  mysid build       verify: errors only
mysid checkpoint -> edits -> mysid diff -> mysid commit "msg"       undo: mysid restore --yes

File names, not paths (Player.kt). Output is capped and prints short names. Failures start with NOT PATCHED, NOT APPLIED, NOT WRITTEN and exit with status 1. Nothing is ever pushed.

For models

• mysid help is the flow above. mysid help --claude shows it in Claude Code's own tool names.

• mysid skill base | android | react print short workflow guides; mysid skill install writes them as Claude Code skills.

• Android commands (build stages, release, devices, Wi-Fi, device logs) are taught by mysid skill android.

What is inside

Build from source

cd rust-mcp
cargo build --release      # rust-mcp/target/release/mysid.exe
cargo test

Layout: rust-mcp/src/ (main.rs starts the command line or the MCP server; cli/ argument parsing and output, dispatch.rs command name to handler, help/ the help text, mcp/ the MCP server and its tool list; tools/ the commands, grouped in file/, build/ (build, release, install, exec), scanner/ (read, search, overview, symbols, tree), scaffold/, android/, vcs/, graph/, doctor/; index/ the code index, textindex/ the search index, parsers/ per language, adapters/ per stack), rust-mcp/skills/ the guides built into the binary, README/ the documentation.

Why "mysid"?

A mysid is a small, adaptable crustacean that moves through complex water and finds what it needs. The tool does the same in a codebase: small, quick, and good at finding the right context.

Apache 2.0, see LICENSE.