Skip to main content
Use Remapdb AI Integrations when you want an AI assistant to search and retrieve Remapdb vehicle data through structured MCP tools instead of copying data manually. The hosted MCP endpoint is:
API access is available on the API and MAX plans. It covers direct API usage and MCP-based AI tool connections.

Video tutorial

Connect an AI assistant through MCP and follow a workshop conversation across vehicle data, registrations, diagnostics and saved ECU inspections.
Watch on YouTube · 1:43

What AI Integrations give your tool

With Remapdb AI Integrations connected, your assistant can:
  • Search manufacturers, models, generations, and engines.
  • Browse vehicle data step by step from vehicle type to engine.
  • Retrieve engine metadata, OEM performance, tuning stages, ECUs, TCUs, tools, options, and work methods.
  • Check the authenticated API key subscription and usage state.
  • Request localized vehicle data by passing a supported language code.
This is useful for internal vehicle data questions, quote-flow prototypes, product catalog enrichment, integration work, and automotive app development.

Requirements

  • Node.js 20 or newer for the npx setup.
  • A Remapdb API key from API settings.
  • An active API or MAX plan with API access enabled for the subscription.
Keep your API key out of source control. Store it in your MCP client config, shell environment, or secret manager.
Most coding agents and desktop AI tools ask you for a command to run. Use npx for that setup:
Set this environment variable in the same MCP configuration:
The public npm package is maintained at github/remapdb-mcp. It connects your AI tool to the hosted Remapdb MCP endpoint securely with your API key.

Setup examples

Claude Code

Run this command:
Then start Claude Code and run:
Use this to confirm remapdb is connected.

Claude Desktop

Add this server to your Claude Desktop MCP configuration:
Restart Claude Desktop after saving the file.

Codex

Add this to your Codex MCP configuration:

Cursor

Add this to your Cursor MCP configuration:
Restart Cursor or reload MCP servers after saving the file.

Windsurf

Add this to your Windsurf MCP configuration:
Restart Windsurf or refresh the MCP configuration after saving.

Gemini CLI

Add this to your Gemini CLI settings.json:
In Gemini CLI, use /mcp to confirm the server is available.

VS Code

Create or edit .vscode/mcp.json in your workspace:
You can also add it through the MCP: Add Server command in the Command Palette.

OpenCode

Add this to your OpenCode config:

Continue

Create a file such as .continue/mcpServers/remapdb.yaml:

Direct HTTP

Use direct HTTP only if your MCP client supports remote streamable HTTP MCP servers.

Test from a terminal

You can test that Node and the Remapdb MCP package start correctly:
If your npm version cannot infer the scoped package binary, use the explicit binary form:

Available tools

UK VRM tools require an active API or MAX full API subscription and subscription.uk_vrm_access=true. Trial API credentials do not grant these MCP tools, including trials on paid Plus/Pro widget plans. Designated free test registrations are available separately through REST; this exception does not enable MCP. lookup_uk_vrm takes vrm, a required idempotency_key (8–128 letters, digits, ., _, :, or -), and optional language. Generate a unique key per lookup and reuse it for retries. A successful uncached lookup consumes one included lookup, or one purchased lookup after the monthly allowance. Cached results consume nothing. REST, MCP and widgets share the same balance and account idempotency namespace. Do not automatically retry a failed lookup with a new key. get_subscription exposes mcp_access, uk_vrm_access, uk_vrm_limit and uk_vrm_remaining inside subscription. uk_vrm_limit includes the current period allowance and unspent top-ups; uk_vrm_remaining is the spendable balance after usage and reservations. Use get_uk_vrm_usage for the breakdown and reset time. Entitlements are rechecked on every request, including existing MCP sessions. Several tools accept an optional language argument. If it is not provided, Remapdb uses the request Accept-Language value where available, then falls back to the API default language. Search and manufacturer listing support pagination with cursor and limit. limit must be between 1 and 100.

Example prompts

After AI Integrations are connected, try prompts like:
Your MCP client decides the exact tool calls.

Troubleshooting

DTC lookup and ECU observation

DTC dictionary tools are included on active API and MAX subscriptions with vdb_read: See DTC lookup for interpretation and limits. Definitions are references, not diagnoses. Manufacturer context can change a code’s meaning. ECU tools are included with active API and MAX subscriptions using the standard vdb_read API key, just like DTC lookup. No separate account activation or additional ECU scopes are needed. Upload the binary through POST /v2/ecu/files first. MCP takes the resulting file_id; it does not read arbitrary local paths, URLs or binary attachments. Each submission needs an idempotency_key. Reuse it on retry, including retries between REST and MCP. Poll the returned job_id every 2 seconds or slower until completed. For a grid, run scan_ecu_maps or inspect_ecu, wait for completion, and call get_ecu_result with details: true. Select maps.items[].map_id. Pass the original file_id, that scan’s job_id as scan_job_id, and the selected map_id to get_ecu_map_grid. Poll the new job and request its detailed result to get grid.values. Identification results retain confidence levels. Map names, units and scaling can be unknown; these are observation tools and do not prove a file is stock, tuned or safe to flash. See ECU observation and Reading ECU results.