Schema | tesla-mcp

tesla-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`TESLA_REGION`	No	Tesla region. One of na, eu, or cn. A wrong region returns HTTP 421.
`TESLA_TOKEN_KEY`	Yes	AES key used to encrypt the Tesla tokens. It is not written into the token file.
`TESLA_MCP_DATA_DIR`	No	Overrides the data directory. Default is /workspace/.tesla-mcp/ on the Grok Bot computer, which holds the encrypted tokens (tokens.json.enc) and history (history.db).	/workspace/.tesla-mcp/
`TESLA_ENABLE_COMMANDS`	No	Set to true to request the vehicle_cmds scope. Only used by the optional tesla-commands-mcp program, which is off by default; tesla-mcp itself never requests vehicle_cmds.	false
`TESLA_ENABLE_LOCATION`	No	Set to true to enable the vehicle_location scope (opt-in). You must sign in again after changing it.	false
`TESLA_COMMANDS_DRY_RUN`	No	Set to false (0, no, and off also turn it off) to leave dry-run mode for the optional vehicle commands. A blank or unrecognized value stays in dry-run.	true
`TESLA_ENABLE_CHARGING_HISTORY`	No	Set to true to enable the vehicle_charging_cmds scope for charging history (opt-in, grants charge control too). You must sign in again after changing it.	false

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
No tools

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

This server cannot be deployed

ActivityMaintained

ResponsivenessNo issues