mytesla.io
io.myteslaPublished by mytesla.ioOfficial publisherv1.0.0Updated Oct 24, 2026
Control your Tesla from your AI assistant - climate, charging, access, and security.
Overview
A remote MCP server that lets an AI assistant control a Tesla vehicle's climate, charging, access and security through a mytesla.io account.
- What you can do
- Control vehicle climate settings through the assistant, such as adjusting or starting climate functions as exposed by the server's tools, which are not listed in the manifest. Manage charging, including charging-related actions on the connected vehicle. Handle access, such as locking or unlocking and related entry controls. Manage security settings for the vehicle. All actions run against the user's own Tesla through the mytesla.io service.
- When to use it
- Useful when you want to operate your Tesla hands-free from a chat assistant, for example to adjust climate or charging or to check and change access and security state, without opening the Tesla app.
- Requirements
- A remote MCP endpoint at mcp.mytesla.io reached over streamable HTTP. OAuth authentication is required, so you need a mytesla.io account and must complete the OAuth sign-in flow. No environment variables or headers are declared. Network access to the endpoint is needed.
Installation
In SourceWeft
- Open mytesla.io in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.mytesla%2Fmytesla/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"mytesla-io": {
"type": "http",
"url": "https://mcp.mytesla.io/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.