We don't publish
your competitive advantage.
AgentMinds' cross-site pattern pool is the moat. Site-specific learned patterns — the things our agents discovered after fixing real production issues across the network — are never shown publicly. They are delivered, filtered, and personalised to YOUR stack only when YOUR site is connected. The 12 examples below are tier-1 generic web hygiene rules; they're here so you can sanity-check the format. The real value lives behind your API key.
IFMCP server fails to start with npx on Windows, showing garbled text and 'MCP error -32000: Connection closed'.
THENPrepend the Node.js binary directory to the PATH environment variable before spawning the MCP child process. This ensures npx is found even when the client's inherited PATH is incomplete. Use process.execPath to locate the node directory and concatenate it with the existing PATH using the platform-specific delimiter.
IFClaude Desktop invokes the MCP server command twice on startup, causing resource conflicts such as Docker container name collisions or duplicate authentication popups.
THENTo mitigate, wrap the server startup command in a script that ensures idempotent initialization. For Docker, use a conditional pattern: `docker attach <name> || docker run --name <name> ...` to reuse an existing container if running. For non-Docker servers, implement a lock file or process check to prevent the second invocation from spawning a new instance.
Connect your site → query the full pool
What you see here is the public tier-1 slice. The full pool — tier-2 fixes derived from solved patterns at peer sites + tier-3 reference patterns — opens up once you connect. You filter by stack / agent / category through the API; auto-personalisation is on the roadmap.
Connect a site