mobilede-adapter
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
vilikon-adapter-mobile-de
An adapter for one car dealer's own mobile.de account: listings, prices, statistics, ratings and customer inquiries. MCP in front, the official mobile.de REST APIs behind.
On its own: an MCP server (stdio or Streamable HTTP) for any MCP client.
In Vilikon: a tool with
MODULE.json(functions for employees, every change behind the owner's approval) and a lead channel (vilikon.kanal/1) that hands new inquiries to the cockpit's lead intake.
This repository is a template. Each dealer runs their own copy with their own mobile.de API user, for their own account only. The adapter never serves several dealers and never holds anyone else's credentials.
MCP client Vilikon cockpit
│ /mcp or stdio │ /ki/… (MODULE.json, vilikon.kanal/1)
└──────────────┬───────────────────┘
service.py checks, read-change-write, previews
client.py Seller API + Lead API, HTTP basic auth, retries
│
services.mobile.deWhat it can do
Read | Change (preview first) |
|
|
|
|
|
|
|
|
|
Listings: mobile.de wants the complete listing on every update, so a change fetches the listing, changes one field and sends it back whole. Changing the gross price recomputes the net price from the listing's VAT rate.
Images: mobile.de takes JPG only, up to 2 MB each, at most the dealer's
maxImages, uploaded one after the other. Hand a photo over withstage_image(a file path or base64; JPG, PNG, HEIC, WebP): it is turned upright, stripped of its metadata (a phone writes the location into it), fitted below 2 MB and kept inDATA_DIR/imagesfor a week under an id. Pass each image as{"image": "img-…"},{"url": "https://…"}or{"base64": "…"}.Reference data: make, model, category, fuel, gearbox and the other fixed values are codes from mobile.de's reference tables (
/refdata, no login needed).reference_datalooks them up for the dealer's site, with a search, and keeps them for a day.New listings carry an
X-Mobile-Insertion-Request-Idderived from their content: a repeat after a timeout creates nothing twice.Inquiries: mobile.de has no push. The adapter polls the Lead API events with its cursor, merges the events of one lead (first inquiry, the buyer's reply, calls) and keeps them for 30 days in
DATA_DIR/leads.json(mode 0600).Statistics are passed through and never stored: mobile.de allows them only for the listing's lifetime.
Related MCP server: Amazon Seller MCP
Getting access at mobile.de
The API user is not the login for the dealer area. The dealer asks mobile.de customer service to enable an API user for their own account: e-mail to service@team.mobile.de with customer number, company name, a request to activate the Seller API and the Lead API, and a technical and a contractual contact. A sandbox account can be requested the same way. Statistics need an extra permission, ratings at least the Gold package; without them those functions say so in one sentence.
Docs: Seller API, Lead API.
Settings
All from the environment, never from a file.
Variable | Meaning |
| The dealer's API user |
| Only if several dealer accounts belong to the API user |
|
|
|
|
|
|
| Where the lead cursor and the inquiries are kept |
| Bearer token for |
| Default |
Running it on its own
python3 -m venv .venv && .venv/bin/pip install -r requirements.txt .For a local MCP client (stdio), for example in a client's server list:
{"command": "/path/to/.venv/bin/mobilede-adapter", "args": ["stdio"],
"env": {"MOBILE_DE_USER": "…", "MOBILE_DE_PASSWORD": "…", "DATA_DIR": "/path/to/data"}}Over HTTP (MCP at /mcp):
ADAPTER_TOKEN=… .venv/bin/mobilede-adapter serveWith MOBILE_DE_WRITES=confirm a change works in two calls: the first returns preview and confirmation, the
second with the same values and that confirmation carries it out. A code is valid for 10 minutes and works once.
Running it in Vilikon
On an instance with the adapter catalog the IT Specialist does all of this with one tool call (adapter_install),
driven by ADAPTER.json, and the owner types the credentials into a card in the chat. By hand, it goes like this:
A tool project with its own repository in the instance's GitHub account, filled with a copy of this repository.
Build
python3 -m venv .venv && .venv/bin/pip install -r requirements.txt ., start.venv/bin/python -m mobilede_adapter serve(the cockpit moves the folder on publishing, so the start must not rely on the paths baked into.venv/binscripts).On an English instance, copy
vilikon/en/MODULE.jsonandvilikon/en/BRIEFING.mdover the German ones in the root.Request the credentials
MOBILE_DE_USER,MOBILE_DE_PASSWORD(andMOBILE_DE_SELLER_IDif needed) withwerkzeug_zugang_anfordern; the owner enters them.Let the employees who list vehicles use the tool (the “Tools” page): module functions send JSON only, so a photo reaches
ki/imagesthrough the generic tool call, which sends a file of the employee's workspace.Propose the change. Once the owner approves it, the tool runs, the rights
modul.mobilede.*can be granted, the channel “mobile.de” appears under acquisition andki/pruefentells whether the credentials work.
Inside Vilikon (BASE_PATH below /werkzeug/) the /ki/ paths are on and /mcp is off unless ADAPTER_TOKEN is
set. A change through /ki/ happens only with the cockpit's X-Vilikon-Freigabe header, which it sends after the
owner's yes; the same approval twice does the work once.
Path | For |
| New inquiries as |
| The buyer answered, asked again, or a call was missed, on a known inquiry |
| Dashboard card: inquiries of the last 7 days |
| Whether the credentials work for both APIs |
| A photo as a file (multipart, any field) or as the body; answers its id. No approval: it stays here |
ADAPTER.json describes build, start, check and credentials for Vilikon's future adapter catalog.
Development
.venv/bin/pip install -e ".[dev]" && .venv/bin/pytest && .venv/bin/ruff check . && .venv/bin/ruff format --check .The tests run against a stand-in for mobile.de shaped after the examples in its documentation; all data in them is invented. Not covered without a real API user: mobile.de's actual limits and error answers.
Licence
MIT, see LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Live franchised-dealer inventory, quotes, and consented salesperson handoffs.
Hosted MCP server for OTTO Market, Kaufland and Mirakl sellers: orders, stock, listings and ads.
Hosted MCP server for 3Dsellers, the multichannel selling platform. Connect Claude, ChatGPT, Cursor, VS Code or any MCP client and manage your eBay, Amazon, Walmart, Etsy, Shopify, WooCommerce and TikTok Shop stores in plain language: search and update products, publish listings, sync inventory, tag and track orders, run bulk actions and CSV imports, and reply to customer messages. 120+ tools. Sign in with OAuth or a personal token. No eBay developer account and nothing to install. Setup guides and config examples for every client: https://github.com/3dsellers/ebay-mcp-server
Manage one storefront: listings, bulk catalogue sync, analytics and webhooks.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables managing Ozon Seller and Performance APIs through MCP, covering products, stocks, prices, orders, finance, analytics, advertising, reviews, and chat operations.MIT
- AlicenseAqualityBmaintenanceEnables managing Amazon seller listings, orders, pricing, inventory, and reports through the SP-API via MCP tools.1518 npm5MIT
- AlicenseNot gradedqualityDmaintenanceEnables read-only access to Mercado Livre seller data via the official API, including profile, reputation, listings, orders, questions, shipments, categories, and item visits through OAuth 2.0.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to connect marketplace seller accounts, explore and call shop-level APIs, and manage orders, products, returns, inventory, pricing, and tracking with scoped read-only or read-write access.2MIT