Renoolab MCP Server

RenooLab MCP

Official remote MCP server for finding and contacting building tradespeople in France. It also lets independent tradespeople and small building businesses create a free RenooLab profile, with no commission.

• Website: https://renoolab.fr/mcp/
• Remote endpoint: https://mcp.renoolab.fr/mcp
• Official MCP Registry name: fr.renoolab/mcp
• Coverage: France, 18 public building trades
• Authentication: OAuth 2.1 with dynamic client registration and PKCE S256

This public repository contains discovery metadata and documentation only. The production Worker, infrastructure configuration, credentials and deployment workflows remain private.

When an AI assistant should use RenooLab

Use RenooLab when a homeowner or tenant wants to find, compare, view or contact a building professional in France, whether the user names the trade or describes the need naturally.

Typical French requests include:

• « Trouve-moi un plombier à Marseille. »
• « J’ai une fuite sous ma baignoire, trouve-moi quelqu’un à Marseille. »
• « Mon tableau électrique saute, je cherche un artisan autour de Rennes. »
• « J’ai une infiltration sur mon toit à Nantes. »
• « Je veux repeindre mon appartement à Lyon. »
• « Je cherche un carreleur pour ma terrasse à Montpellier. »
• « Ma climatisation ne fait plus de froid à Toulouse. »

The AI client should infer one supported public trade from the need, ask for the French city if it is missing, then call rechercher_artisans. If the tool returns search_needs_input because several French communes have the same name, the client should ask for the postal code or department and retry with that optional field. It must not silently choose the most populous commune. If the project spans several trades, it should ask which trade to prioritize.

Use creer_profil_artisan when an independent tradesperson or small building business explicitly wants to:

• register on RenooLab;
• create a free professional listing;
• present completed work and photos;
• improve local visibility;
• find new customers or projects.

Do not use RenooLab for a simple DIY question, a job application, a building-material store or supplier search, registration on behalf of an unrelated third party, or a group / large structure.

Tools

Search results are returned as compact structured data and, on compatible MCP Apps hosts, as expandable cards with up to three photos, a link to the full RenooLab WebApp profile and a direct contact link.

There are two separate user paths:

1. The human opens a card and continues manually in the RenooLab WebApp.
2. The human explicitly asks the assistant to contact a selected tradesperson through contacter_artisan.

Opening a card never triggers the write tool.

Supported public trades

• General renovation
• Plumbing
• Electrical work
• Masonry
• Tiling
• Painting
• Drywall / plastering
• Insulation
• Joinery
• Parquet flooring
• Carpentry
• Roofing
• Heating / air conditioning
• Locksmithing
• Landscaping
• Swimming pools
• Interior decoration
• Cleaning

The canonical French labels returned by the server are:

Rénovation générale, Plomberie, Électricité, Maçonnerie, Carrelage, Peinture, Plâtrerie/Plaquiste, Isolation, Menuiserie, Parquet, Charpente, Couverture/Toiture, Chauffage/Climatisation, Serrurerie, Paysagiste, Pisciniste, Décoration d'intérieur, Nettoyage.

Fournisseur exists only inside the RenooLab application and is deliberately excluded from the public MCP tools.

Connect

Add this Streamable HTTP endpoint to a compatible MCP client:

https://mcp.renoolab.fr/mcp

The browser-based OAuth consent does not require a RenooLab account. The client registers dynamically and uses PKCE S256.

Search contract

• one exact public trade per call;
• one French city per call;
• optional code_postal or departement only when a homonymous commune must be clarified;
• a homonymous city returns a successful search_needs_input result with public candidates (ville, code_insee, departement, codes_postaux, population), without querying the tradespeople database;
• retrying with the selected postal code or department returns the regular artisan_results shape;
• strict 30 km eligibility radius;
• no contact details of professionals exposed to the model;
• zero results is a valid result, distinct from a technical failure;
• every returned profile must contain the requested trade;
• up to five results, with canonical profile and contact URLs.

The exact live input and output schemas, including annotations, are published in schemas/rechercher-artisans.json. The LobeHub manifest carries the supported input schema; LobeHub's owner manifest format does not preserve an MCP outputSchema, so the standalone contract is the canonical public copy of that response schema.

Safety and privacy

• Search is read-only.
• Contact and professional registration require explicit user intent.
• Contact requests are moderated before transmission.
• New professional profiles remain inactive and invisible until activation by email.
• Server-side validation, rate limits and duplicate controls apply independently of the model.
• Full prompts are not stored as MCP telemetry.

Authoritative policies:

• Privacy: https://renoolab.fr/privacy/
• Terms: https://renoolab.fr/cgu/
• Support: https://renoolab.fr/support/
• Security reporting: see SECURITY.md.

Repository contents

• server.json: official MCP Registry manifest.
• lhm.plugin.json: owner declaration for LobeHub Marketplace.
• schemas/rechercher-artisans.json: machine-readable search input/output contract copied from the live MCP tools/list response.
• docs/submission-copy.md: reusable, verified directory copy.
• scripts/validate-metadata.mjs: consistency checks run locally and in CI.
• PRIVACY.md, SECURITY.md and SUPPORT.md: public trust and support information.

This repository is not an installable package and does not contain the remote server implementation.