In-depth architectural comparison of the Jobber MCP and Google Workspace MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Jobber MCP
Workplace & Productivity · Local stdio
Quality: 52/100 (Good) | Auth: OAuth 2.0
Google Workspace MCP
Workplace & Productivity · Local stdio
Quality: 59/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Jobber MCP if you need specialized Workplace & Productivity tools running via a local process. Choose Google Workspace MCP if your workspace requires Workplace & Productivity integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Jobber MCP when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Paid Service).
You have access to required keys: JOBBER_CLIENT_ID, JOBBER_CLIENT_SECRET.
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_OAUTH_REDIRECT_URI, WORKSPACE_MCP_LOG_LEVEL, WORKSPACE_MCP_PORT, WORKSPACE_MCP_HOST.
Customer-hosted, read-only MCP server for Jobber operations queries: owner action lists, overdue invoices, stale requests, estimates, jobs, and safe read-only GraphQL validation.
Comprehensive Google Workspace MCP server with full support for Google Calendar, Drive, Gmail, and Docs, Forms, Chats, Slides and Sheets over stdio, Streamable HTTP and SSE transports.
Category & Scope
Tools & Capabilities Breakdown
Jobber MCP Tools (6)
jobber_auth_url
create the one-time Jobber OAuth authorization link for a customer-hosted install.
jobber_exchange_code
exchange the redirected OAuth code and store tokens locally without exposing them in chat.
jobber_refresh_token
refresh the stored access token for continued read-only reporting.
jobber_account
validate the connected account before running operational queries.
jobber_clients_sample
validate read access with a capped client sample.
jobber_graphql_read
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Jobber MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Google Workspace MCP belongs to Workplace & Productivity using local stdio subprocess. Select Jobber MCP when you need capabilities focused on workplace & productivity and Google Workspace MCP when you require tools for workplace & productivity.
Primary tools included: Full coverage of 12 major Google Workspace services with 120+ tools, OAuth 2.1 multi-user authentication with external auth passthrough support, Supports stdio, streamable HTTP, and SSE transports.