Schema | tesla-fleet-mcp

tesla-fleet-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`TESLA_VIN`	No	Default vehicle if tools omit vin
`TESLA_REGION`	No	eu (default) or na	eu
`MCP_TRANSPORT`	No	Set to `http` to start Streamable HTTP instead of stdio
`TESLA_AUDIENCE`	Yes	Fleet base URL for your region (EU example in env.example)
`TESLA_MCP_HOST`	No	Bind address	0.0.0.0
`TESLA_MCP_PORT`	No	Bind port	8787
`TESLA_CLIENT_ID`	Yes	Developer app client id
`TESLA_MCP_TOKEN`	No	Bearer gate for Streamable HTTP. Not a Fleet/Tessie token
`TESLA_CACHE_PATH`	No	Token cache path	./token-cache.json
`TESLA_COMMAND_BASE`	No	Proxy origin, e.g. https://127.0.0.1:4443
`TESLA_REDIRECT_URI`	Yes	Must match the app's allowed redirect (e.g. https://your.domain/callback)
`NODE_EXTRA_CA_CERTS`	No	Proxy TLS CA if you use a self-signed localhost cert
`TESLA_CLIENT_SECRET`	Yes	Developer app secret

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

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/supervised-nl/tesla-fleet-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server