Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Query and update your Odoo ERP in plain language, under your own Odoo access rules.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.aidoo.ai/mcpRun this in your terminal
claude mcp add --transport http aidoo https://mcp.aidoo.ai/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"aidoo": {
"url": "https://mcp.aidoo.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"aidoo": {
"type": "http",
"url": "https://mcp.aidoo.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.aidoo.ai/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain aidoo.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry last month.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, yontu
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Türkçe yazı denetimi: TDK kuralları, yapay zekâ izleri, metin türüne göre üslup.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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.
aid_live_, created from the API keys page of your workspaceRun it without installing anything, with uv:
uvx aidoo-mcp --check
Or install it:
pipx install aidoo-mcp
pip install aidoo-mcp
Prefer Node over Python? The npm/ directory ships the same bridge for npx, with no Python dependency:
npx aidoo-mcp --check
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, ...
~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows:
{
"mcpServers": { "aidoo": { "command": "uvx", "args": ["aidoo-mcp"], "env": { "AIDOO_API_KEY": "aid_live_your_key_here" } } } }
~/.cursor/mcp.json:
{
"mcpServers": { "aidoo": { "command": "uvx", "args": ["aidoo-mcp"], "env": { "AIDOO_API_KEY": "aid_live_your_key_here" } } } }
~/.codeium/windsurf/mcp_config.json, same block as Cursor.
.vscode/mcp.json in your workspace:
{
"servers": { "aidoo": { "type": "stdio", "command": "uvx", "args": ["aidoo-mcp"], "env": { "AIDOO_API_KEY": "aid_live_your_key_here" } } } }
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:
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.
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.
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.
`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.
uv sync
uv run pytest uv run ruff check . uv run ruff format --check .
MIT. See LICENSE.