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.
IFI need to run an MCP server with a client that requires a specific transport (stdio, SSE, or streamable HTTP).
THENRun the server with the appropriate transport argument: 'stdio' (default), 'sse' (deprecated as of 2025-03-26), or 'streamableHttp'. For development from source, use the corresponding npm scripts: npm run start:sse (deprecated) or npm run start:streamableHttp. The streamable HTTP transport is the recommended replacement for SSE.
IFRemote MCP server fails to load on claude.ai; logs show GET method calls instead of POST; server uses latest protocol version (2025-03-26) but client uses older version.
THENEnsure your MCP server is backward-compatible by supporting the older SSE protocol. Implement both GET /sse (for SSE streaming) and POST /message (for JSON-RPC) endpoints. Use a version negotiation mechanism to fall back to the protocol version expected by the client. For claude.ai and Claude Desktop, target the 2024-11-05 protocol version if the client does not support 2025-03-26.
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