turso.tech
Turso provides SQLite-compatible databases that can run locally, in the cloud, or in a synced local-first model. Its cloud platform lets users manage organizations, groups, and databases and access those databases remotely.
Turso exposes a REST Platform API, a per-database SQL-over-HTTP API, a hosted MCP server, and the `turso` CLI; all require authentication via Turso-issued tokens or OAuth login.
- Turso MCP serverdetected
- Turso Platform APIdiscovered
- Turso SQL over HTTP APIdiscovered
- Turso CLIdiscovered
Create a Platform API token with the Turso CLI after logging in: turso auth login or turso auth signup, then mint a token such as turso auth api-tokens mint my-token --org my-org. The API docs also show token creation via the Create API Token endpoint. See API authentication for scoping guidance.
Create a database or group token with the Turso CLI, for example turso db tokens create <database-name> or turso group tokens create <group-name>. You can add flags like --read-only, --permissions, and --expiration. The docs note you can also create these via the Platform API. See Platform Tokens and SDK authentication.
$ turso auth loginAcquired by the CLI — running turso auth login opens the auth flow and stores the credential.
Point your MCP client at the server URL and approve access in the browser. The server accepts a Client ID Metadata Document (CIMD), so the client authenticates with its own hosted URL as the client_id — nothing to register.
conventions · 1/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✓https://turso.tech/llms.txt
- API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing