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 works in the inspector but fails to connect in Claude Desktop, showing 'SyntaxError: Unexpected token 'E', "Error: typ"... is not valid JSON'.
THENAdd the `--directory` argument pointing to the project directory in the `claude_desktop_config.json` command, positioned before `run`. For example: `"args": ["--directory", "/path/to/project", "run", "--with", "mcp", "mcp", "run", "/path/to/project/server.py"]`. This ensures UV uses the correct working directory, resolving the JSON parsing error that occurs when it cannot find the project home directory.
IFNeed to integrate time/timezone functionality into an MCP client like Claude, VS Code, Zed, or Zencoder.
THENAdd the server configuration as shown in the official docs. The recommended method is using uvx with command 'uvx' and args ['mcp-server-time']. Alternative methods: Docker (image mcp/time) or pip install followed by python -m mcp_server_time. For custom system timezone, add --local-timezone=YOUR_TZ to the args.
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