Other clients
Any client that supports remote MCP servers over Streamable HTTP can connect to Teslemetry at:
https://api.teslemetry.com/mcp
There are two ways to authenticate:
- OAuth — supported by clients that can open a browser. Provide only the URL; the client registers itself and sends you to a Teslemetry consent screen to approve access.
- Bearer token — for clients that take static headers, or for unattended/automated use. Generate an access token and send it as
Authorization: Bearer YOUR_TESLEMETRY_TOKEN.
Cursor
Add Teslemetry to ~/.cursor/mcp.json (global) or .cursor/mcp.json in your project:
{
"mcpServers": {
"teslemetry": {
"url": "https://api.teslemetry.com/mcp"
}
}
}
Cursor will prompt you to sign in with OAuth on first use. To skip OAuth, add a bearer token instead:
{
"mcpServers": {
"teslemetry": {
"url": "https://api.teslemetry.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_TESLEMETRY_TOKEN"
}
}
}
}
VS Code (GitHub Copilot)
Add Teslemetry to .vscode/mcp.json in your workspace:
{
"servers": {
"teslemetry": {
"type": "http",
"url": "https://api.teslemetry.com/mcp"
}
}
}
VS Code handles the OAuth sign‑in automatically. Open the Chat view in Agent mode to use the tools.
Other MCP clients
Windsurf, Cline, Zed, Goose, and most other MCP clients use the same shape — a server entry with an http / streamable-http type and the Teslemetry URL. Consult your client's documentation for the exact config file location and field names, then supply:
| Field | Value |
|---|---|
| Transport | Streamable HTTP (http) |
| URL | https://api.teslemetry.com/mcp |
| Auth | OAuth, or Authorization: Bearer YOUR_TESLEMETRY_TOKEN |
Generic / bearer-token config
A minimal, OAuth‑free configuration works in any client that supports headers:
{
"mcpServers": {
"teslemetry": {
"type": "http",
"url": "https://api.teslemetry.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_TESLEMETRY_TOKEN"
}
}
}
}