RenooLab MCP

Official remote MCP server for finding building tradespeople in France, preparing multi-trade renovation projects, submitting moderated contact requests and creating free RenooLab professional profiles.

• 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. »

For one trade, the AI client should infer or accept a supported public trade, ask for the French city if it is missing, then call rechercher_artisans. This read-only search may return attributed Google Maps listings when no RenooLab profile is available. If several French communes have the same name, the client must ask for the postal code or department and retry; it must not silently choose the most populous commune.

For one chantier with at least two confirmed trades in the same French city, the AI client must call rechercher_chantier once with all confirmed trades. It must not split the project into several single-trade searches or silently reduce it to one trade.

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 RenooLab photos, a link to the full WebApp profile and a contact path. External listings are attributed to Google Maps and never expose a telephone number to the model.

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 exactly one selected result 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 contracts

• rechercher_artisans accepts a natural besoin or an explicit metier, plus an optional French ville; it asks for missing or ambiguous inputs instead of guessing;
• rechercher_chantier requires a French ville and a list of confirmed metiers_confirmes; it can return complete providers, a minimal combination, a partial result or a clarification request;
• both searches accept code_postal or departement to disambiguate a homonymous commune, and never silently select one;
• a zero-result search is a valid business result, distinct from a technical failure;
• contacter_artisan requires exactly one target: either the returned RenooLab artisan_id or the explicitly selected external external_place_id, never both;
• contact and signup retain independent server-side validation, rate limits, duplicate controls and explicit-confirmation requirements.

Contract provenance

schemas/mcp-tools-v1.4.0.json is the canonical, versioned public snapshot of the live MCP tools/list contract captured on 23 August 2026. Its recorded source hash identifies the audited live response; its second SHA-256 protects the snapshot after sanitization. Sanitization removes only each tool’s host-specific _meta payload and retains every other public MCP field exactly: name, title, description, input and output schemas, annotations, execution metadata and security schemes.

The snapshot records the deployed Grounding-enabled state: rechercher_artisans may return attributed Google Maps results and has openWorldHint: true. It documents live runtime behavior without publishing private configuration, credentials or deployment infrastructure.

The four per-tool files in schemas are exact mirrors of that snapshot. The LobeHub manifest deliberately projects only the fields supported by its owner format—name, description and input schema—while retaining the exact live descriptions and compatible input schemas.

Safety and privacy

• Search is read-only.
• Contact and professional registration require explicit user intent.
• Contact requests target exactly one selected result and are moderated before transmission.
• An external Google Maps selection stores only its Place ID and the user's confirmed request; Google listing details are not persisted by the contact queue.
• 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/mcp-tools-v1.4.0.json: canonical sanitized v1.4.0 tools/list snapshot with release provenance and hashes.
• schemas/rechercher-artisans.json: exact per-tool mirror for the single-trade search contract.
• schemas/rechercher-chantier.json: multi-trade project-search input/output contract.
• schemas/contacter-artisan.json: moderated contact input/output contract.
• schemas/creer-profil-artisan.json: professional-profile creation input/output contract.
• 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.