The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Aidoo for Odoo listing page.
Connect any MCP client to your Odoo ERP through Aidoo.
aidoo-mcp is a small stdio bridge. It takes an Aidoo API key, opens an authenticated
session against the hosted Aidoo MCP server, and relays the Model Context Protocol
messages in both directions. Your assistant then queries, creates and updates Odoo
records in plain language, under the permissions carried by the key.
The Aidoo MCP server is hosted at https://mcp.aidoo.ai, and clients that support
remote connectors with OAuth or custom headers can reach it directly, with nothing to
install. Many MCP clients still speak stdio only, or offer no way to set an
Authorization header. This bridge fills that gap: one command, no local server,
no Odoo credentials on your machine.
The bridge is transparent. It never rewrites payloads, so every tool your workspace exposes is available the moment Aidoo ships it, with no update needed here.
aid_live_, created from the API keys page of your workspaceRun it without installing anything, with uv:
Or install it:
Prefer Node over Python? The npm/ directory ships the same bridge for
npx, with no Python dependency:
The command verifies that the endpoint answers, performs the MCP handshake and prints the tools your key grants:
~/Library/Application Support/Claude/claude_desktop_config.json on macOS,
%APPDATA%\Claude\claude_desktop_config.json on Windows:
~/.cursor/mcp.json:
~/.codeium/windsurf/mcp_config.json, same block as Cursor.
.vscode/mcp.json in your workspace:
Point it at the aidoo-mcp executable and pass the key through the environment. If the
client cannot set environment variables, use the flag instead:
Cursor, Windsurf and any client that does accept custom headers can also skip the
bridge entirely and target https://mcp.aidoo.ai/sse with an Authorization header.
See the Aidoo documentation.
| Option | Environment variable | Default |
|---|---|---|
--api-key | AIDOO_API_KEY | required |
--url | AIDOO_MCP_URL | https://mcp.aidoo.ai/mcp |
--transport | AIDOO_MCP_TRANSPORT | inferred from the URL path |
--timeout | AIDOO_MCP_TIMEOUT | 60 |
--retries | 3 |
Logs go to stderr, so they never interfere with the protocol stream on stdout. Exit
code 2 means a configuration problem, 1 a connection that could not be established.
No API key found The AIDOO_API_KEY variable did not reach the process. Client
configuration files often ignore your shell profile, so set the key in the env block
shown above.
Handshake fails with 401 The key was revoked, or its MCP permissions are disabled. Check it on the API keys page of your workspace.
The tool list is shorter than expected Tools follow the permissions of the key. Grant the missing ones, then restart your client.
Nothing happens in the client Restart the client completely after editing its
configuration, then look at its MCP logs. aidoo-mcp --check tells you within seconds
whether the problem is on your side or ours.
A corporate network blocks the connection The bridge needs outbound HTTPS on port
443 to mcp.aidoo.ai. Try --transport sse if an intermediate proxy mishandles
streamable HTTP.
MIT. See LICENSE.