aidoo-mcp 0.1.0__tar.gz

aidoo_mcp-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,33 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+
+      - name: Install
+        run: uv sync --python ${{ matrix.python-version }}
+
+      - name: Lint
+        run: uv run ruff check .
+
+      - name: Check formatting
+        run: uv run ruff format --check .
+
+      - name: Test
+        run: uv run pytest -q

aidoo_mcp-0.1.0/.gitignore

@@ -0,0 +1,15 @@
+__pycache__/
+*.py[cod]
+.venv/
+venv/
+dist/
+build/
+*.egg-info/
+.pytest_cache/
+.ruff_cache/
+.coverage
+.DS_Store
+.env
+uv.lock
+key.pem
+*.pem

aidoo_mcp-0.1.0/CHANGELOG.md

@@ -0,0 +1,16 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project adheres to
+[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.1.0] - 2026-09-22
+
+### Added
+
+- stdio bridge to the hosted Aidoo MCP server, with bearer authentication
+- streamable HTTP and SSE upstream transports, selected automatically from the URL
+- `--check` command that verifies the endpoint, the handshake and the API key
+- configuration through `AIDOO_API_KEY`, `AIDOO_MCP_URL`, `AIDOO_MCP_TRANSPORT`
+  and `AIDOO_MCP_TIMEOUT`, each overridable on the command line
+- retries with backoff while the session is being established

aidoo_mcp-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,29 @@
+# Contributing
+
+Issues and pull requests are welcome.
+
+## Getting started
+
+```bash
+git clone https://github.com/eantoniomota/aidoo-mcp.git
+cd aidoo-mcp
+uv sync
+uv run pytest
+uv run ruff check .
+```
+
+## Ground rules
+
+- Keep the bridge transparent. It relays protocol messages and must not interpret,
+  rewrite or cache them. Tool behaviour belongs to the Aidoo server.
+- Every change that touches configuration or the relay comes with a test.
+- Run `ruff check .` and `ruff format .` before opening a pull request.
+- Never commit an API key, a log containing one, or a real Odoo hostname.
+
+## Reporting a bug
+
+Include your Python version, the output of `aidoo-mcp --check`, the name of your MCP
+client, and the relevant lines from its MCP log. Redact your API key.
+
+For anything related to the Aidoo platform itself rather than this bridge, use the
+support channels at [aidoo.ai](https://aidoo.ai/contact).

aidoo_mcp-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Aidoo
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

aidoo_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,250 @@
+Metadata-Version: 2.5
+Name: aidoo-mcp
+Version: 0.1.0
+Summary: Connect any MCP client to your Odoo ERP through Aidoo
+Project-URL: Homepage, https://aidoo.ai
+Project-URL: Documentation, https://aidoo.ai/docs
+Project-URL: Source, https://github.com/eantoniomota/aidoo-mcp
+Project-URL: Issues, https://github.com/eantoniomota/aidoo-mcp/issues
+Author-email: Aidoo <support@aidoo.ai>
+License: MIT License
+        
+        Copyright (c) 2026 Aidoo
+        
+        Permission is hereby granted, free of charge, to any person obtaining a copy
+        of this software and associated documentation files (the "Software"), to deal
+        in the Software without restriction, including without limitation the rights
+        to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+        copies of the Software, and to permit persons to whom the Software is
+        furnished to do so, subject to the following conditions:
+        
+        The above copyright notice and this permission notice shall be included in all
+        copies or substantial portions of the Software.
+        
+        THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+        IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+        FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+        AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+        LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+        OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+        SOFTWARE.
+License-File: LICENSE
+Keywords: aidoo,erp,mcp,model-context-protocol,odoo
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Office/Business
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.10
+Requires-Dist: anyio>=4.5
+Requires-Dist: mcp>=1.9
+Description-Content-Type: text/markdown
+
+# aidoo-mcp
+
+Connect any MCP client to your Odoo ERP through [Aidoo](https://aidoo.ai).
+
+`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.
+
+[![PyPI](https://img.shields.io/pypi/v/aidoo-mcp.svg)](https://pypi.org/project/aidoo-mcp/)
+[![Python](https://img.shields.io/pypi/pyversions/aidoo-mcp.svg)](https://pypi.org/project/aidoo-mcp/)
+[![License](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
+
+## Why a bridge
+
+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.
+
+```
+MCP client  <--stdio-->  aidoo-mcp  <--HTTPS-->  Aidoo  <--XML-RPC-->  Odoo
+```
+
+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.
+
+## Requirements
+
+- Python 3.10 or newer
+- An [Aidoo account](https://app.aidoo.ai/register) with an Odoo connection
+- An Aidoo API key, prefixed `aid_live_`, created from the API keys page of your workspace
+
+## Install
+
+Run it without installing anything, with [uv](https://docs.astral.sh/uv/):
+
+```bash
+uvx aidoo-mcp --check
+```
+
+Or install it:
+
+```bash
+pipx install aidoo-mcp
+# or
+pip install aidoo-mcp
+```
+
+## Check your setup
+
+```bash
+export AIDOO_API_KEY=aid_live_your_key_here
+aidoo-mcp --check
+```
+
+The command verifies that the endpoint answers, performs the MCP handshake and prints
+the tools your key grants:
+
+```
+[aidoo-mcp] https://mcp.aidoo.ai/health is reachable
+[aidoo-mcp] authenticated with https://mcp.aidoo.ai/mcp (transport=http, key=aid_live_...cdef)
+[aidoo-mcp] 8 tools available: aidoo_context, aidoo_create, aidoo_print, aidoo_query, ...
+```
+
+## Configure your client
+
+### Claude Desktop
+
+`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS,
+`%APPDATA%\Claude\claude_desktop_config.json` on Windows:
+
+```json
+{
+  "mcpServers": {
+    "aidoo": {
+      "command": "uvx",
+      "args": ["aidoo-mcp"],
+      "env": { "AIDOO_API_KEY": "aid_live_your_key_here" }
+    }
+  }
+}
+```
+
+### Cursor
+
+`~/.cursor/mcp.json`:
+
+```json
+{
+  "mcpServers": {
+    "aidoo": {
+      "command": "uvx",
+      "args": ["aidoo-mcp"],
+      "env": { "AIDOO_API_KEY": "aid_live_your_key_here" }
+    }
+  }
+}
+```
+
+### Windsurf
+
+`~/.codeium/windsurf/mcp_config.json`, same block as Cursor.
+
+### VS Code
+
+`.vscode/mcp.json` in your workspace:
+
+```json
+{
+  "servers": {
+    "aidoo": {
+      "type": "stdio",
+      "command": "uvx",
+      "args": ["aidoo-mcp"],
+      "env": { "AIDOO_API_KEY": "aid_live_your_key_here" }
+    }
+  }
+}
+```
+
+### Any other stdio client
+
+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:
+
+```bash
+aidoo-mcp --api-key aid_live_your_key_here
+```
+
+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](https://aidoo.ai/docs).
+
+## Usage
+
+```
+aidoo-mcp [--api-key KEY] [--url URL] [--transport {http,sse}]
+          [--timeout SECONDS] [--retries N] [--check] [--quiet]
+```
+
+| 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.
+
+## Ask your assistant
+
+```
+List the five quotations I sent last week that are still pending.
+Create a contact for Martin Dupont at Dupont SA, martin@dupont.fr.
+Generate the PDF of invoice INV/2026/0042.
+```
+
+## Security
+
+- The key is read from the environment or the command line and sent as a bearer token
+  over HTTPS. It is masked in every log line.
+- Odoo credentials stay in Aidoo. The bridge never sees them, and never talks to Odoo.
+- Each key carries its own permissions, and every call runs under the Odoo access
+  rules of the linked user. Grant only what the assistant needs.
+- Use one key per person, never a shared key, and revoke it from the dashboard if in doubt.
+- Report a vulnerability privately: see [SECURITY.md](SECURITY.md).
+
+## Troubleshooting
+
+**`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.
+
+## Development
+
+```bash
+uv sync
+uv run pytest
+uv run ruff check .
+uv run ruff format --check .
+```
+
+## License
+
+MIT. See [LICENSE](LICENSE).

aidoo_mcp-0.1.0/PUBLISHING.md

@@ -0,0 +1,79 @@
+# Publishing to the MCP Registry
+
+`server.json` describes the Aidoo server for the [official MCP Registry](https://registry.modelcontextprotocol.io).
+The registry stores metadata only, and the entry is what makes Aidoo discoverable from
+the clients and directories that read the registry.
+
+The server is published as **`ai.aidoo/aidoo`**, the reverse DNS form of `aidoo.ai`.
+That namespace is proven with a TXT record on the apex of the domain, signed by
+`key.pem`. The key never leaves the machine and is excluded from the repository: keep
+it in the password manager, because regenerating it means changing the DNS record.
+
+## Every release
+
+```bash
+mcp-publisher validate
+mcp-publisher login dns --domain aidoo.ai \
+  --private-key "$(openssl pkey -in key.pem -noout -text | grep -A3 priv | tail -n +2 | tr -d ' :\n')"
+mcp-publisher publish
+```
+
+Bump `version` in `server.json` first: the registry rejects a version that already
+exists. On macOS the system `openssl` is LibreSSL and cannot read Ed25519 keys, so use
+`/opt/homebrew/opt/openssl@3/bin/openssl`.
+
+## The DNS record
+
+```
+aidoo.ai.  IN  TXT  "v=MCPv1; k=ed25519; p=<public key>"
+```
+
+It sits on the **apex**, next to the SPF and Google records, never under a selector such
+as `_mcp-auth`. Regenerate the value with:
+
+```bash
+openssl pkey -in key.pem -pubout -outform DER | tail -c 32 | base64
+```
+
+## Retiring an entry
+
+A remote URL belongs to a single server entry, so republishing under a different name
+fails with `remote URL ... is already used` until the previous entry is retired:
+
+```bash
+mcp-publisher login github
+mcp-publisher status --status deleted --all-versions <old server name>
+```
+
+## Adding the PyPI package
+
+Once `aidoo-mcp` is on PyPI, add a `packages` block so clients can install the bridge
+from the registry entry. PyPI ownership is proven through the package metadata, so
+`pyproject.toml` needs this before the release that follows:
+
+```toml
+[project]
+keywords = ["mcp-name:ai.aidoo/aidoo"]
+```
+
+Then add to `server.json`:
+
+```json
+"packages": [
+  {
+    "registryType": "pypi",
+    "identifier": "aidoo-mcp",
+    "version": "0.1.0",
+    "transport": { "type": "stdio" },
+    "environmentVariables": [
+      {
+        "name": "AIDOO_API_KEY",
+        "description": "Aidoo API key, prefixed aid_live_",
+        "isRequired": true,
+        "isSecret": true,
+        "format": "string"
+      }
+    ]
+  }
+]
+```

aidoo_mcp-0.1.0/README.md

@@ -0,0 +1,203 @@
+# aidoo-mcp
+
+Connect any MCP client to your Odoo ERP through [Aidoo](https://aidoo.ai).
+
+`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.
+
+[![PyPI](https://img.shields.io/pypi/v/aidoo-mcp.svg)](https://pypi.org/project/aidoo-mcp/)
+[![Python](https://img.shields.io/pypi/pyversions/aidoo-mcp.svg)](https://pypi.org/project/aidoo-mcp/)
+[![License](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
+
+## Why a bridge
+
+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.
+
+```
+MCP client  <--stdio-->  aidoo-mcp  <--HTTPS-->  Aidoo  <--XML-RPC-->  Odoo
+```
+
+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.
+
+## Requirements
+
+- Python 3.10 or newer
+- An [Aidoo account](https://app.aidoo.ai/register) with an Odoo connection
+- An Aidoo API key, prefixed `aid_live_`, created from the API keys page of your workspace
+
+## Install
+
+Run it without installing anything, with [uv](https://docs.astral.sh/uv/):
+
+```bash
+uvx aidoo-mcp --check
+```
+
+Or install it:
+
+```bash
+pipx install aidoo-mcp
+# or
+pip install aidoo-mcp
+```
+
+## Check your setup
+
+```bash
+export AIDOO_API_KEY=aid_live_your_key_here
+aidoo-mcp --check
+```
+
+The command verifies that the endpoint answers, performs the MCP handshake and prints
+the tools your key grants:
+
+```
+[aidoo-mcp] https://mcp.aidoo.ai/health is reachable
+[aidoo-mcp] authenticated with https://mcp.aidoo.ai/mcp (transport=http, key=aid_live_...cdef)
+[aidoo-mcp] 8 tools available: aidoo_context, aidoo_create, aidoo_print, aidoo_query, ...
+```
+
+## Configure your client
+
+### Claude Desktop
+
+`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS,
+`%APPDATA%\Claude\claude_desktop_config.json` on Windows:
+
+```json
+{
+  "mcpServers": {
+    "aidoo": {
+      "command": "uvx",
+      "args": ["aidoo-mcp"],
+      "env": { "AIDOO_API_KEY": "aid_live_your_key_here" }
+    }
+  }
+}
+```
+
+### Cursor
+
+`~/.cursor/mcp.json`:
+
+```json
+{
+  "mcpServers": {
+    "aidoo": {
+      "command": "uvx",
+      "args": ["aidoo-mcp"],
+      "env": { "AIDOO_API_KEY": "aid_live_your_key_here" }
+    }
+  }
+}
+```
+
+### Windsurf
+
+`~/.codeium/windsurf/mcp_config.json`, same block as Cursor.
+
+### VS Code
+
+`.vscode/mcp.json` in your workspace:
+
+```json
+{
+  "servers": {
+    "aidoo": {
+      "type": "stdio",
+      "command": "uvx",
+      "args": ["aidoo-mcp"],
+      "env": { "AIDOO_API_KEY": "aid_live_your_key_here" }
+    }
+  }
+}
+```
+
+### Any other stdio client
+
+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:
+
+```bash
+aidoo-mcp --api-key aid_live_your_key_here
+```
+
+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](https://aidoo.ai/docs).
+
+## Usage
+
+```
+aidoo-mcp [--api-key KEY] [--url URL] [--transport {http,sse}]
+          [--timeout SECONDS] [--retries N] [--check] [--quiet]
+```
+
+| 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.
+
+## Ask your assistant
+
+```
+List the five quotations I sent last week that are still pending.
+Create a contact for Martin Dupont at Dupont SA, martin@dupont.fr.
+Generate the PDF of invoice INV/2026/0042.
+```
+
+## Security
+
+- The key is read from the environment or the command line and sent as a bearer token
+  over HTTPS. It is masked in every log line.
+- Odoo credentials stay in Aidoo. The bridge never sees them, and never talks to Odoo.
+- Each key carries its own permissions, and every call runs under the Odoo access
+  rules of the linked user. Grant only what the assistant needs.
+- Use one key per person, never a shared key, and revoke it from the dashboard if in doubt.
+- Report a vulnerability privately: see [SECURITY.md](SECURITY.md).
+
+## Troubleshooting
+
+**`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.
+
+## Development
+
+```bash
+uv sync
+uv run pytest
+uv run ruff check .
+uv run ruff format --check .
+```
+
+## License
+
+MIT. See [LICENSE](LICENSE).

aidoo_mcp-0.1.0/SECURITY.md

@@ -0,0 +1,24 @@
+# Security policy
+
+## Reporting a vulnerability
+
+Report vulnerabilities privately to **security@aidoo.ai**. Do not open a public issue.
+
+Include the affected version, the steps to reproduce, and the impact you observed. You
+will get an acknowledgement within three business days, and a fix or a mitigation plan
+within thirty days for confirmed issues.
+
+## Scope
+
+This repository contains the stdio bridge only. It holds no Odoo credentials and stores
+nothing on disk. Reports about the hosted Aidoo platform are equally welcome at the same
+address.
+
+## Handling your API key
+
+- The key is read from `AIDOO_API_KEY` or `--api-key`, sent as a bearer token over HTTPS,
+  and masked in every log line the bridge writes.
+- Prefer the environment over the command line: process arguments are visible to other
+  local processes.
+- Use one key per person, and revoke it from the Aidoo dashboard as soon as it leaks.
+- Grant each key the narrowest set of permissions that still does the job.