The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Mercedes Benz Service Reminder – SilberArrows listing page.
A Model Context Protocol server that helps Mercedes-Benz owners plan their next Service A or Service B, understand what each service typically includes, read general guidance on common warning lights, and find a Mercedes-Benz specialist in Dubai.
Homepage: https://mercedes-benz.silberarrows.com/
Disclaimer: Intervals are general guidance only (approximately 15,000 km or 12 months, whichever comes first, on most models). Always follow your Mercedes-Benz's own service indicator (ASSYST) and the manufacturer's schedule for your model. Warning light information is general and is not a diagnosis.
No installation is needed with npx:
Or install globally: npm install -g mercedes-benz-service-reminder-mcp.
Add to claude_desktop_config.json (Settings → Developer → Edit Config):
Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
Any client that supports stdio MCP servers can launch it with:
npx-y mercedes-benz-service-reminder-mcpClients that only accept remote (HTTP) servers, such as ChatGPT connectors, need a stdio-to-HTTP bridge (for example npx -y supergateway --stdio "npx -y mercedes-benz-service-reminder-mcp") or a hosted deployment such as Smithery. A Dockerfile is included:
| Tool | What it does |
|---|---|
get_next_service | From the last service type (A/B), date and mileage (plus optional current mileage), returns the next service type, due date and due km under the alternating A/B (ASSYST-style) schedule. Default interval 15,000 km or 12 months, whichever comes first; optional overrides. |
explain_service | What a Mercedes-Benz Service A or Service B typically includes. |
warning_light_info | General guidance for a small set of common Mercedes-Benz warning lights and messages (check engine, flashing check engine, reduced power, brake/ABS/ESP, battery/electrical, service due). |
find_specialist | Contact details for SilberArrows - Mercedes-Benz Service Centre, Dubai. |
Ask your assistant:
"My Mercedes-Benz had a Service A on 1 March 2026 at 40,000 km and it's now on 50,000 km. When is the next service?"
get_next_service → Service B, due by 2027-03-01 or 55,000 km, whichever comes first; estimated for late January 2027 based on driving so far.
"What's included in a Mercedes-Benz Service B?" → explain_service
"My Mercedes-Benz check engine light is flashing – what does it mean?" → warning_light_info
"Where can I get my Mercedes-Benz serviced in Dubai?" → find_specialist
SilberArrows is a Mercedes-Benz service centre in Al Quoz Industrial Area 1, Dubai, offering Service A and Service B, diagnostics and general Mercedes-Benz maintenance.
Mercedes-Benz is a trademark of Mercedes-Benz Group AG. This project is independent and is not affiliated with or endorsed by Mercedes-Benz Group AG.
MIT © SilberArrows
This server can also run as a stateless Streamable HTTP MCP endpoint on Netlify Functions (netlify/functions/mcp.mts, served at /mcp).
https://silberarrows-mcp.netlify.app/mcp{ "mcpServers": { "mercedes-benz-service-reminder": { "url": "https://silberarrows-mcp.netlify.app/mcp" } } }npx netlify-cli deploy --prod (uses netlify.toml)node test/http-client-test.mjs https://silberarrows-mcp.netlify.app/mcpNo authentication is required. For platforms that require an "API Key" connection method (e.g. Vercel Connect), an API key is optional; any value works, e.g. silberarrows-public. Send it either as:
Authorization: Bearer silberarrows-public, orx-api-key: silberarrows-publicThe key is only used for client identification and requests are never rejected based on it.