Documentation
rx7db is an MCP server for the Mazda RX-7 FD3S (1992–2002). Its tools research your question with an internal Claude agent and return one clear answer, with links to diagrams when useful. Each call is billed to your own Anthropic API key.
Knowledge tools
| Tool | Use for |
|---|---|
troubleshoot | Diagnose a symptom or malfunction and walk through the fix |
cooling | Overheating, temperature swings, coolant loss, and cooling-system health |
job_planner | Plan a known repair, service, or install: parts, tools, torques, service procedures, and verification |
tune | Tuning: AFR targets, timing, ECU settings, tuning symptoms |
wiring | Electrical diagnosis: circuit traces, pinouts, wire colors, multimeter steps (returns diagram images) |
vacuum | Vacuum/pressure hose routing, the "rat's nest", solenoid/actuator testing, sequential-turbo control (returns routing diagrams) |
build_planner | Plan a modification sequence toward a target power level |
turbo_sizing | Airflow/WHP math for turbo and boost combinations |
wheel_fitment | Validate wheel width/offset, tire size, and suspension/fender/brake clearance |
find_parts | Locate OEM or aftermarket parts, with live supersession/stock lookups |
ask | Any other FD3S question (specs, maintenance, how systems work) |
Your AI assistant handles most of the tool details for you. Ask your question in plain language and it will choose the right tool, carry context into follow-up questions, and include your saved vehicle profile when it helps. You shouldn't need to copy session IDs or format tool arguments yourself. Conversations remain available for seven days after your last question.
Answers link directly to any diagrams they cite. We also plan to add inline images for web and app clients when OAuth connector support is ready.
Vehicle config
Pass vehicle_config with your car's year and market, engine and turbo setup,
ECU, and supporting modifications to get more specific answers. Call
set_vehicle once to save the profile and use it on future calls.
Use get_vehicle to view it and clear_vehicle to remove it.
| Tool | Use for |
|---|---|
set_vehicle | Save or replace your vehicle profile |
get_vehicle | Retrieve your saved vehicle profile |
clear_vehicle | Delete your saved vehicle profile |
Plain Markdown is enough. Include what you know, leave out categories that don't apply, and mark uncertain details as unknown rather than guessing. A useful profile looks like this:
# Vehicle profile
## Car
- Year/model: 2002 Mazda RX-7 Type RB-S (FD3S)
- Market: Japan
- Steering: Right-hand drive
- Transmission: Unknown
- Odometer: Unknown
## Engine, turbo, and exhaust
- Engine: 13B-REW; porting and rebuild history unknown
- Turbo: GReddy TD06-20G single-turbo conversion
- Wastegate: External and recirculated; brand and spring pressure unknown
- Intake: GReddy Airinx S
- Intercooler: Custom bar-and-plate V-mount
- Exhaust: RE-Amemiya 90 mm Dolphin tail with resonated mid-pipe
- Catalytic converter: GESi high-flow metal core
- Boost settings: Unknown
- Oil catch can: Radium FD3S
## Fuel and engine management
- ECU: Apexi Power FC; tune details unknown
- Boost controller: HKS EVC-S
- Wideband: Innovate LC-2
- Fuel type, injectors, and fuel pump: Unknown
## Cooling
- Radiator: Koyo V-mount
- Radiator fans: Mishimoto
## Electrical
- Battery: Antigravity ATX20HD lithium battery, relocated with a JP3 kit
- Charging: JP3 alternator voltage-boost adapter harness
## Chassis, suspension, wheels, and brakes
- Chassis: Banzai Racing crossmember brace
- Mounts: Super Now engine and differential mounts
- Suspension: Öhlins coilovers; model and spring rates unknown
- Links: Megan Racing rear toe links; 1320 Performance front end links
- Wheels: Advan GT, 17 × 9.5 +45
- Tires: Advan Neova AD09, 255/45R17
- Brakes: EBC Yellowstuff pads, EBC GD rotors, stainless brake and clutch lines
## Notes
- This list is based on prior-owner records and visible parts.
- Treat anything marked unknown as unverified rather than making an assumption.
Costs & timing
Each tool call uses your Anthropic API key and typically costs about $0.05–$0.50, but long running sessions can cost more. A call can take a few minutes, depending on the question.
When Anthropic reports the usage details, rx7db adds the actual cost and duration of that call to the end of the tool response. The footer looks like this:
[session_id: … | 3 turns | $0.0412 | 24.3s]Your assistant can read this footer even if it doesn't repeat it in the answer you see. Depending on your client, the footer may appear in the conversation, inside expandable tool details, or only in the raw tool response. You can ask, “How much did that rx7db call cost?” and your assistant should answer from the footer. To estimate the cost of a longer conversation, ask it to add the amounts from each rx7db call in that conversation.
The amount in the footer covers that individual rx7db call, not all usage on your Anthropic account. Cost or duration may be absent when Anthropic doesn't return that metric. Your Anthropic usage dashboard remains the source of truth for total account charges.