SiteData MCP vs Aria Icons
A side-by-side look at the SiteData MCP and Aria Icons MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SiteData MCPDeveloper ToolsWebsite traffic, DR growth and payment rankings; manage website and keyword favorites via OAuth.33EmergingAuth: oauth 2.0Verdict: choose SiteData MCP for developer tools work; choose Aria Icons for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
SChoose SiteData MCP when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: OAuth 2.0.
Choose Aria Icons when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S SiteData MCP | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 33/100 · Emerging | 47/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | OAuth 2.0 | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner |
Tools & capabilities
SiteData MCP tools
No tool names declared yet. Check the project README from the listing page.
Aria Icons 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.
SiteData MCP
No confirmed install command for SiteData MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Aria Icons
{
"mcpServers": {
"aria-icons": {
"command": "npx",
"args": [
"-y",
"aria-icons@latest"
]
}
}
}
Frequently asked questions
SiteData MCP is categorized under Developer Tools and uses an install path we have not confirmed yet. Aria Icons belongs to Developer Tools and uses a local stdio subprocess. Pick SiteData MCP for developer tools work and Aria Icons 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. SiteData MCP has no confirmed install command yet — follow its own setup instructions.
SiteData MCP has no declared pricing — check the project's own site. Auth: oauth 2.0. Aria Icons is listed as free. 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 sitedata-mcp and aria-icons as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SiteData MCP has a quality signal of 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Aria Icons has 47/100 (Fair) with 2 views, 0 installs and 87 GitHub stars.