tyta

MCP运维云端

提供方 Stopa

运维云端 stdio · 本地进程 未标注 社区 / 第三方 Claude DesktopClaude
查看接入方式

A command-line interface for interacting with Toyota Connected Services (EU region), supporting vehicle status queries, remote control, and automation script integration.

一句话选型结论

按资料字段整理

tyta 属于运维云端类 MCP 服务器,stdio · 本地进程,鉴权方式未标注,可直接接入 Claude Desktop、Claude,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类运维云端 传输方式stdio · 本地进程 鉴权未标注 部署方式本地部署
GitHub 星标 2 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

运维云端
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

Local Deployment Vehicle Management Remote Control Python CLI Tool Toyota Services Automation

支持客户端

适用场景

Local DeploymentVehicle ManagementRemote Control

安装与配置

stdio · 本地进程 未标注
客户端在本机拉起子进程,数据不出本机
tyta-mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 python,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
tyta当前 未标注 stdio · 本地进程 本地部署 有 2026-08-06
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Stopa上游标注的维护方 Stopa
分类运维云端本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · python本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-08-06上游最后核验时间

详细介绍

12.0 KB
来自项目仓库与上游目录的原文,未做删改

tyta

A command-line interface for Toyota Connected Services (EU). Communicate with your Toyota vehicle
directly from the terminal or from automation scripts.

> Note: EU region only. Requires a Toyota Connected Services account.

> Disclaimer: This is an unofficial, community-built tool with no affiliation with Toyota.
> It is provided as-is, with no warranty of any kind. AI was used heavily in the making of this tool.
> Toyota may change or discontinue their API at any time without notice, which may break this tool.
> Use at your own risk. The author accepts no liability for any damage, data loss, unintended vehicle
> commands, or service disruption arising from use of this software.

Install```bash

pipx install tyta


Or for development:```bash
pipx install --editable .

Quick Start```bash

Authenticate

tyta auth login

Check auth status

tyta auth status

List your vehicles

tyta vehicles list

Set a default vehicle (so you don't need --vin on every command)

tyta vehicles use JTDKB3FU803012345

Show vehicle status

tyta status


## Global Options

These options are accepted by every command:

| Option | Env Var | Default | Description |
|---|---|---|---|
| `--json` | — | off | Output raw JSON envelope instead of human-readable text |
| `--auth-file PATH` | `TOYOTA_AUTH_FILE` | `~/.config/tyta/auth.json` | Path to auth token file |
| `--config-file PATH` | `TOYOTA_CONFIG_FILE` | `~/.config/tyta/config.json` | Path to config file |
| `--debug` | — | off | Enable debug logs to stderr; show tracebacks on error |

## Environment Variables

| Variable | Description |
|---|---|
| `TOYOTA_USERNAME` | Toyota account email. Used for non-interactive login and headless re-auth. |
| `TOYOTA_PASSWORD` | Toyota account password. Used for non-interactive login and headless re-auth. |
| `TOYOTA_AUTH_FILE` | Override path to the auth token file. |
| `TOYOTA_CONFIG_FILE` | Override path to the config file. |
| `TOYOTA_VIN` | Default VIN for per-vehicle commands. Overridden by `--vin` flag; overrides config default. |

### Headless / CI environments

If `TOYOTA_USERNAME` and `TOYOTA_PASSWORD` are both set, the CLI will re-authenticate
automatically whenever tokens expire — no manual intervention needed.```bash
export TOYOTA_USERNAME="user@example.com"
export TOYOTA_PASSWORD="secret"
tyta status   # re-auths silently if tokens have expired

Commands

Auth```bash

tyta auth login # Authenticate and save tokens
tyta auth logout # Delete saved tokens
tyta auth status # Show authentication state and token expiry


`tyta auth login` supports non-interactive mode via `TOYOTA_USERNAME` and `TOYOTA_PASSWORD`
environment variables.

### Vehicles```bash
tyta vehicles list                    # List all vehicles linked to the account
tyta vehicles use <VIN>               # Set the default VIN (validates against API)
tyta vehicles info [--vin VIN]        # Model, year, colour, fuel type
tyta vehicles capabilities [--vin VIN]
tyta vehicles features [--vin VIN]
tyta vehicles subscriptions [--vin VIN]

Status```bash

tyta status [--vin VIN] # Combined: telemetry + location + lock + health
tyta telemetry [--vin VIN] # Raw telemetry: fuel, odometer, battery
tyta location [--vin VIN] # Raw GPS location: coordinates and timestamp
tyta health [--vin VIN] # Raw vehicle health: warning lights and alerts


`tyta status` returns a combined envelope with all four data sources. Use the individual
commands for targeted queries.

### Electric```bash
tyta electric status [--vin VIN]
tyta electric refresh [--vin VIN]     # Real-time refresh (warns about 12V drain)
tyta electric charge-now [--vin VIN]

tyta electric reserve-charge \
    --day MONDAY --start 07:00 [--end 08:00] [--charge-type startOnly|startEnd] \
    [--vin VIN]

tyta electric set-charging-time \
    --day MONDAY --start 07:00 [--end 08:00] [--charge-type startOnly|startEnd] \
    [--vin VIN]

--day accepts uppercase weekday names: MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY,
SATURDAY, SUNDAY.

--start / --end accept 24-hour time as HH:MM (e.g. 07:30).

--charge-type defaults to startOnly; use startEnd when --end is provided.

Climate```bash

tyta climate status [--vin VIN]
tyta climate settings [--vin VIN]
tyta climate on [--vin VIN]
tyta climate off [--vin VIN]


### Trips```bash
tyta trips list [--from YYYY-MM-DD] [--to YYYY-MM-DD] [--limit N] [--page N] [--routes] [--vin VIN]

trips list defaults to the last 30 days. --limit controls results per page (default 10, max 50);
--page selects the page (default 1). --routes includes per-trip route geometry.

Remote```bash

tyta remote [--vin VIN] # Show remote/lock status (no subcommand)
tyta remote lock [--vin VIN]
tyta remote unlock [--vin VIN]
tyta remote horn [--vin VIN]
tyta remote find [--vin VIN] # Flash lights + sound horn
tyta remote headlights on [--vin VIN]
tyta remote headlights off [--vin VIN]
tyta remote hazard on [--vin VIN]
tyta remote hazard off [--vin VIN]


`tyta remote` with no subcommand shows the current remote/lock status. Action commands
(`lock`, `unlock`, `horn`, etc.) are fire-and-forget: the API acknowledges immediately;
vehicle execution is asynchronous.

## Configuration

tyta reads a JSON config file (default: `~/.config/tyta/config.json`) for persistent settings. Use `tyta config` to manage them:```bash
tyta config show                        # Print all config keys and their current values
tyta config set date_format iso         # iso | human (default: human)
tyta config set distance_unit mi        # km | mi (default: km)
tyta config set default_vin <VIN>       # Set default VIN (also set by `tyta vehicles use`)
Key Accepted values Default Effect
date_format human, iso human human → "24 Mar 2026, 08:04 UTC"; iso → pass-through
distance_unit km, mi km Unit for distance values in trip output
default_vin any string (none) Default VIN used when --vin flag is not provided

Use --config-file PATH (or TOYOTA_CONFIG_FILE env var) to point to a custom config file.

VIN Resolution

For all per-vehicle commands, the VIN is resolved in this order:

  1. --vin flag on the command
  2. TOYOTA_VIN environment variable
  3. default_vin from config file (set via tyta vehicles use)
  4. Auto-select if the account has exactly one vehicle (emits a warning)

Output Format

By default, commands print human-readable text to stdout. Pass --json to get a machine-readable
JSON envelope instead — useful for scripting, piping to jq, or feeding to an LLM.```bash
tyta --json status
tyta --json telemetry --vin JTDKB3FU803012345


### Success```json
{
  "ok": true,
  "warnings": [],
  "data": { ... }
}

Success with warnings```json

{
"ok": true,
"warnings": ["No default vehicle set, using only available vehicle: VIN XXXXXXX"],
"data": { ... }
}


### Error```json
{
  "ok": false,
  "error": {
    "code": "not_authenticated",
    "message": "Not authenticated. Run `tyta auth login`."
  }
}

Error Codes

Code Meaning
not_authenticated No token file found
token_expired Tokens expired and refresh failed
api_error Toyota API returned a non-2xx response
vehicle_not_found Specified VIN not found in account
no_vehicles Account has no linked vehicles
invalid_config Config or token file is malformed
invalid_input User-supplied input is invalid
unknown_error Unexpected exception

Exit Codes

Code Meaning
0 Success
1 Operational error (ok: false)
2 Usage error (bad arguments)

Debugging

Pass --debug to enable verbose logs on stderr and print tracebacks on error:```bash
tyta --debug status
tyta --debug auth login


Logs go to **stderr**; JSON output always goes to **stdout**.

## Shell Completions

tyta supports tab completion for commands, subcommands, and flags in bash, zsh, and fish.

### Install completions

**bash:**```bash
tyta --install-completion bash

zsh:```bash
tyta --install-completion zsh


**fish:**```bash
tyta --install-completion fish

After installing, restart your shell (or source the relevant config file) for completions to take effect.

Show the completion script without installing```bash

tyta --show-completion bash
tyta --show-completion zsh
tyta --show-completion fish


## MCP Server

tyta includes an MCP (Model Context Protocol) server (`tyta/mcp/`) that exposes
Toyota Connected Services operations as structured tools for AI assistants such as Claude Desktop.
This lets an AI assistant query vehicle data and send remote commands on your behalf.

### Option 1 — Single-click install (MCPB bundle)

The easiest way to get started. Download the latest `tyta.mcpb` bundle from the
releases page, open it in Claude Desktop,
and enter your Toyota credentials in the installation dialog. No CLI setup, no config file editing.

See `mcpb/` for the bundle source and packaging details.

**What it does:**
- Collects your Toyota email and password via Claude Desktop's installation UI and stores them
  securely — you never edit a JSON file.
- Installs `tyta` automatically on first launch — no Python or pip required.
- All 14 MCP tools are available immediately after installation.

**Requirements:** Claude Desktop with MCPB support.

---

### Option 2 — Manual setup

For AI clients that don't support MCPB, or if you prefer to manage the installation yourself.

**Step 1 — Install tyta:**```bash
pipx install "tyta[mcp]"

Step 2 — Configure your MCP client.

Pass your Toyota credentials as environment variables so the server can authenticate
automatically on first use:json { "mcpServers": { "tyta": { "command": "tyta-mcp", "env": { "TOYOTA_USERNAME": "user@example.com", "TOYOTA_PASSWORD": "secret" } } } }

For Claude Desktop, add this to:
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json

If installed with pipx, you may need the full path to tyta-mcp
(e.g. /Users//.local/bin/tyta-mcp).

Alternatively, run tyta auth login once beforehand and omit the env block — the server will
use the cached token.


Available tools

Tool Description
auth_status Check authentication status and token expiry
vehicles_list List all vehicles linked to the account
telemetry Fuel level, odometer, 12V battery
location GPS coordinates and last-seen timestamp
remote_status Door lock status and caution indicator count
health Warning lights and health alerts
electric_status EV battery level, charging status, and range
climate_status Climate running state, target temperature, heating/seat options
trips_list Trip history with optional date range filter
trips_show Full detail for a single trip by ID
remote_lock Lock vehicle doors (write operation)
remote_unlock Unlock vehicle doors (write operation)
remote_horn Sound the vehicle horn (write operation)
remote_find Flash lights and sound horn to locate the vehicle (write operation)

Safety: write operations require explicit confirmation

The four write-operation tools (remote_lock, remote_unlock, remote_horn, remote_find)
will not execute unless the AI passes confirm: true as a parameter. This prevents an AI
assistant from accidentally triggering physical vehicle commands. When asking Claude to lock your
car, it will confirm with you before sending the command.


Acknowledgements

tyta is built on the shoulders of pytoyoda — the community Python library for Toyota Connected Services Europe. The API reverse-engineering, authentication flow, and request signing approach in this project are derived directly from pytoyoda's work. Many thanks to @DurgNomis-drol for starting the original project and to the pytoyoda contributors for maintaining it.

License

MIT

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
tyta 怎么安装?

在客户端按下面的安装命令接入:tyta-mcp。装完在客户端配置里引用同一个包或端点。

tyta 怎么在 Claude Desktop、Claude 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

tyta 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

tyta 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

tyta 支持哪些客户端?

资料标注支持 Claude Desktop、Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

tyta 能提供哪些能力?

资料显示能力标签包括 Local Deployment、Vehicle Management、Remote Control、Python、CLI Tool、Toyota Services。具体工具清单以官方文档为准。

tyta 需要什么运行环境?

运行时为 python;属于本地进程,需要在本机装好运行环境。

tyta 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-08-06。