Site Rep MCP vs Invgate Service Desk MCP
A side-by-side look at the Site Rep MCP and Invgate Service Desk MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
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 Rep MCP for support & service management work; choose Invgate Service Desk MCP 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 Rep MCP when
- You need dedicated capabilities in the Support & Service Management domain.
- Its auth model fits you: No auth required.
Choose Invgate Service Desk MCP 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:
INVGATE_BASE_URL, INVGATE_API_TOKEN, INVGATE_API_USERNAME, INVGATE_WRITE_PROFILE, INVGATE_ENABLE_WRITES, INVGATE_TELEMETRY, INVGATE_TELEMETRY_DETAIL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Site Rep MCP | |
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 39/100 · Fair | 48/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | INVGATE_BASE_URLINVGATE_API_TOKENINVGATE_API_USERNAMEINVGATE_WRITE_PROFILEINVGATE_ENABLE_WRITESINVGATE_TELEMETRYINVGATE_TELEMETRY_DETAIL |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 4 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Site Rep MCP | View Invgate Service Desk MCP |
Tools & capabilities
Site Rep MCP tools
No tool names declared yet. Check the project README from the listing page.
Invgate Service Desk 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 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.
Invgate Service Desk MCP
{
"mcpServers": {
"tracegazer-invgate-service-desk-mcp": {
"command": "uvx",
"args": [
"invgate-service-desk-mcp"
],
"env": {
"INVGATE_BASE_URL": "YOUR_INVGATE_BASE_URL_HERE",
"INVGATE_API_TOKEN": "YOUR_INVGATE_API_TOKEN_HERE",
"INVGATE_API_USERNAME": "YOUR_INVGATE_API_USERNAME_HERE",
"INVGATE_WRITE_PROFILE": "YOUR_INVGATE_WRITE_PROFILE_HERE",
"INVGATE_ENABLE_WRITES": "YOUR_INVGATE_ENABLE_WRITES_HERE",
"INVGATE_TELEMETRY": "YOUR_INVGATE_TELEMETRY_HERE",
"INVGATE_TELEMETRY_DETAIL": "YOUR_INVGATE_TELEMETRY_DETAIL_HERE"
}
}
}
}
Frequently asked questions
Site Rep MCP is categorized under Support & Service Management and uses an install path we have not confirmed yet. Invgate Service Desk MCP belongs to Support & Service Management and uses a local stdio subprocess. Pick Site Rep MCP for support & service management work and Invgate Service Desk MCP 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 Rep MCP has no confirmed install command yet — follow its own setup instructions.
Site Rep MCP has no declared pricing — check the project's own site. Auth: no auth required. Invgate Service Desk MCP 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-rep-mcp and tracegazer-invgate-service-desk-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Site Rep MCP has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Invgate Service Desk MCP has 48/100 (Fair) with 2 views, 0 installs and 4 GitHub stars.