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.
IFSSE server crashes with 'Not connected' error after a few seconds when started via npx
THENMove notification timers from server creation to start only after a client connects to the SSE endpoint. In the server setup, use an event listener for the 'connect' event to begin sending periodic messages, ensuring that the server does not attempt to send notifications before any client is connected.
IFMCP server fails to initialize in Claude Desktop with error 'SyntaxError: Unexpected token 'E', "Error: typ"... is not valid JSON'.
THENEnsure that all outputs from the MCP server, including error messages, are valid JSON-RPC responses. Wrap any non-JSON error strings in a proper JSON-RPC error object with 'jsonrpc', 'id', and 'error' fields. For example, use '{"jsonrpc": "2.0", "id": null, "error": {"code": -32000, "message": "Error description"}}' instead of raw text.
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