When something fails.
The common problems, each with its fix. Most come down to a tool that needs a fresh window.
Updated . Struq skill 0.5.0.
The skill does not show up
Open a new session: most tools read their skills when they start. Still missing? Run the install with your tool’s flag, for example npx @struq/skill@latest --cursor, and read what it prints: one line per tool, with where the skill went.
It installed into the wrong tool
When the installer finds no AI tool, it installs into Claude Code. Name your tool with its flag instead: --cursor, --codex, --opencode, --gemini, --copilot or --windsurf.
The install command fails
The installer needs Node 18 or newer. Check with node --version and update Node if it is older.
Struq does not appear in my client
Open a new window: most clients read their MCP servers only when they start. In Cursor, approve the connection afterwards under Settings, then MCP. In Windsurf and Antigravity the key is serverUrl, not url.
I only see four tools
That is a free account: the four catalogue tools. Just moved to Pro? Connect again so your client picks up the rest.
The tools that save are missing
You allowed read only at sign-in. Revoke the connection in your Struq account under AI connections, then connect again and allow saving.
I have to sign in again
On the first connection that is expected. Later, it means the sign-in expired or was revoked. Connect again.
I use Claude on a free plan
Custom connectors in the Claude app need a paid Claude plan. Use Struq through Claude Code instead.
A tool returns an error
Try again after a minute. If it keeps failing, email [email protected] with the tool name and the time.