> ## Documentation Index
> Fetch the complete documentation index at: https://docs.remapdb.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AI Integrations

> Connect AI tools to Remapdb vehicle tuning data through MCP.

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:

```text theme={null}
https://api.remapdb.com/mcp
```

<Info>
  **API access** is available on the **API** and **MAX** plans. It covers direct API usage and MCP-based AI tool connections.
</Info>

## 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](https://app.remapdb.com/api).
* An active **API** or **MAX** plan with API access enabled for the subscription.

<Warning>
  Keep your API key out of source control. Store it in your MCP client config, shell environment, or secret manager.
</Warning>

## Recommended setup

Most coding agents and desktop AI tools ask you for a command to run. Use `npx` for that setup:

```bash theme={null}
npx -y @remapdb/mcp
```

Set this environment variable in the same MCP configuration:

```text theme={null}
REMAPDB_API_KEY=your_remapdb_api_key
```

The public npm package is maintained at [github/remapdb-mcp](https://github.com/BitMeshLtd/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:

```bash theme={null}
claude mcp add --env REMAPDB_API_KEY=your_remapdb_api_key --transport stdio remapdb -- npx -y @remapdb/mcp
```

Then start Claude Code and run:

```text theme={null}
/mcp
```

Use this to confirm `remapdb` is connected.

### Claude Desktop

Add this server to your Claude Desktop MCP configuration:

```json theme={null}
{
  "mcpServers": {
    "remapdb": {
      "command": "npx",
      "args": ["-y", "@remapdb/mcp"],
      "env": {
        "REMAPDB_API_KEY": "your_remapdb_api_key"
      }
    }
  }
}
```

Restart Claude Desktop after saving the file.

### Codex

Add this to your Codex MCP configuration:

```toml theme={null}
[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:

```json theme={null}
{
  "mcpServers": {
    "remapdb": {
      "command": "npx",
      "args": ["-y", "@remapdb/mcp"],
      "env": {
        "REMAPDB_API_KEY": "your_remapdb_api_key"
      }
    }
  }
}
```

Restart Cursor or reload MCP servers after saving the file.

### Windsurf

Add this to your Windsurf MCP configuration:

```json theme={null}
{
  "mcpServers": {
    "remapdb": {
      "command": "npx",
      "args": ["-y", "@remapdb/mcp"],
      "env": {
        "REMAPDB_API_KEY": "your_remapdb_api_key"
      }
    }
  }
}
```

Restart Windsurf or refresh the MCP configuration after saving.

### Gemini CLI

Add this to your Gemini CLI `settings.json`:

```json theme={null}
{
  "mcpServers": {
    "remapdb": {
      "command": "npx",
      "args": ["-y", "@remapdb/mcp"],
      "env": {
        "REMAPDB_API_KEY": "your_remapdb_api_key"
      }
    }
  }
}
```

In Gemini CLI, use `/mcp` to confirm the server is available.

### VS Code

Create or edit `.vscode/mcp.json` in your workspace:

```json theme={null}
{
  "servers": {
    "remapdb": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@remapdb/mcp"],
      "env": {
        "REMAPDB_API_KEY": "your_remapdb_api_key"
      }
    }
  }
}
```

You can also add it through the **MCP: Add Server** command in the Command Palette.

### OpenCode

Add this to your OpenCode config:

```json theme={null}
{
  "$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`:

```yaml theme={null}
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.

```text theme={null}
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:

```bash theme={null}
REMAPDB_API_KEY=your_remapdb_api_key npx -y @remapdb/mcp
```

If your npm version cannot infer the scoped package binary, use the explicit binary form:

```bash theme={null}
REMAPDB_API_KEY=your_remapdb_api_key npx -y --package @remapdb/mcp remapdb-mcp
```

## Available tools

| 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.                                    |

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:

```text theme={null}
Search Remapdb for Audi A4 2.0 TDI engines.
```

```text theme={null}
Find the engine details and available remap stages for engine ID 123.
```

```text theme={null}
List vehicle types in Remapdb, then show manufacturers for the passenger car type.
```

```text theme={null}
Use Remapdb to compare available tuning data for BMW 320d generations.
```

```text theme={null}
Show me the tuning gains for BMW X7 G07 2018 M50i xDrive 530hp.
```

```text theme={null}
Find the closest matching engine for BMW X7 G07 M50i xDrive and summarize OEM power, stage gains, ECU, and available tuning methods.
```

```text theme={null}
Search for Volkswagen Golf GTI engines and show the available remap stages for the best match.
```

Your MCP client decides the exact tool calls.

## 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](https://app.remapdb.com/api). 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.                                     |

## Related actions

* [Credentials and authentication](/api/credentials-and-authentication)
* [Plan access](/api/plan-access)
* [Usage limits](/api/usage-limits)