Google Workspace vs OrionCMD Checks
A side-by-side look at the Google Workspace and OrionCMD Checks MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
O
OrionCMD ChecksCommunication · Remote HTTP/SSEPay-per-call TLS certificate, DNS/email-auth and domain-expiry checks for any domain (x402 USDC).42FairAuth: not declaredVerdict: choose Google Workspace for communication work as a local process; choose OrionCMD Checks for communication over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Google Workspace when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET.
OChoose OrionCMD Checks when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | O OrionCMD Checks | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 51/100 · Good | 42/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Paid service |
| Required env vars | GOOGLE_CLIENT_IDGOOGLE_CLIENT_SECRET | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 191 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Google Workspace | View OrionCMD Checks |
Tools & capabilities
Google Workspace tools
No tool names declared yet. Check the project README from the listing page.
OrionCMD Checks 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.
Google Workspace
{
"mcpServers": {
"google-workspace-2": {
"command": "npx",
"args": [
"-y",
"@aaronsb/google-workspace-mcp"
],
"env": {
"GOOGLE_CLIENT_ID": "YOUR_GOOGLE_CLIENT_ID_HERE",
"GOOGLE_CLIENT_SECRET": "YOUR_GOOGLE_CLIENT_SECRET_HERE"
}
}
}
}
OrionCMD Checks
{
"mcpServers": {
"orioncmd-checks": {
"url": "https://api.orioncmd.com/llms.txt"
}
}
}
Frequently asked questions
Google Workspace is categorized under Communication and uses a local stdio subprocess. OrionCMD Checks belongs to Communication and uses a remote HTTP/SSE transport. Pick Google Workspace for communication work and OrionCMD Checks for communication.
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.
Google Workspace has no declared pricing — check the project's own site. OrionCMD Checks is listed as a paid service. 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 google-workspace-2 and orioncmd-checks as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Workspace has a quality signal of 51/100 (Good) with 1 views, 0 installs and 191 GitHub stars. OrionCMD Checks has 42/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.