FRENES

Developer tools · MCP server

Squiggles: MCP server, setup and security

Squiggles is an open-source MCP server that lets an AI agent run LSP diagnostics navigate to definitions and rename symbols across servers. Its repository has 6 stars and its last commit is from September 25, 2026 and it is licensed under MIT.

Actively maintained

What Squiggles does

According to its repository: “Run any number of LSP servers from one YAML config for diagnostics, go-to-definition and rename, plus server-specific features like Rust macro expansion.”

An MCP server gives an AI agent extra tools it calls during the conversation: the agent reads their description, decides to use them and gets the result back. Squiggles is listed under Developer tools, a category of 475 servers in the directory, where it ranks #425 by stars.

Topics declared by the repository: lsp, typescript.

Installing and connecting Squiggles

Distribution modes declared in the official MCP registry:

  • npm package (Node.js, usually started with npx)

Like any MCP server, you declare it in your client's configuration (Claude Desktop, Claude Code, Cursor, VS Code, Codex…): a name, the command that starts it or its URL, and any environment variables. The client then starts it and lists its tools. Project language: TypeScript.

Security: what to check

An MCP server runs code with the rights you give it, and the model reads its tool descriptions: a malicious or compromised server can hijack the agent. Read the code, or pick a maintained and widely used server, before connecting it.

None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Squiggles. That does not replace reading the code.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on February 12, 2026, the carldaws/squiggles repository has 6 stars and 1 forks, with 0 open issues. It has more stars than 17% of the servers in the directory. Last change 1 month ago. Version published in the registry: 1.0.2 (September 20, 2026).

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.

StorybookStorybook : 91.4K91.4KFront End ChecklistFront End Checklist : 74.6K74.6KTldrawTldraw : 51.1K51.1KCodebase MemoryCodebase Memory : 47.4K47.4KCCXTCCXT : 44.5K44.5KPostHog MCP ServerPostHog MCP Server : 40.4K40.4KClaude task masterClaude task master : 28.3K28.3KAgent Skills Search ServerAgent Skills Search Server : 26.6K26.6KSquigglesSquiggles : 66
GitHub stars of the most followed servers in the category (log scale); Squiggles in orange. Checked October 25, 2026.

Verdict

Squiggles is a reasonable choice; check the points below before connecting it.

Strengths

  • Active project: recent commit
  • Listed in the official MCP registry
  • Permissive licence (MIT)

Limitations

  • Few visible users

Frequently asked questions

How do I install Squiggles?

Squiggles is distributed as npm package (Node.js, usually started with npx). Add it to your client's MCP configuration (Claude Desktop, Cursor, VS Code…) following the README of carldaws/squiggles.

Is Squiggles free?

The code is published under the MIT licence and can be used free of charge.

Is Squiggles safe?

No risk signal found (system access, secrets, licence, abandonment). As with any MCP server, keep rights minimal and read the code before sensitive use.

Is it an official server?

Nothing says so: it is a project published by carldaws on GitHub. Check who maintains it before giving it access.

What are the alternatives to Squiggles?

In the same category: Radar Kubernetes MCP Server, Repowise, Jscpd, and Apify MCP server. Radar Kubernetes MCP Server and Repowise score higher on our grid.

Related articles

Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score