MCP Teslamate Fleet vs Moxie Docs MCP
A side-by-side look at the MCP Teslamate Fleet and Moxie Docs MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Teslamate Fleet for travel & transportation work as a local process; choose Moxie Docs MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Teslamate Fleet when
- You need dedicated capabilities in the Travel & Transportation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
TESLAMATE_DB_HOST, TESLAMATE_DB_PASS, TESLA_VIN, TESLA_TOKEN_FILE. - You want tools like
tesla_status, tesla_charging_history, tesla_drives.
Choose Moxie Docs MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Travel & Transportation | Knowledge & Memory |
| Quality signal | 55/100 · Good | 80/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | API key required |
| Pricing | Free | Freemium |
| Required env vars | TESLAMATE_DB_HOSTTESLAMATE_DB_PASSTESLA_VINTESLA_TOKEN_FILE | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 2 | 2 |
| Directory activity | 1 views 0 installs 0 upvotes | 36 views 25 installs 4 upvotes |
| Tools | 29 | 12 |
| Full listing | View MCP Teslamate Fleet | View Moxie Docs MCP |
Tools & capabilities
MCP Teslamate Fleet tools 29
tesla_statusCurrent vehicle state — battery, range, location, climate, odometer. Returns the latest position snapshot and vehicle info from TeslaMate.tesla_charging_historyCharging sessions over the last N days. Shows energy added, duration, battery range, and location for each session.tesla_drivesRecent drives — distance, duration, efficiency, start/end locations. Shows the last N days of driving activity with energy consumption.tesla_battery_healthBattery degradation trend — range at 100% charge over time. Shows monthly snapshots of ideal range when battery is at 100%.tesla_efficiencyEnergy consumption trends — Wh/mi over time. Shows weekly average efficiency from driving data.tesla_location_historyWhere the car has been — top locations by time spent. Groups positions by proximity and shows time at each cluster.tesla_state_historyVehicle state transitions — online, asleep, offline. Shows when the car was awake vs sleeping, useful for vampire drain analysis.tesla_software_updatesFirmware version history — all recorded software versions and install dates.tesla_liveLive vehicle data from Fleet API — real-time battery, charging, climate, locks, sentry. More current than TeslaMate (which polls on intervals). Use this when you need the latest state right now.tesla_climate_onStart climate preconditioning — heats or cools cabin to target temp.tesla_climate_offStop climate preconditioning.tesla_set_tempSet cabin temperature target (Fahrenheit). Both driver and passenger.- +17 more on the listing page
Moxie Docs MCP tools 12
moxie.get_ai_contextCompact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.moxie.get_doc_impactGiven the paths you're about to change (and any you're deleting), returns the conventions, gaps, and existing docs whose evidence overlaps them - and flags net-new/undocumented surfaces.moxie.get_api_contextGiven paths you're about to touch, returns structured context for any API endpoints they map to: method, path, schema, and known consumers/features.moxie.review_changeSelf-review a change before opening the PR; returns a severity-ranked verdict (clean / warnings / must-fix) covering convention breaches, stale docs, undocumented surface, and broken references.moxie.get_conventionsDiscovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.moxie.search_docsSemantic + keyword search over generated docs, conventions, gaps, and AI context.moxie.get_doc_gapsUnresolved documentation gaps with severity and the paths they concern.moxie.get_documentation_opportunitiesRecommended doc work: missing docs, drift repairs, and PR templates.moxie.get_documentation_patternsHow the repository organizes and maintains its docs (where new docs belong).moxie.list_docsPaginated, section-grouped table of contents of every generated doc.moxie.propose_doc_updateAdd or update a doc as part of your current change; returns the target path + Markdown to write into your branch.moxie.propose_doc_removalRemove a Moxie-tracked doc your change makes obsolete; returns the path to delete in your branch.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Teslamate Fleet
{
"mcpServers": {
"lodordev-mcp-teslamate-fleet": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/lodordev/mcp-teslamate-fleet",
"mcp-teslamate-fleet"
],
"env": {
"TESLAMATE_DB_HOST": "YOUR_TESLAMATE_DB_HOST_HERE",
"TESLAMATE_DB_PASS": "YOUR_TESLAMATE_DB_PASS_HERE",
"TESLA_VIN": "YOUR_TESLA_VIN_HERE",
"TESLA_TOKEN_FILE": "YOUR_TESLA_TOKEN_FILE_HERE"
}
}
}
}
Moxie Docs MCP
{
"mcpServers": {
"moxie-docs-mcp": {
"command": "npx",
"args": [
"-y",
"moxie-docs"
]
}
}
}
Frequently asked questions
MCP Teslamate Fleet is categorized under Travel & Transportation and uses a local stdio subprocess. Moxie Docs MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick MCP Teslamate Fleet for travel & transportation work and Moxie Docs MCP for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Teslamate Fleet is listed as free. Auth: oauth 2.0. Moxie Docs MCP is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add lodordev-mcp-teslamate-fleet and moxie-docs-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Teslamate Fleet has a quality signal of 55/100 (Good) with 1 views, 0 installs and 2 GitHub stars. Moxie Docs MCP has 80/100 (Excellent) with 36 views, 25 installs and 2 GitHub stars.
