Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Squiggles is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Let your coding agent see the squiggles — LSP diagnostics, navigation, refactoring, and extras
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user squiggles-mcp '--' npx -y squiggles
# 2 — ask your agent for something these tools do
# goto_definition, goto_type_definition, goto_implementation and 25 more
Squiggles costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Squiggles as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user squiggles-mcp '--' npx -y squigglesReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
28 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Go to the definition of a symbol at the given position. Returns the file and location where the symbol is defined.
No parameter schema on file.
Go to the type definition of a symbol. Returns where the type of the symbol at the given position is defined.
No parameter schema on file.
Go to implementations of an interface or abstract method. Returns concrete implementation locations.
No parameter schema on file.
Go to the declaration of a symbol (relevant in C/C++ for header declarations).
No parameter schema on file.
Find all references to a symbol across the project. Returns every location where the symbol is used.
No parameter schema on file.
Get hover information (type signature, documentation) for a symbol at the given position.
No parameter schema on file.
Get parameter information for a function call at the given position.
No parameter schema on file.
Get all symbols (functions, classes, variables, etc.) defined in a file as a hierarchical tree.
No parameter schema on file.
Search for symbols across the entire project by name. Supports fuzzy matching.
No parameter schema on file.
Get available code actions (quick fixes, refactorings) at the given position. Diagnostics overlapping the range are passed to the server so quick fixes are included.
No parameter schema on file.
Format a file using the language server
No parameter schema on file.
Check if a symbol at the given position can be renamed, and get its current name.
No parameter schema on file.
Rename a symbol across all affected files. Returns the workspace edit, or applies it to disk when apply is true.
No parameter schema on file.
Find all functions/methods that call the function at the given position.
No parameter schema on file.
Find all functions/methods that are called by the function at the given position.
No parameter schema on file.
Get the type hierarchy (supertypes and subtypes) for the type at the given position.
No parameter schema on file.
Open a file in the LSP server. This triggers diagnostics and makes the file available for subsequent no-arg diagnostics calls.
No parameter schema on file.
Get current diagnostics (errors, warnings) for a file. If no file is specified, returns diagnostics for all currently open files with issues. Waits for fresh results after recent edits.
No parameter schema on file.
Get the USR and symbol details for the symbol at the given position
No parameter schema on file.
Show the Clang AST for a range in a C/C++ file
No parameter schema on file.
List the imports of a Go file and the package it belongs to
No parameter schema on file.
Add an import path to a Go file. Applies the change to disk.
No parameter schema on file.
Run go mod tidy for the module containing the given go.mod file
No parameter schema on file.
Run govulncheck to find known vulnerabilities in dependencies. May take a while on first run.
No parameter schema on file.
List Go modules found under a directory
No parameter schema on file.
Go to the source definition (the implementation, not the .d.ts declaration) of a symbol
No parameter schema on file.
Sort imports and remove unused ones in a TypeScript/JavaScript file. Applies the changes to disk.
No parameter schema on file.
Update all imports that reference a file after it has been moved or renamed on disk. Move the file first, then call this. Applies the changes to disk.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Squiggles or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.1.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Squiggles can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.