Site vs Rootly MCP Server
A side-by-side look at the Site and Rootly MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SiteSupport & Service ManagementOutsourced IT Quotes: the site's own MCP server — dataset, enquiry (enquiry = a human handoff,...37FairAuth: not declaredVerdict: choose Site for support & service management work; choose Rootly MCP Server for support & service management as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
SChoose Site when
- You need dedicated capabilities in the Support & Service Management domain.
Choose Rootly MCP Server when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
ROOTLY_API_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Site | |
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 37/100 · Fair | 44/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | ROOTLY_API_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 45 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Site | View Rootly MCP Server |
Tools & capabilities
Site tools
No tool names declared yet. Check the project README from the listing page.
Rootly MCP Server 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.
Site
No confirmed install command for Site yet — follow the setup steps linked from its listing page rather than a guessed package name.
Rootly MCP Server
{
"mcpServers": {
"rootly-ai-labs-rootly-mcp-server": {
"command": "uvx",
"args": [
"--from",
"rootly-mcp-server",
"rootly-mcp-server"
],
"env": {
"ROOTLY_API_TOKEN": "YOUR_ROOTLY_API_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Site is categorized under Support & Service Management and uses an install path we have not confirmed yet. Rootly MCP Server belongs to Support & Service Management and uses a local stdio subprocess. Pick Site for support & service management work and Rootly MCP Server for support & service management.
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.
Site has no declared pricing — check the project's own site. Rootly MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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 site-197 and rootly-ai-labs-rootly-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Site has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Rootly MCP Server has 44/100 (Fair) with 1 views, 0 installs and 45 GitHub stars.