REDLINE Developers

Built by Redline Autohaus

Automotive tools.
Ready for AI.

Give your next build a foundation in real diagnostic evidence and practical firmware tools. Explore our UDS API and free, open-source MCP servers for WinOLS and Ghidra.

Explore the docs Get WinOLS MCPGet Ghidra MCP

Machine-readable contracts Open-source MCP

REDLINE / DEVELOPER TOOLKIT
01 / DIAGNOSTIC EVIDENCEHTTP API

Structured for your next insight.

{
  "representation": "complete",
  "payload_hex": "22F186"
}
02 / MAP DEFINITIONSLOCAL MCP
winols_get_project
winols_validate_map
winols_create_map
03 / FIRMWARE ANALYSISLOCAL MCP
ghidra_get_call_graph
ghidra_trace_data_flow
Evidence → context → toolsBuilt for developers
AI-readable documentation & schemas
Evidence-first diagnostic ingestion
Free MIT-licensed MCP servers

The toolkit

Built for automotive work.

Three focused products for developers, researchers, and calibration specialists.

AI-ready API

UDS Evidence API

Turn diagnostic observations into structured, traceable records. Preserve the bytes, their source, and the context your applications need to work with them.

  • Complete, partial, and unavailable evidence
  • Source provenance and separate interpretations
  • Durable batch ingestion and repeatable retries
  • OpenAPI, JSON Schemas, and an AI client guide

For storing and analyzing diagnostic evidence. Access to dataset records requires a scoped Redline credential.

Explore the UDS API OpenAPI
Free & open source

WinOLS MCP

Connect your MCP-compatible AI assistant to map-definition workflows in WinOLS through a Rust server and local Lua bridge.

  • Inspect projects, maps, and Original/current bytes
  • Validate proposed definitions before creation
  • Create map metadata and read it back
  • Try the mock backend without WinOLS

The MCP is free under MIT. Live use requires your own WinOLS and OLS530 licenses. Limited live checks passed; full acceptance remains incomplete.

Explore WinOLS MCP Source code
Free & open source

Ghidra MCP

Bring 85 native analysis tools into your MCP client, with 84 supported headlessly. Inspect firmware in background Ghidra or an active CodeBrowser window.

  • Call graphs, control flow, and bounded SSA tracing
  • Typed variables, structures, and guarded annotations
  • Batch inspection and candidate function matching
  • Isolated emulation with explicit inputs and limits

The MCP is free under MIT. Bring Ghidra 12.1.3 and JDK 21; build the Java adapter against your Ghidra installation.

Explore Ghidra MCP Source code

Made for AI-assisted development

A clear contract.
A traceable foundation.

Give your tools the structure to work with automotive data while keeping the source evidence intact.

Read the AI client guide
01

Discover the contract

Public OpenAPI, JSON Schemas, Markdown guides, and runnable examples give developers and AI clients an explicit starting point.

02

Keep the evidence intact

Preserve exact bytes, gaps, unknown context, and source provenance. Store interpretations with their supporting evidence and review status.

03

Build with defined tools

Use scoped API access for ingestion and a focused set of MCP tools for local Ghidra analysis and WinOLS map definitions.

Your next build starts here.

Choose a product, read its contract, and try a working example.

Open documentation