Detailing Manager

io.github.RadoslavMoshevPublished by GitHub account RadoslavMoshevv0.1.4Updated Nov 7, 2026

Connect your auto detailing studio's tasks, cars, clients and revenue to Claude or ChatGPT.

VerifiedSTDIODesktop onlyBusiness & Commerce

Server details

Identifier: io.github.RadoslavMoshev/detailing-manager
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Nov 7, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account RadoslavMoshev for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.RadoslavMoshev%2Fdetailing-manager.svg)](https://sourceweft.com/mcp/io.github.RadoslavMoshev%2Fdetailing-manager?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Connects an auto detailing studio's tasks, cars, clients and revenue in Detailing Manager to Claude or ChatGPT.

What you can do: Access the studio's detailing tasks, vehicles, clients and revenue data from an AI assistant.
Query and work with studio records through the assistant rather than the Detailing Manager interface.
No individual tools are documented in the supplied listing, so the exact actions available are not described.
When to use it: Useful for auto detailing studios already running Detailing Manager that want to ask an assistant about their jobs, cars, clients or revenue without switching apps.
Requirements: Runs as a local process via the npm package @detailingmanager/mcp (Node.js required). Needs a Studio MCP key created in Detailing Manager under Settings > Integrations > MCP, supplied through the DETAILING_MCP_API_KEY environment variable. Desktop client only.

Before you install

The server requires a secret API key (DETAILING_MCP_API_KEY) that grants access to studio business data; keep it out of shared configs. The listing does not document which tools exist or whether they can change or delete records, so confirm write behavior before use.

Installation

In SourceWeft

Open Detailing Manager in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.4LatestNov 7, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.