Troubleshooting¶

Solutions for common issues when setting up or using the Alpenglow MCP Connector.

Bridge won't start / "command not found"¶

If uvx is not recognized, uv is not installed or not on your PATH. Reinstall (see Install the Bridge) and restart your terminal.

To verify the bridge can reach your Odoo server, run it manually:

uvx alpenglow-mcp-bridge --url https://your-odoo.com --db your-database --token YOUR_KEY

If it starts without errors, the connection is working. Press ++ctrl+c++ to stop.

"No database is selected"¶

Your Odoo server hosts multiple databases and the bridge doesn't know which one to use. Add the --db flag with your database name:

uvx alpenglow-mcp-bridge --url https://your-odoo.com --db my_production_db --token YOUR_KEY

If you used the setup wizard, --db is already included in the generated config.

Module won't install: `defusedxml` not met¶

Install the package in your Odoo server's Python environment:

pip install defusedxml

If you use a system-packaged Odoo, you may need sudo pip install defusedxml or install via your OS package manager.

"MCP access is not enabled"¶

Go to Settings > General Settings > Alpenglow MCP and toggle Enable MCP Access on. Or run the setup wizard.

"Authentication required" / 403 errors¶

Check that:

The API key is correct and included in the --token flag.
The credential has not been revoked (check the Credentials screen).
The credential has not expired.
The linked Odoo user account is active.

"Rate limit exceeded" / 429 errors¶

Wait for the rate limit window to reset (shown in the X-RateLimit-Reset response header). To increase limits, go to Settings > General Settings > Alpenglow MCP > Rate Limiting.

Model not found / access denied for a model¶

The model must be registered as an MCP resource with the appropriate operation enabled. Go to Settings > Alpenglow MCP > Resources and verify:

The model is listed and active (not archived).
The required operation (read/create/write/delete) is toggled on.
If the resource is in Read-Only mode, only read operations are allowed.

Fields missing from response¶

If a resource uses an Allowlist field policy, only the specified fields are returned. Check the resource's field policy and field list. With a Denylist policy, the listed fields are excluded from responses.

Records not visible¶

If a resource has a Record Filter domain, only records matching that domain are accessible. Check the filter on the resource form. Also verify that the Odoo user linked to the credential has the necessary ir.model.access and ir.rule permissions to see those records.

Claude Desktop: wrong config file (Windows)¶

If Claude Desktop was installed from the Microsoft Store, it reads its config from a different location than the standard install:

Install type	Config path
Standard	`%APPDATA%\Claude\claude_desktop_config.json`
Microsoft Store	`%LOCALAPPDATA%\Packages\Claude_<id>\LocalCache\Roaming\Claude-3p\claude_desktop_config.json`

Tip

Use Settings > Developer > Edit Config inside Claude Desktop to open the correct file automatically, regardless of install type.