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:
https://api.remapdb.com/mcp
API access is available on the API and MAX plans. It covers direct API usage and MCP-based AI tool connections.
- 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.
Recommended setup
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:
REMAPDB_API_KEY=your_remapdb_api_key
Setup examples
Claude Code
Run this command:
claude mcp add --env REMAPDB_API_KEY=your_remapdb_api_key --transport stdio remapdb -- npx -y @remapdb/mcp
remapdb is connected.
Claude Desktop
Add this server to your Claude Desktop MCP configuration:
{
"mcpServers": {
"remapdb": {
"command": "npx",
"args": ["-y", "@remapdb/mcp"],
"env": {
"REMAPDB_API_KEY": "your_remapdb_api_key"
}
}
}
}
Codex
Add this to your Codex MCP configuration:
[mcp_servers.remapdb]
command = "npx"
args = ["-y", "@remapdb/mcp"]
[mcp_servers.remapdb.env]
REMAPDB_API_KEY = "your_remapdb_api_key"
Cursor
Add this to your Cursor MCP configuration:
{
"mcpServers": {
"remapdb": {
"command": "npx",
"args": ["-y", "@remapdb/mcp"],
"env": {
"REMAPDB_API_KEY": "your_remapdb_api_key"
}
}
}
}
Windsurf
Add this to your Windsurf MCP configuration:
{
"mcpServers": {
"remapdb": {
"command": "npx",
"args": ["-y", "@remapdb/mcp"],
"env": {
"REMAPDB_API_KEY": "your_remapdb_api_key"
}
}
}
}
Gemini CLI
Add this to your Gemini CLI settings.json:
{
"mcpServers": {
"remapdb": {
"command": "npx",
"args": ["-y", "@remapdb/mcp"],
"env": {
"REMAPDB_API_KEY": "your_remapdb_api_key"
}
}
}
}
/mcp to confirm the server is available.
VS Code
Create or edit .vscode/mcp.json in your workspace:
{
"servers": {
"remapdb": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@remapdb/mcp"],
"env": {
"REMAPDB_API_KEY": "your_remapdb_api_key"
}
}
}
}
OpenCode
Add this to your OpenCode config:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"remapdb": {
"type": "local",
"command": ["npx", "-y", "@remapdb/mcp"],
"environment": {
"REMAPDB_API_KEY": "your_remapdb_api_key"
}
}
}
}
Continue
Create a file such as .continue/mcpServers/remapdb.yaml:
name: Remapdb
version: 0.0.1
schema: v1
mcpServers:
- name: Remapdb
type: stdio
command: npx
args:
- "-y"
- "@remapdb/mcp"
env:
REMAPDB_API_KEY: your_remapdb_api_key
Direct HTTP
Use direct HTTP only if your MCP client supports remote streamable HTTP MCP servers.
URL: https://api.remapdb.com/mcp
Authorization: Bearer your_remapdb_api_key
Mcp-Protocol-Version: 2025-03-26
Test from a terminal
You can test that Node and the Remapdb MCP package start correctly:
REMAPDB_API_KEY=your_remapdb_api_key npx -y @remapdb/mcp
REMAPDB_API_KEY=your_remapdb_api_key npx -y --package @remapdb/mcp remapdb-mcp
| Tool | What it does |
|---|
search_vehicles | Searches manufacturers, models, generations, and engines. |
list_vehicle_types | Lists available Remapdb vehicle types. |
list_manufacturers | Lists manufacturers for a vehicle type. |
list_models | Lists models for a manufacturer. |
list_generations | Lists generations for a model. |
list_engines | Lists engines for a generation. |
get_engine | Gets engine metadata, OEM performance, tuning stages, ECUs, TCUs, tools, options, and work methods. |
get_subscription | Shows API key scopes, call limit, and subscription access state. |
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:
Search Remapdb for Audi A4 2.0 TDI engines.
Find the engine details and available remap stages for engine ID 123.
List vehicle types in Remapdb, then show manufacturers for the passenger car type.
Use Remapdb to compare available tuning data for BMW 320d generations.
Show me the tuning gains for BMW X7 G07 2018 M50i xDrive 530hp.
Find the closest matching engine for BMW X7 G07 M50i xDrive and summarize OEM power, stage gains, ECU, and available tuning methods.
Search for Volkswagen Golf GTI engines and show the available remap stages for the best match.
Troubleshooting
| Issue | What to check |
|---|
| Missing API key | Set REMAPDB_API_KEY in your MCP configuration or pass --api-key when testing from a terminal. |
| Invalid API key | Copy the API key again from API settings. If credentials were rotated, update every MCP client config. |
| API access unavailable | Confirm the subscription is active and on the API or MAX plan. |
| Not enough permissions | Confirm the API key includes the vdb_read scope. |
| Rate limit reached | Wait for the limit window to reset or review API usage for the account. |
| Node cannot start | Use an absolute npx path if your MCP client does not load nvm, asdf, or your shell profile. |
