Bouncie MCP Server
An MCP server that connects Bouncie OBD2 vehicle tracking data to AI assistants. It enables users to retrieve real-time vehicle stats, health diagnostics, and detailed trip history through the Bouncie API.
README
Bouncie MCP Server
An MCP (Model Context Protocol) server that exposes the Bouncie vehicle tracking API. Connect your Bouncie OBD2 device data to any MCP-compatible AI assistant.
Features
- Vehicle info — make, model, year, VIN, engine, nickname
- Live vehicle stats — GPS location, speed, fuel level, odometer, engine running status
- Vehicle health — battery status, check engine light (MIL), diagnostic trouble codes (DTCs)
- Trip history — distance, duration, speeds, fuel consumed, hard braking/acceleration, GPS traces
- User profile — authenticated user information
Prerequisites
- A Bouncie account with at least one connected device
- A Bouncie developer app — register at bouncie.dev
- Node.js 18+
Setup
1. Install
npm install
npm run build
2. Get Bouncie API credentials
- Go to bouncie.dev and create an app
- Note your Client ID and Client Secret
- Set a Redirect URI (e.g.
https://example.com/callback) - Under "Users & Devices", authorize your Bouncie account
- Copy the Authorization Code from the device's expanded view
3. Configure environment
Set these environment variables:
| Variable | Required | Description |
|---|---|---|
BOUNCIE_CLIENT_ID |
Yes | Your app's client ID |
BOUNCIE_CLIENT_SECRET |
Yes | Your app's client secret |
BOUNCIE_REDIRECT_URI |
Yes | Redirect URI used during app registration |
BOUNCIE_AUTH_CODE |
One of these | Authorization code (exchanged for token automatically) |
BOUNCIE_ACCESS_TOKEN |
One of these | Pre-obtained access token (skip OAuth exchange) |
4. Add to your MCP client
Claude Desktop / Claude Code
Add to your MCP settings (claude_desktop_config.json or .claude/settings.json):
{
"mcpServers": {
"bouncie": {
"command": "node",
"args": ["/path/to/bouncie-mcp/dist/index.js"],
"env": {
"BOUNCIE_CLIENT_ID": "your-client-id",
"BOUNCIE_CLIENT_SECRET": "your-client-secret",
"BOUNCIE_REDIRECT_URI": "https://example.com/callback",
"BOUNCIE_ACCESS_TOKEN": "your-access-token"
}
}
}
}
Tools
get_vehicles
List all vehicles on the account.
| Parameter | Type | Description |
|---|---|---|
vin |
string (optional) | Filter by VIN |
imei |
string (optional) | Filter by device IMEI |
Returns: Array of vehicles with model info, VIN, IMEI, nickname, and live stats (location, speed, fuel, odometer, engine status, battery, MIL/DTCs).
get_vehicle
Get a single vehicle by VIN or IMEI.
| Parameter | Type | Description |
|---|---|---|
vin |
string (optional) | Vehicle VIN |
imei |
string (optional) | Device IMEI |
At least one identifier is required.
get_trips
Get trip history for a vehicle.
| Parameter | Type | Description |
|---|---|---|
imei |
string | Device IMEI (required) |
starts_after |
string (optional) | ISO date — trips starting after this time |
ends_before |
string (optional) | ISO date — trips ending before this time |
gps_format |
"polyline" | "geojson" (optional) |
GPS data format (default: polyline) |
transaction_id |
string (optional) | Fetch a specific trip |
Note: The date window (
starts_aftertoends_before) must be no longer than 1 week. Defaults to the last 7 days if not specified.
Returns: Array of trips with distance, duration, average/max speed, fuel consumed, hard braking/acceleration counts, odometer readings, and GPS trace.
get_user
Get the authenticated user's profile.
No parameters.
Development
npm run dev # Run with tsx (hot reload)
npm run build # Compile TypeScript
npm test # Run tests
npm run test:watch # Watch mode
npm run lint # Type check
API Reference
This server wraps the Bouncie REST API v1:
- Base URL:
https://api.bouncie.dev/v1 - Auth:
https://auth.bouncie.com/oauth/token - Endpoints:
/vehicles,/trips,/user
Webhook Event Types
Bouncie also supports webhooks (not exposed via this MCP server, but documented here for reference):
| Event Type | Description |
|---|---|
connect |
Device plugged in |
disconnect |
Device unplugged |
battery |
Battery status change (normal/critical) |
mil |
Check engine light on/off with DTC codes |
tripStart |
Trip begins — includes odometer |
tripEnd |
Trip ends — includes odometer, fuel consumed |
tripMetrics |
Trip summary — distance, time, speeds, braking/acceleration |
tripData |
Real-time GPS breadcrumbs during trip |
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.