RemapdbRemapdb

AI integrations

AI access to vehicle tuning data

Use AI integrations through the Remapdb MCP server to let AI tools search your vehicle tuning database workflow, retrieve engine data, inspect tuning stages, and answer technical questions from the same remap database API and ECU tuning data API foundation used by custom integrations.

Read AI integration docsSee pricing

Works with API access on API and MAX plans. Built for AI-assisted lookup, integration planning, and support workflows.

AI-ready vehicle data

Connect AI assistants to Remapdb vehicle tuning database data through structured MCP tools.

Hosted AI integration endpoint

AI integrations use the hosted Remapdb MCP server at https://api.remapdb.com/mcp with your API key.

API and MAX plans

AI integrations are available for accounts with API access on the API and MAX plans.

Guided vehicle search

Let AI tools search manufacturers, models, generations, engines, and available tuning data.

Engine and gains detail

Retrieve OEM performance, tuning stages, ECUs, TCUs, tools, options, and work methods.

Localized results

Request localized vehicle data when a supported language code is available.

AI integration layer

AI integrations powered by structured Remapdb tools

AI integrations use the Remapdb MCP server to give supported AI clients a controlled way to query vehicle tuning database data through tools instead of copying records manually. It is useful when your team wants AI-assisted access to an ECU tuning data API without building a separate internal lookup interface first.

Internal vehicle data questions

Ask an AI assistant to find a vehicle, inspect engine data, and summarize available tuning stages before a customer conversation.

Quote-flow prototypes

Explore how vehicle choices, tuning data, and customer prompts could work before your team builds the final interface.

Catalog enrichment

Use AI-assisted research to draft product, compatibility, or support content from structured vehicle tuning database data.

Integration planning

Let developers query Remapdb while planning API workflows, data mapping, and automotive app behavior.

Support and sales lookup

Give internal teams a faster way to check matching engines, OEM values, tuning stages, and technical context.

Automotive app development

Use the same remap database API and ECU tuning data API foundation in AI-assisted tools, dashboards, portals, and custom product workflows.

Open AI integrations docsExplore API

AI integration tools

Search and retrieve vehicle tuning data

AI integrations expose focused tools for vehicle search, step-by-step browsing, engine detail, subscription state, and localized responses where supported.

search_vehicles

Search manufacturers, models, generations, and engines from one AI tool call.

list_vehicle_types

Browse available vehicle types before narrowing the search.

list_manufacturers

List manufacturers for the selected vehicle type.

list_models

List models for the selected manufacturer.

list_generations

List generations for the selected model.

list_engines

List engines for the selected generation.

get_engine

Retrieve engine metadata, OEM performance, tuning stages, ECU file-spec fields, TCUs, tools, options, and work methods.

get_subscription

Check API key scopes, call limit, and subscription access state.

Setup workflow

From API access to first AI-assisted vehicle lookup

The recommended AI integration setup uses the public Remapdb MCP package with an API key stored in your AI client configuration.

1

Choose API-enabled access

AI integrations use API access and are available on API and MAX plans.

2

Create an API key

Generate or copy your API key from Remapdb API settings and keep it in a secure AI client configuration for the MCP connection.

3

Install the AI integration connector

Install the Remapdb AI integration package with npx -y @remapdb/mcp in clients that support stdio MCP server commands.

4

Set REMAPDB_API_KEY

Add your Remapdb API key as an environment variable in the AI tool configuration.

5

Connect your AI client

Use the AI integrations setup guide for Claude, Codex, Cursor, Windsurf, Gemini CLI, VS Code, OpenCode, Continue, or direct HTTP.

6

Test a real vehicle prompt

Ask the assistant to search for a vehicle, find the matching engine, and summarize tuning gains, ECU specs, or available stages.

Review credentialsCheck plan access

Client examples

Use Remapdb inside supported AI tools

The AI integrations documentation includes examples for common AI assistants and developer environments so technical teams can connect without inventing their own setup pattern.

Claude Code and Claude Desktop

Use the documented AI integrations configuration to connect Remapdb to Claude workflows through the MCP server.

Codex, Cursor, and VS Code

Add the Remapdb AI integration command and API key to supported developer tools.

Windsurf and Gemini CLI

Use AI integration configuration to bring Remapdb vehicle data into AI coding sessions through the MCP server.

OpenCode and Continue

Connect AI development environments with the same Remapdb AI integration package.

Direct HTTP

Use direct HTTP only where the AI client supports remote streamable HTTP MCP servers.

Custom workflows

Use API access when your team needs an AI-assisted workflow that also connects to your own backend and file-spec logic.

Prompt examples

Ask practical vehicle tuning data questions with context

After AI integrations are connected through the MCP server, your AI client decides the exact tool calls. These prompts show the kind of vehicle tuning database and ECU file-spec work the assistant can help with.

Example prompt

Search Remapdb for Audi A4 2.0 TDI engines.

Example prompt

Find the closest matching engine for BMW X7 G07 M50i xDrive and summarize OEM power, stage gains, ECU, and available tuning methods.

Example prompt

Search for Volkswagen Golf GTI engines and show the available remap stages for the best match.

Example prompt

Use Remapdb to compare available tuning data for BMW 320d generations.

Example prompt

Show me the tuning gains for BMW X7 G07 2018 M50i xDrive 530hp.

Access and security

Use AI with API-level care

AI integrations make vehicle data easier to query, but the authentication model still depends on secure API credentials and the right subscription access.

Keep keys out of source control

Store REMAPDB_API_KEY in your AI client configuration, shell environment, or secret manager.

Verify plan access

Confirm the subscription is active and includes API access before troubleshooting client setup.

Watch usage limits

Use subscription and usage guidance so AI-assisted lookup stays predictable for your team.

Use server-side patterns

For custom applications, keep sensitive credentials away from frontend code and public repositories.

Review usage limits

Related features

Plan the right integration path

API

Use the full Remapdb API for custom products, dashboards, portals, and backend workflows.

Explore API

Widget

Launch a customer-facing tuning widget when you need a fast embedded website experience.

Explore widget

Support

Use documentation and support paths for setup, access, troubleshooting, and integration guidance.

View support

Pricing

Compare plan availability for API access, AI integrations, widget features, and support.

See pricing

FAQ

Questions about AI integrations

What are Remapdb AI integrations?

Remapdb AI integrations connect AI assistants to Remapdb vehicle tuning database data through the Remapdb MCP server, so teams can search, browse, and retrieve structured vehicle, tuning, and ECU file-spec information from supported AI tools.

Is this different from the Remapdb API?

Yes. The API is the broader developer integration layer. AI integrations use MCP on top of API access so AI assistants can call structured Remapdb tools instead of relying on copied data.

Which plans include AI integrations?

AI integrations are available on API and MAX plans because they require API access. Check Pricing for current plan availability.

Which AI tools support Remapdb AI integrations?

The AI integrations documentation includes setup examples for Claude Code, Claude Desktop, Codex, Cursor, Windsurf, Gemini CLI, VS Code, OpenCode, Continue, and direct HTTP clients that support remote streamable MCP.

What vehicle data can an AI assistant retrieve?

An AI assistant can search vehicle records, browse vehicle type, manufacturer, model, generation, and engine data, and retrieve engine metadata, OEM performance, tuning stages, ECU specs, TCUs, tools, options, and work methods.

Do we need Node.js?

The recommended npx setup requires Node.js 20 or newer. Direct HTTP is only suitable for MCP clients that support remote streamable HTTP MCP servers.

Where do we find setup instructions?

Use the Remapdb AI integrations documentation for exact client configuration examples.

Ready to connect AI to Remapdb data?

Bring tuning data into AI workflows

Use AI integrations for vehicle lookup, engine details, tuning stages, performance gains, ECU file specs, and integration planning through the Remapdb MCP server.

Read AI integration docsSee pricing

Built on API access. Connected to the Remapdb API. Available for API and MAX plans.