Site vs Site Rep MCP
A side-by-side look at the Site and Site Rep MCP 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 declaredS
Site Rep MCPSupport & Service ManagementRead-only Site Rep handoff: agent brief, pending work, first-customer receipt with payment evidence.39FairAuth: no auth requiredVerdict: choose Site for support & service management work; choose Site Rep MCP for support & service management. 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.
SChoose Site Rep MCP when
- You need dedicated capabilities in the Support & Service Management domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Site | S Site Rep MCP |
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 37/100 · Fair | 39/100 · Fair |
| Install command | Not confirmed yet | Not confirmed yet |
| Transport | — | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Site | View Site Rep MCP |
Tools & capabilities
Site tools
No tool names declared yet. Check the project README from the listing page.
Site Rep MCP 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.
Site Rep MCP
No confirmed install command for Site Rep MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Site is categorized under Support & Service Management and uses an install path we have not confirmed yet. Site Rep MCP belongs to Support & Service Management and uses an install path we have not confirmed yet. Pick Site for support & service management work and Site Rep MCP for support & service management.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
Site has no declared pricing — check the project's own site. Site Rep MCP 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 site-197 and site-rep-mcp 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. Site Rep MCP has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.