Alpenglow MCP Bridge
Connect Claude Desktop (or any MCP client) to your Odoo instance through the Alpenglow MCP Connector.
The bridge runs locally on your machine and translates MCP stdio protocol into HTTP requests to your Odoo server. All business logic, access control, and rate limiting stay on the server.
Prerequisites
- An Odoo 19 instance with the Alpenglow MCP Connector module installed
- An API key generated through the Alpenglow setup wizard
- Python 3.10+ (or install via
uv/uvxwhich handles this automatically)
Quick start
Option A: Run with uvx (recommended)
Install uv if you don't have it, then run:
uvx alpenglow-mcp-bridge --url https://your-odoo.com --token YOUR_API_KEY
Option B: Install with pip
pip install alpenglow-mcp-bridge
alpenglow-mcp-bridge --url https://your-odoo.com --token YOUR_API_KEY
Claude Desktop configuration
Add this to ~/.claude/claude_desktop_config.json:
{
"mcpServers": {
"alpenglow-odoo": {
"command": "uvx",
"args": [
"alpenglow-mcp-bridge",
"--url", "https://your-odoo.com",
"--token", "YOUR_API_KEY"
]
}
}
}
Environment variables
Instead of CLI flags, you can set:
ALPENGLOW_URL— Odoo instance URLALPENGLOW_TOKEN— API key
Available tools
| Tool | Description |
|---|---|
alpenglow_list_models |
List available Odoo models |
alpenglow_describe |
Get full schema for a model |
alpenglow_search |
Search records with filters and pagination |
alpenglow_read |
Read records by ID |
alpenglow_create |
Create new records |
alpenglow_update |
Update existing records |
alpenglow_delete |
Delete records |
alpenglow_aggregate |
Run reporting queries (count, sum, avg, group_by, trend, etc.) |
alpenglow_execute |
Call whitelisted ORM methods |
License
MIT
Metadata
Release files for alpenglow-mcp-bridge 1.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| alpenglow_mcp_bridge-1.0.4.tar.gz | 5.5 kB | Without provenance | Details for alpenglow_mcp_bridge-1.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| alpenglow_mcp_bridge-1.0.4-py3-none-any.whl | Python 3 | none | any | Details for alpenglow_mcp_bridge-1.0.4-py3-none-any.whl |
Total release size: 12.4 kB
Release files / alpenglow_mcp_bridge-1.0.4.tar.gz
| Download URL | alpenglow_mcp_bridge-1.0.4.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f535dcb4c108c00a729fb68ed75adb7edd82d4936d4b5219e30ad4fff7dbc769
|
|
BLAKE2b-256 checksum How to use checksums |
e833c75c5053b79e653fdca2d048872d4d2aa0b2d3ee7bf8d8a39ae30db66882
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.15 {"installer":{"name":"uv","version":"0.11.15","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / alpenglow_mcp_bridge-1.0.4-py3-none-any.whl
| Download URL | alpenglow_mcp_bridge-1.0.4-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0d47ba3b6bb8e066c42fedba67a865b8891dcb1a68f8dbeb4cc9672ae4835477
|
|
BLAKE2b-256 checksum How to use checksums |
b10f8b128889aa731818e5103dbe97919d74b2e9a50fdf18fe218f0fafd3aa16
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.15 {"installer":{"name":"uv","version":"0.11.15","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for alpenglow-mcp-bridge 1.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.