AI vs Site
A side-by-side look at the AI and Site MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SiteDeveloper ToolsSR&ED Finder: the site's own MCP server — compare, enquiry (enquiry = a human handoff, not a...43FairAuth: no auth requiredVerdict: choose AI for developer tools work as a local process; choose Site for developer tools. 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.
- You prefer a local stdio subprocess transport.
SChoose Site when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Site | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 53/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner |
Tools & capabilities
AI tools
No tool names declared yet. Check the project README from the listing page.
Site 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
{
"mcpServers": {
"contentrain-ai": {
"command": "npx",
"args": [
"-y",
"contentrain"
]
}
}
}
Site
No confirmed install command for Site yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
AI is categorized under Developer Tools and uses a local stdio subprocess. Site belongs to Developer Tools and uses an install path we have not confirmed yet. Pick AI for developer tools work and Site 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. Site has no confirmed install command yet — follow its own setup instructions.
AI has no declared pricing — check the project's own site. Site has no declared pricing — check the project's own site. Auth: no auth required. 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 site-259 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. Site has 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.