In-depth architectural comparison of the Odoo Pulse 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
Odoo Pulse
Workplace & Productivity · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Google Workspace MCP
Workplace & Productivity · Local stdio
Quality: 67/100 (Great) | Auth: OAuth 2.0
Verdict Summary: Choose Odoo Pulse 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 Odoo Pulse when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: ODOO_URL, ODOO_DB, ODOO_USERNAME, ODOO_API_KEY, ODOO_READ_ONLY, ODOO_WRITABLE_MODELS, ODOO_ALLOW_DELETE.
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.
An AI Business Analyst for Odoo ERP: one-call reports with a verdict (businesspulse, pipelinereview, receivableshealth, inventoryrisk, salessnapshot, absenceoverview) over the XML-RPC API.
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
Odoo Pulse Tools (31)
odoo_version
Check connectivity and return the Odoo server version info.
list_models
List Odoo models (technical name + label). Optionally filter by a
case-insensitive substring matched against the model name or label,
e.g. 'sale', 'res.partner', 'invoice'.
get_model_fields
Inspect the schema of an Odoo model. Returns each field's label, type,
help text, requiredness and relation. Pass `fields` to limit the result
to specific field names. Example model: 'res.partner'.
search_read
Query records from an Odoo model.
Args:
model: Technical model name, e.g. 'sale.order', 'res.partner'.
domain: Odoo search domain as a list of triplets, e.g.
[["state", "=", "sale"], ["amount_total", ">", 1000]].
Use 'and'/'|' operators as Odoo expects. Defaults to all records.
fields: Field names to return. Omit to let Odoo decide (can be large).
limit: Max records (capped by ODOO_MAX_RECORDS).
offset: Pagination offset.
order: Sort spec, e.g. 'date_order desc'.
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).
Odoo Pulse 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 Odoo Pulse when you need capabilities focused on workplace & productivity and Google Workspace MCP when you require tools for workplace & productivity.
Count records in a model matching an Odoo domain filter.
read_records
Fetch specific records by their ids. Pass `fields` to limit columns.
aggregate_records
Group and aggregate records server-side (one call instead of pulling rows).
Args:
model: Technical model name, e.g. 'sale.order'.
group_by: One or more fields to group on. A field may carry a
granularity, e.g. 'date_order:month'.
measures: 'field:agg' specs. Bare 'field' means sum. Allowed
aggregators: sum, avg, min, max, count, count_distinct. Omit to
count records.
domain: Odoo search domain (list of triplets). Defaults to all records.
limit: Max groups (capped by ODOO_MAX_RECORDS).
offset: Pagination offset over groups.
order: Sort spec, e.g. 'amount_total desc'.
read_attachment
Read an ir.attachment: metadata always, base64 content when small enough.
Binary attachments under ODOO_MAX_ATTACHMENT_BYTES are returned with their
base64 `datas`; larger ones return metadata plus a warning. URL-type
attachments return the link, never binary data.
Args:
attachment_id: The ir.attachment id.
include_data: When False, return metadata only (no base64 fetch).
create_record
Create one record. Returns a preview unless confirm=True.
Args:
model: Odoo model name (must be in ODOO_WRITABLE_MODELS).
values: Field -> value mapping for the new record.
confirm: Set True to actually create; otherwise a dry-run preview.
update_records
Update one or more records. Returns a preview unless confirm=True.
Args:
model: Odoo model name (must be in ODOO_WRITABLE_MODELS).
ids: Record ids to update.
values: Field -> value mapping to write.
confirm: Set True to actually write; otherwise a dry-run preview.
delete_records
Delete one or more records. Returns a preview unless confirm=True.
Deletes also require ODOO_ALLOW_DELETE=true on the server.
Args:
model: Odoo model name (must be in ODOO_WRITABLE_MODELS).
ids: Record ids to delete.
confirm: Set True to actually delete; otherwise a dry-run preview.
create_lead
Create a CRM lead/opportunity (crm.lead). Preview unless confirm=True.
Use extra_values to set fields this helper doesn't model, including custom
mandatory fields (e.g. {"presales_id": 5}).
+19 more tools listed on main page
Google Workspace MCP Tools (123)
start_google_auth
Manually initiate Google OAuth authentication flow.
NOTE: This is a legacy OAuth 2.0 tool and is disabled when OAuth 2.1 is enabled.
The authentication system automatically handles credential checks and prompts for
authentication when needed. Only use this tool if:
1. You need to re-authenticate with different credentials
2. You want to proactively authenticate before using other tools
3. The automatic authentication flow failed and you need to retry
In most cases, simply try calling the Google Workspace tool you need - it will
automatically handle authentication if required.
search_gmail_messages
Searches messages in a user's Gmail account based on a query.
Returns both Message IDs and Thread IDs for each found message, along with Gmail web interface links for manual verification.
Supports pagination via page_token parameter.
get_gmail_message_content
Retrieves the full content (subject, sender, recipients, body) of a specific Gmail message.
Bodies are returned inline and truncated at 20,000 characters. Set full=True to
get the complete, untruncated message instead: it is exported to disk and the
response carries a short-lived download URL (HTTP transport) or file path (stdio
transport) rather than the body, so large messages never stream through the model
context. Stateless deployments have no file storage, so there full=True returns the
untruncated body inline.
get_gmail_messages_content_batch
Retrieves the content of multiple Gmail messages in a single batch request.
Supports up to 25 messages per batch to prevent SSL connection exhaustion.
get_gmail_attachment_content
Downloads an email attachment and saves it to local disk.
In stdio mode, returns the local file path for direct access.
In HTTP mode, returns a temporary download URL (valid for 1 hour).
May re-fetch message metadata to resolve filename and MIME type.
send_gmail_message
Sends an email using the user's Gmail account. Supports new emails, replies, and
forwards, with optional attachments. Supports Gmail's "Send As" feature to send
from configured alias addresses.
To forward an existing message, pass forward_message_id. The original subject,
body (quoted with a "Forwarded message" header), and attachments are carried over.
In forward mode, body (if any) is prepended as a note and subject is optional.
Threading, reply, and signature options do not apply when forwarding.
THIS TOOL SENDS IMMEDIATELY AND CANNOT SCHEDULE. Gmail's REST API exposes no
send-time parameter; Schedule send is a web-UI feature with no API equivalent,
so no argument to this tool can defer delivery. Never tell a user a message
was scheduled. For "prepare now, deliver later", create a draft with
draft_gmail_message. An external scheduler must retain the message data to
create and send a new message via send_gmail_message at the chosen time, or
call users.drafts.send with the draft ID returned by draft_gmail_message.
Alternatively, let the user schedule that draft in the Gmail UI.
draft_gmail_message
Creates a draft email in the user's Gmail account. Supports both new drafts and reply drafts with optional attachments.
Supports Gmail's "Send As" feature to draft from configured alias addresses.
SCHEDULED SEND IS NOT AVAILABLE. Gmail's REST API exposes no send-time
parameter; the Schedule send feature is web-UI only, and a message cannot be
placed in the Scheduled folder through the API. Do not claim a message was
scheduled. To deliver at a chosen time, create a draft with
draft_gmail_message. An external scheduler must retain the message data to
create and send a new message via send_gmail_message then, or call
users.drafts.send with the draft ID returned by draft_gmail_message.
Alternatively, let the user schedule the draft in the Gmail UI.
get_gmail_thread_content
Retrieves the complete content of a Gmail conversation thread, including all messages.
Optionally also returns structured ownership analysis so a caller can
determine who sent the last message and who owes whom a response without
re-parsing the formatted string or making a second tool call.
get_gmail_threads_content_batch
Retrieves the content of multiple Gmail threads in a single batch request.
Supports up to 25 threads per batch to prevent SSL connection exhaustion.
list_gmail_labels
Lists labels in the user's Gmail account.
manage_gmail_label
Manages Gmail labels: create, update, or delete labels.
list_gmail_filters
Lists all Gmail filters configured in the user's mailbox.