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.
IFNeed to connect a local MCP server (e.g., filesystem server) to Claude Desktop.
THENEdit the claude_desktop_config.json file to add an 'mcpServers' entry with the server command, args, and allowed directory paths. Restart Claude Desktop. The server will appear in the interface as a hammer icon.
IFMCP client logs 'Unexpected end of JSON input' when attempting to connect to a server, especially if the server command is set to a non-MCP executable like 'echo'.
THENReplace the placeholder command (e.g., 'echo') with the actual MCP server process (e.g., 'npx', 'uvx', or a full path to the server binary). For PostgreSQL, use a command like 'npx -y @modelcontextprotocol/server-postgres' followed by a valid connection URI. Remove any nested server objects (e.g., 'server': { 'type': 'tcp', ... })—they are not part of the standard MCP configuration schema.
IFMCP server logs show 'Unexpected end of JSON input' and transport closes immediately after initialization.
THENFix the MCP server configuration by ensuring the `command` field points to a proper MCP server executable (e.g., `uvx` or `npx` with the correct server package) and that the `args` array is present and valid. Remove any nested `server` or `protocol` objects that are not part of the stdio MCP server spec.
IFNeed to enable the Sequential Thinking tool in an MCP host like Claude Desktop, VS Code, or Codex CLI.
THENAdd the server configuration to the host's MCP config file (e.g., claude_desktop_config.json) using either npx or docker command as shown. Ensure the server is restarted to pick up the new tool.
IFNeed to give Claude Desktop or any MCP-compatible AI access to GPU-accelerated AI services.
THENAdd the gpu-bridge MCP server to your Claude Desktop configuration by modifying the `claude_desktop_config.json` file to include the `@gpu-bridge/mcp-server` package with your API key. Restart Claude Desktop to enable 30 GPU-powered tools.
IFMCP server fails to start when launched via npx, showing garbled error text and 'MCP error -32000: Connection closed'.
THENEnsure the environment PATH variable passed to the child process includes the Node.js bin directory (the directory containing npx). When spawning the MCP server command, prepend the Node.js executable path's directory to the inherited PATH. This ensures npx can be found even if the parent process has a restricted PATH.
IFMCP server fails to initialize in Claude Desktop with JSON parse error "Unexpected token 'E', 'Error: typ'... is not valid JSON"
THENAdd the `--directory` argument to the `uv` command in claude_desktop_config.json to specify the project root directory containing the server script. This ensures UV resolves the correct Python path and dependencies. For example: use `uv --directory /path/to/project run --with mcp mcp run /path/to/project/server.py`.
IFError initializing MCP server: Connection closed when using MCPServerStdio with args ["-y", "codex", "mcp"]
THENChange the command argument from "codex mcp" to "codex mcp-server" in the MCPServerStdio instantiation. This ensures Codex CLI starts as an MCP server instead of displaying help for the /mcp directive.
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