Dealer Fusion MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Dealer Fusion MCP Serversearch inventory for Toyota Camry 2024 in stock"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Dealer Fusion Workspace
Intelligence layer for an automotive dealership network.
Reads CRM, DMS, CDP, and Adobe Analytics data; responds to and qualifies customers; writes back to CRM; emits PII-free OEM signals.
Architecture
Dealer_Fusion_Workspace/
dealer_fusion_mock_data_stub_v1/ — 31 JSONL data files + 11 JSON schemas
dealer_fusion_core/ — shared DuckDB loader + privacy helper
dealer_fusion_mcp/ — FastMCP server (port 4010, Bearer auth)
dealer_fusion_explorer/
backend/ — FastAPI CRUD + graph API (port 8020)
frontend/ — React + Vite + TypeScript (port 5200)
start_explorer.sh — stable backend start scriptRelated MCP server: MCP Business AI Transformation
Prerequisites
Python 3.11+
Node.js 18+
npm 9+
Quick start
# 1 — Install Python dependencies
pip install -e dealer_fusion_core/
pip install -r requirements.txt
# 2 — Terminal 1: MCP server
cd /path/to/Dealer_Fusion_Workspace
python3 -m dealer_fusion_mcp.server
# 3 — Terminal 2: Explorer backend (use the script — limits file-watching to src dirs only)
./start_explorer.sh
# 4 — Terminal 3: Explorer frontend
cd dealer_fusion_explorer/frontend
npm install
npm run dev -- --port 5200Open the Explorer UI at http://localhost:5200
Services
Service | Port | Start command |
MCP Server | 4010 |
|
Explorer Backend | 8020 |
|
Explorer Frontend | 5200 |
|
Environment variables
Variable | Default | Description |
|
| MCP server port |
|
| Bearer token for all MCP requests |
| auto-resolved | Override path to |
| auto-resolved | Override path to |
|
| Explorer backend port |
MCP server (14 tools)
Authentication: Authorization: Bearer dev-token
Protocol: MCP streamable HTTP / SSE — POST http://localhost:4010/mcp
Lead & CRM
Tool | Required args | Returns |
|
|
|
|
|
|
|
|
|
|
| 11-section view: customer, CRM, DMS, CDP, identity graph, segments, leads, activities, appointments, deals, service history |
Inventory & DMS
Tool | Required args | Returns |
|
|
|
|
|
|
|
|
|
|
|
|
Analytics & CDP
Tool | Required args | Returns |
|
|
|
|
|
|
|
|
|
Dealer Ops
Tool | Required args | Returns |
|
|
|
|
|
|
|
|
|
decision_type must be one of: acknowledge_and_escalate · acknowledge_and_nurture · suppress_marketing_or_privacy_only · merge_duplicate_then_update_owner
Explorer API (http://localhost:8020)
GET /api/entities — all 31 entity types with record counts
GET /api/{entity}/list?page=&limit=&search= — paginated, searchable table
GET /api/{entity}/{id} — single record
POST /api/{entity} — create record
PUT /api/{entity}/{id} — update record
DELETE /api/{entity}/{id} — soft-delete (sets deleted_at)
GET /api/customers/{customer_key}/golden-record — force-graph payload for Golden Record view
GET /api/search?q= — cross-entity full-text search
GET /api/schema — all 31 tables with columns, row counts, and FK relationships
GET /health — health checkExplorer UI views
Tab | Description |
Entity Browser | Browse, search, edit, and soft-delete records across all 31 tables |
Golden Record | Search by name / email / CUST_XXXXX ID → interactive force-graph of linked entities |
Dealer Inbox | Live lead triage view sorted by urgency: handover → temperature → score |
KPI Dashboard | OEM network KPIs with dealer filter and trend charts |
Schema | ERD-style force-graph of all 31 tables with FK edges, domain colour-coding, and column explorer |
Data model
31 tables across 8 domains — all joined on customer_key.
Domain | Tables |
Core |
|
CRM |
|
DMS |
|
CDP |
|
Adobe |
|
Dealer Fusion |
|
Reference |
|
OEM |
|
Key joins: customers.customer_key → CRM, DMS, CDP, Adobe, and Dealer Fusion tables. See dealer_fusion_mock_data_stub_v1/DATA_DICTIONARY.md for the full relationship map.
Tests
# Python — MCP server + Explorer backend
python3 -m pytest dealer_fusion_mcp/tests/ dealer_fusion_explorer/backend/tests/ -v
# Frontend — Vitest
cd dealer_fusion_explorer/frontend && npx vitest runMCP smoke test
# Quick connectivity check using the MCP JSON-RPC protocol
python3 - << 'EOF'
import requests, json
r = requests.post("http://localhost:4010/mcp",
headers={"Authorization": "Bearer dev-token",
"Content-Type": "application/json",
"Accept": "application/json, text/event-stream"},
json={"jsonrpc":"2.0","id":1,"method":"initialize","params":{
"protocolVersion":"2024-11-05","capabilities":{},
"clientInfo":{"name":"test","version":"1"}}},
stream=True, timeout=10)
sid = r.headers.get("mcp-session-id")
for line in r.iter_lines():
line = line.decode() if isinstance(line, bytes) else line
if line.startswith("data:"):
d = json.loads(line[5:])
print("Server:", d["result"]["serverInfo"])
print("Session:", sid)
break
EOFPS brand design tokens (Explorer UI)
--ps-bg-primary: #0A0B0D
--ps-bg-surface: #141518
--ps-bg-elevated: #1E2025
--ps-text-primary: #FFFFFF
--ps-text-secondary: #9CA3AF
--ps-accent: #E63312
--ps-border: rgba(255,255,255,0.10)This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sksachan/dealer-fusion-workspace'
If you have feedback or need assistance with the MCP directory API, please join our Discord server