What is the key difference between Odoo Pulse and Teamwork MCP?

Odoo Pulse belongs to the Workplace & Productivity category with local stdio execution, while Teamwork MCP belongs to the Workplace & Productivity category with local stdio execution.

How do I install Odoo Pulse or Teamwork MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Odoo Pulse and Teamwork MCP free or paid?

Odoo Pulse operates under a BYOK (Pay Provider Direct) model (API Key required). Teamwork MCP operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Odoo Pulse lists 6 tools with 2 views and 1 GitHub stars. Teamwork MCP lists 5 tools with 2 views and 25 GitHub stars.

Can I use both Odoo Pulse and Teamwork MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Odoo Pulse vs Teamwork MCP

In-depth architectural comparison of the Odoo Pulse and Teamwork 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: 49/100 (Fair) | Auth: API Key required

Teamwork MCP

Workplace & Productivity · Local stdio

Quality: 52/100 (Good) | Auth: API Key required

Verdict Summary: Choose Odoo Pulse if you need specialized Workplace & Productivity tools running via a local process. Choose Teamwork 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.
Primary tools included: Single-call structured reports with verdicts (on-track, at-risk, off-track), Supports multiple business domains: sales, CRM, inventory, procurement, production, projects, Timezone offset handling for date bucketing.

Explore Odoo Pulse Details

Choose Teamwork MCP 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)).

Feature & Specification Comparison

Specification	Odoo Pulse minhhq-a1 Workplace & Productivity	Teamwork MCP teamwork Workplace & Productivity
Summary	An AI Business Analyst for Odoo ERP: one-call reports with a verdict (businesspulse, pipelinereview, receivableshealth, inventoryrisk, salessnapshot, absenceoverview) over the XML-RPC API.	Project and resource management platform that keeps your client projects on track, makes managing resources a breeze, and keeps your profits on point.
Category & Scope	Workplace & Productivity

Tools & Capabilities Breakdown

Odoo Pulse Tools (6)

Single-call structured reports with verdicts (on-track, at-risk, off-track)

Supports multiple business domains: sales, CRM, inventory, procurement, production, projects

Timezone offset handling for date bucketing

Configurable verdict thresholds and company filters

Read-only by default with controlled write operations

Works over Odoo XML-RPC API without Odoo-side installation

Teamwork MCP Tools (5)

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 Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "minhhq-a1-odoo-pulse": {
      "command": "uvx",
      "args": [
        "odoo-pulse"
      ],
      "env": {
        "ODOO_URL": "YOUR_ODOO_URL_HERE",
        "ODOO_DB": "YOUR_ODOO_DB_HERE",
        "ODOO_USERNAME": "YOUR_ODOO_USERNAME_HERE",
        "ODOO_API_KEY": "YOUR_ODOO_API_KEY_HERE",
        "ODOO_READ_ONLY": "YOUR_ODOO_READ_ONLY_HERE",
        "ODOO_WRITABLE_MODELS": "YOUR_ODOO_WRITABLE_MODELS_HERE",
        "ODOO_ALLOW_DELETE": "YOUR_ODOO_ALLOW_DELETE_HERE"
      }
    }
  }
}

Teamwork MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "teamwork-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ],
      "env": {
        "TW_MCP_SERVER_ADDRESS": "YOUR_TW_MCP_SERVER_ADDRESS_HERE",
        "TW_MCP_BEARER_TOKEN": "YOUR_TW_MCP_BEARER_TOKEN_HERE",
        "NODE_EXTRA_CA_CERTS": "YOUR_NODE_EXTRA_CA_CERTS_HERE"
      }
    }
  }
}

Frequently Asked Questions

Odoo Pulse is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Teamwork MCP belongs to Workplace & Productivity using local stdio subprocess. Select Odoo Pulse when you need capabilities focused on workplace & productivity and Teamwork MCP when you require tools for workplace & productivity.

More alternatives to Odoo Pulse More alternatives to Teamwork MCP Workplace & Productivity category hub