Turso MCP Server

Turso MCP server enabling AI agents to interact with Turso's edge SQLite platform — managing libSQL databases, executing queries, creating and managing database groups, and leveraging Turso's globally distributed SQLite for edge-native applications.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Developer Tools turso sqlite edge-database mcp-server libsql serverless edge
⚙ Agent Friendliness
74
/ 100
Can an agent use this?
🔒 Security
78
/ 100
Is it safe for agents?
⚡ Reliability
76
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
72
Documentation
78
Error Messages
75
Auth Simplicity
80
Rate Limits
65

🔒 Security

TLS Enforcement
100
Auth Strength
75
Scope Granularity
62
Dep. Hygiene
78
Secret Handling
78

HTTPS enforced. Separate management and database tokens. SOC 2. No fine-grained scopes.

⚡ Reliability

Uptime/SLA
78
Version Stability
78
Breaking Changes
75
Error Recovery
72
AF Security Reliability

Best When

An agent needs to query or manage globally distributed SQLite databases — especially for edge-native or per-user database architectures.

Avoid When

You need a full-featured RDBMS with complex transactions or high-write throughput.

Use Cases

  • Creating and managing Turso databases from infrastructure agents
  • Executing SQL queries against Turso databases from data agents
  • Managing database replication and multi-region groups from ops agents
  • Monitoring database usage and quotas from analytics agents
  • Provisioning per-user databases for multi-tenant app agents
  • Migrating SQLite databases to Turso's edge platform

Not For

  • High-write transactional workloads (Turso is read-optimized edge SQLite)
  • Teams using PostgreSQL, MySQL, or other full RDBMS
  • Non-edge use cases where latency at scale doesn't matter

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
Yes
Webhooks
No

Authentication

Methods: api_token
OAuth: No Scopes: No

Turso platform API tokens for management API. Database-level auth tokens for SQL access. Tokens are organization-scoped — no fine-grained resource scopes.

Pricing

Model: usage-based
Free tier: Yes
Requires CC: No

Very generous free tier (500 databases!). Per-database-count pricing. Ideal for multi-tenant per-user database architectures. MCP server is community open source.

Agent Metadata

Pagination
cursor
Idempotent
Full
Retry Guidance
Not documented

Known Gotchas

  • Two token types: platform API token and per-database auth token — use correct one
  • Organization slug required for management API calls
  • libSQL extends SQLite with some incompatibilities — not 100% SQLite-compatible
  • Database URLs use libsql:// scheme — different from standard HTTP
  • Group-level vs database-level operations have different API paths
  • Edge replication latency — eventually consistent across regions

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Turso MCP Server.

$99

Scores are editorial opinions as of 2026-03-06.

5220
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered