General Tools

tuneworks.ai

Provides automotive tuning guidance, tire temperature analysis, and vehicle management for car enthusiasts.

1 endpoint24 known toolsFirst detected September 8, 2026Last detected September 8, 2026

ENDPOINT 1

https://tuneworks.ai/mcp

No auth detected

MCP server metadata

Name: tuneworks-mcp
Version: 0.1.0

Capabilities

toolsextensions.io.modelcontextprotocol/skills

Server instructions

TuneWorks MCP has two tiers. Without authentication, it exposes three free setup helpers: handling diagnosis, tire temperature analysis, and autocross damper adjustment. With authentication, it exposes connected /app garage tools for vehicles, setups, sessions, maintenance, shop lists, Share Build, and bounded log context. /app/admin, billing administration, checkout, arbitrary SQL, raw database access, deletes, and user impersonation are not available. Sending Share Build is an external email action and requires explicit user confirmation.

Known tools 24

diagnose_handling_issue

Use this without authentication for understeer/oversteer setup guidance.

Inferred read-only

analyze_tire_temperatures

Use this without authentication to interpret inside/middle/outside tire temperature readings.

Inferred read-only

recommend_autocross_damper_adjustment

Use this without authentication for a bounded shock/damper adjustment recommendation.

Inferred read-only

get_tuneworks_app_capabilities

Use this when the user asks what TuneWorks can do with free public tools or with their connected garage, vehicles, setups, sessions, maintenance, shop lists, Share Build, and log history.

Inferred read-only

create_vehicle

Use this when the connected user explicitly asks to add a vehicle to their TuneWorks garage.

Inferred read-only

update_vehicle

Use this when the connected user explicitly asks to edit an existing TuneWorks vehicle.

Potential side effects

get_garage_summary

Use this when the user asks for an overview of their TuneWorks garage, recent activity, saved vehicles, setups, sessions, maintenance, or lists.

Inferred read-only

list_vehicles

Use this when the user asks to see, choose, or reference vehicles saved in their TuneWorks app garage.

Inferred read-only

get_vehicle_context

Use this when the user asks about one saved TuneWorks vehicle, including its setup, session, maintenance, list, or log context.

Inferred read-only

list_setups

Use this when the user asks for chassis setups or setup history saved in their signed-in TuneWorks app account.

Inferred read-only

create_setup

Use this when the connected user explicitly asks to save a new TuneWorks setup for a vehicle.

Inferred read-only

update_setup

Use this when the connected user explicitly asks to edit an existing TuneWorks setup revision.

Potential side effects

list_sessions

Use this when the user asks for driving sessions, events, track days, autocross runs, or session notes saved in TuneWorks.

Inferred read-only

create_session

Use this when the connected user explicitly asks to save a new TuneWorks driving session.

Inferred read-only

update_session

Use this when the connected user explicitly asks to edit an existing TuneWorks driving session.

Potential side effects

list_maintenance

Use this when the user asks for service reminders, maintenance history, due work, or completed maintenance saved in TuneWorks.

Inferred read-only

create_maintenance

Use this when the connected user explicitly asks to create a TuneWorks maintenance reminder/service item.

Potential side effects

update_maintenance

Use this when the connected user explicitly asks to edit a TuneWorks maintenance reminder/service item.

Potential side effects

list_shop_lists

Use this when the user asks for reusable shop lists, event prep lists, task lists, or parts lists saved in TuneWorks.

Inferred read-only

create_shop_list

Use this when the connected user explicitly asks to create a TuneWorks shop list, task list, or parts list.

Potential side effects

update_shop_list

Use this when the connected user explicitly asks to edit a TuneWorks shop list, task list, or parts list.

Potential side effects

get_share_build_options

Use this when the user wants to choose existing TuneWorks vehicles, setups, and sessions for Share Build.

Inferred read-only

preview_share_build

Use this before sending Share Build to summarize the selected vehicle, setups, sessions, recipients, and message.

Potential side effects

send_share_build

Use this only after explicit user confirmation to email selected TuneWorks vehicle, setup, and session details to up to 3 recipients.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.tuneworks-mcp]
url = "https://tuneworks.ai/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "tuneworks-mcp": {
      "type": "http",
      "url": "https://tuneworks.ai/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: tuneworks-mcp
Remote MCP URL: https://tuneworks.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "tuneworks-mcp": {
      "url": "https://tuneworks.ai/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "tuneworks-mcp": {
      "type": "http",
      "url": "https://tuneworks.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "tuneworks-mcp",
  "transport": "streamable-http",
  "url": "https://tuneworks.ai/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.