A side-by-side look at the AI and Dogg World Check MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AI for developer tools work as a local process; choose Dogg World Check for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose AI when
You need dedicated capabilities in the Developer Tools domain.
No tool names declared yet. Check the project README from the listing page.
Dogg World Check tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
AI is categorized under Developer Tools and uses a local stdio subprocess. Dogg World Check belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick AI for developer tools work and Dogg World Check for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
AI has no declared pricing — check the project's own site. Dogg World Check has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add contentrain-ai and dogg-world-check as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AI has a quality signal of 53/100 (Good) with 3 views, 0 installs and 6 GitHub stars. Dogg World Check has 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.