Schema | tesla-mcp

tesla-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`TESLA_CLIENT_ID`	Yes	Client ID for your Tesla developer application.
`MCP_BEARER_TOKEN`	Yes	Bearer token required for MCP clients to authenticate to /mcp. If unset, every /mcp request is refused.
`TESLA_VEHICLE_ID`	No	Optional Tesla vehicle ID to target.
`NIGHTLY_LOCK_TIME`	No	Local time for the nightly automatic lock.	22:00
`TESLA_CLIENT_SECRET`	Yes	Client secret for your Tesla developer application.
`TESLA_FLEET_BASE_URL`	No	Fleet API base URL for your region. Change this if your Tesla account is outside North America.	North America Fleet API host
`TESLA_PUBLIC_KEY_PEM`	Yes	PEM contents of the P-256 public command key, served at the Tesla well-known public-key endpoint.
`TOKEN_ENCRYPTION_KEY`	Yes	AES-256-GCM key used to encrypt Tesla tokens at rest in a Durable Object.
`NIGHTLY_LOCK_TIMEZONE`	No	Timezone for the nightly automatic lock.	America/New_York
`DANGEROUS_COMMANDS_ENABLED`	No	Gate for dangerous commands. Defaults to "false"; must be explicitly enabled before any dangerous tool could be registered.	false
`TESLA_BOOTSTRAP_REFRESH_TOKEN`	Yes	Tesla OAuth refresh token used to seed the encrypted token store.
`TESLA_COMMAND_PRIVATE_KEY_PKCS8_B64`	Yes	Base64-encoded PKCS#8 DER private key used to sign Tesla Vehicle Command Protocol messages.

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