RDW MCP Server

Global Installation (Recommended for CLI usage)

After global installation, you can run the server directly:

This runs the package directly without installing it globally.

git clone https://github.com/yourusername/rdw-mcp-server.git cd rdw-mcp-server npm install npm run build node build/index.js

After global installation, start the MCP server:

rdw-mcp --http # Runs on port 3000 rdw-mcp --http --port=8080 # Custom port

The server supports both stdio and HTTP transports:

- Stdio: For direct command-line and Claude Desktop integration
- HTTP: For remote access, web integrations, and scalable deployments

When running in HTTP mode (--http), the server provides:

- MCP Endpoint:POST /mcp- Main MCP protocol endpoint
- Health Check:GET /health- Server status and version info
- CORS Support: Cross-origin requests enabled for web integrations
- Stateless Design: No session management, perfect for scaling
- Error Handling: Proper HTTP status codes and JSON-RPC error responses

# Start HTTP server rdw-mcp --http --port=3000 # Health check curl http://localhost:3000/health # MCP requests (requires proper JSON-RPC format) curl -X POST http://localhost:3000/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

VS Code's MCP support (.vscode/mcp.json) uses aserverskey with an explicittype:

Using global installation (recommended):

{ "servers": { "rdw": { "type": "stdio", "command": "rdw-mcp" } } }

{ "servers": { "rdw": { "type": "stdio", "command": "npx", "args": ](#deploy-as-a-remote-mcp-server-cloudflare-workers)["rdw-mcp-server"] } } }

For Claude Desktop, use themcpServerskey shown inConfiguration for Claude Desktopbelow instead.

git clone https://github.com/yourusername/rdw-mcp-server.git cd rdw-mcp-server npm install npm run build node build/index.js

npm install npm run cf:dev # local Worker at http://localhost:8787

npx @modelcontextprotocol/inspector # connect to http://localhost:8787/mcp (Streamable HTTP) or http://localhost:8787/sse (SSE)

npx wrangler login # first time only npm run deploy

- The Worker is public once deployed - anyone with the URL can call the RDW lookup through it. That's fine given it only proxies already-public RDW data with no auth on the RDW side either, but keep it in mind before adding write actions or private data in the future (at that point, add an OAuth provider).
- The Worker usesMcpAgent(from theagentspackage), which is Durable-Object-backed and exposes both/mcp(Streamable HTTP) and/sse(legacy SSE) for broad client compatibility.

{ "mcpServers": { "rdw": { "command": "rdw-mcp" } } }

{ "mcpServers": { "rdw": { "command": "npx", "args": ["rdw-mcp-server"] } } }

{ "mcpServers": { "rdw": { "command": "node", "args": ["C:\\ABSOLUTE\\PATH\\TO\\rdw-mcp\\build\\index.js"] } } }

{ "mcpServers": { "rdw": { "command": "node", "args": ["/ABSOLUTE/PATH/TO/rdw-mcp/build/index.js"] } } }

This server uses official RDW (Dutch vehicle authority) open data APIs, verified live againstopendata.rdw.nl:

- Base API:https://opendata.rdw.nl/resource/
- Vehicle Registration: Datasetm9d7-ebf2- Basic vehicle information and specifications
- Fuel & Emissions: Dataset8ys7-d773- Fuel types, emissions, and environmental data
- APK / Inspection Reports: Datasetsgfe-77wx("Meldingen Keuringsinstantie") - Periodic inspection report history and resulting APK expiry dates
- Registration History: Datasetdb8s-mw3u("Kenteken-tenaamstelling") - Registration/ownership-change history
- Axle Specifications: Dataset3huj-srit- Technical axle load specifications
- Body Types: Datasetvezc-m2t6- Carrosserie and body type classifications
- Technical Defects: Dataseta34c-vvps("Geconstateerde Gebreken") - Defect codes found during inspections

Note: RDW's open data doesnotexpose a per-vehicle recall dataset (only a general recall-campaign catalog with no license-plate field) or a separate per-vehicle color history dataset - colors are already covered by the base vehicle record. Open-recall status comes from a flag on the base vehicle record instead.

All data is retrieved in real-time from official government sources and is publicly available.

- No Data Storage: This server does not store any vehicle data locally
- Real-time Queries: All requests are forwarded directly to RDW APIs
- Public Data Only: Only publicly available registration data is accessed
- No Authentication: No personal or sensitive data is required or processed

The RDW API may impose rate limits. If you encounter rate limiting:

- Wait a few seconds between requests
- Avoid making bulk requests in quick succession
- Consider implementing delays in your application logic

Once connected to an MCP client like Claude Desktop, you can ask questions like:

- "Look up license plate 12-ABC-3"
- "What information is available for kenteken XYZ-123?"
- "Tell me about the vehicle with plate 1-ABC-23"
- "Show me all data for license plate ABC-12-D"
- "Get complete RDW information for kenteken DEF-456"

- "What are the emissions data for kenteken ABC-12-D?"
- "Show me the APK history for license plate XYZ-456"
- "Are there any recalls for vehicle 12-ABC-3?"
- "What's the registration history of kenteken DEF-456?"
- "Show me technical defects for license plate GHI-789"

- "What's the towing capacity of vehicle 12-ABC-3?"
- "Show me axle specifications for kenteken XYZ-456"
- "Are there any open recalls for license plate ABC-12-D?"
- "What defects were found during inspections for kenteken DEF-456?"
- "Show me the complete inspection history for license plate GHI-789"

- Language: TypeScript
- Runtime: Node.js (stdio / HTTP) or Cloudflare Workers (remote MCP)
- Protocol: Model Context Protocol (MCP)
- Transport: Standard I/O (stdio), Streamable HTTP, or SSE (Cloudflare Workers deployment)
- Validation: Zod schemas for input validation
- API: RESTful calls to RDW open data endpoints

The server includes comprehensive error handling for:

- Invalid license plates (wrong format or non-existent)
- Network connectivity issues
- API rate limiting and timeouts
- Missing or malformed data from RDW API
- Invalid search parameters

- Ensure Node.js version is 18.0.0 or higher:node --version
- Try reinstalling:npm uninstall -g rdw-mcp-server && npm install -g rdw-mcp-server

- Check your internet connection
- Verify the license plate format (Dutch plates: XX-XXX-X, XXX-XX-X, etc.)
- Some older vehicles may not have complete data in the RDW database

- Verify your configuration matches the installation method (global vs npx)
- If using global installation, ensurerdw-mcpcommand works in terminal
- If using npx, ensurenpx rdw-mcp-serverworks in terminal
- Restart Claude Desktop after configuration changes
- For development setups, ensure the absolute path and build directory are correct
- Check the console output for error messages
- Verify your license plate format matches Dutch standards
- Test with known valid license plates
- Ensure you have an active internet connection

Contributions are welcome! This MCP server can be extended with additional RDW datasets or functionality.

git clone https://github.com/jodur/rdw-mcp-server.git cd rdw-mcp-server

The RDW provides many more datasets that could be integrated, beyond what's already used above:

- Taxi and bus registrations
- Fuel-specific technical variants
- Import/export vehicle history

- Use TypeScript with strict typing
- Follow existing code patterns
- Add JSDoc comments for all functions
- Use Zod for input validation
- Include proper error handling

- NEW: Remote MCP server on Cloudflare Workers: Addedsrc/worker.ts, deployable via the Cloudflare dashboard (Git integration, no CLI needed) orwrangler deploy. Exposes/mcp(Streamable HTTP) and/sse, authless - connect it directly from claude.ai as a custom connector.
- Shared tool logic: Extracted the RDW lookup tool intosrc/rdw-lib.ts, imported unchanged by both the Node entry point and the Worker - no duplicated logic, no behavior change to the existing stdio/HTTP distribution.
- Fixed data gap: The tool previously claimed to return APK history, recalls, ownership history, and defects but never actually fetched them (endpoint doesn't existassumptions that turned out to be wrong). Verified live againstopendata.rdw.nland wired up the real datasets for APK/inspection history (sgfe-77wx), registration/ownership history (db8s-mw3u), and defects found (a34c-vvps).
- Corrected claims: Tool description and README no longer claim recall-history or per-vehicle color-history data that RDW's open API doesn't actually expose - recall status is now accurately described as an open/closed flag, not a history.

- NEW TRANSPORT: Added Streamable HTTP transport support (stateless)
- SDK Compliance: Updated to modern MCP TypeScript SDK patterns
- HTTP Features: Express.js server with/mcpendpoint and/healthcheck
- Command Line: Added--httpand--port=Narguments for HTTP mode
- CORS Support: Cross-origin requests enabled for web integrations
- Stateless Design: New server instance per request, perfect for scaling
- Modern API: Updated from deprecatedserver.tool()toserver.registerTool()
- Enhanced Structure: Better code organization with separated functions
- Dual Transport: Supports both stdio (default) and HTTP transports

- MAJOR ENHANCEMENT: Now queries ALL available RDW databases in a single lookup
- Added APK inspection history and records
- Added vehicle recall and safety action information
- Added complete registration/ownership history
- Added axle load specifications and technical data
- Added body type and carrosserie classifications
- Added technical defect records and inspection findings
- Added additional color information
- Enhanced parallel data fetching for improved performance
- Comprehensive vehicle data from 8+ RDW datasets
- Updated tool description and documentation

- BREAKING CHANGE: Simplified to single comprehensive lookup tool
- Integrated all fuel and emissions data into main license plate lookup
- Removed separate fuel/emissions and vehicle search tools
- Enhanced fuel/emissions data display with emission codes and soot emissions
- Improved data completeness in single query

- Comprehensive README improvements for npm users
- Enhanced installation and usage instructions
- Added troubleshooting and privacy sections
- Improved example queries and development setup
- Fixed package.json references to removed test files

- Enhanced vehicle data output
- Improved license plate normalization
- Added comprehensive error handling
- Enhanced documentation

- Initial release
- Basic license plate lookup
- Fuel and emissions data
- Vehicle search by brand/model

This server uses public RDW data and is not affiliated with the official RDW organization. Always verify critical vehicle information through official channels.

Access live U.S. congressional data from the Congress.gov API.

Access Israeli Government Open Data from the data.gov.il portal.

A Centralized MCP Server for Fetching Data from Many Countries' Govs

Access Socrata Open Data APIs from government data portals.