Turso MCP. Manage distributed databases and edge locations in chat.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Turso MCP Server gives your AI client direct access to manage complex distributed databases. Provision, list, and delete libSQL edge instances—from global locations down to specific connection tokens.
Stop context-switching between your terminal and IDE; manage your entire serverless SQLite infrastructure conversationally.
What your AI agents can do
Create database
Provisions a new, massively distributed Serverless SQLite database given an organization slug, DB name, and target group.
Create database token
Mints and returns a secure connection token that is tied only to the specific database instance requested.
Delete database
Permanently deletes a global libSQL database. Warning: This operation cannot be undone.
You create new distributed libSQL instances using create_database, get architectural details with get_database_details, and permanently remove databases via delete_database.
The server mints secure connection tokens for specific DBs (create_database_token) and handles mandatory key rotation by revoking all old JWT tokens (rotate_database_tokens).
You audit your entire setup by listing organizations, global edge locations, database groups, and all registered databases using list_organizations, list_edge_locations, list_database_groups, and list_databases.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
Turso MCP Server: 10 Tools for Database & Location Ops
Use these tools to monitor, track, and profile every aspect of your Turso edge infrastructure—from organizations down to individual connection tokens.
019d7616create database
Provisions a new, massively distributed Serverless SQLite database given an organization slug, DB name, and target group.
019d7616create database token
Mints and returns a secure connection token that is tied only to the specific database instance requested.
019d7616delete database
Permanently deletes a global libSQL database. Warning: This operation cannot be undone.
019d7616get database details
Provides deep architectural metadata and specific traits for one target libSQL instance.
019d7616list database groups
Retrieves a list of logical groups that orchestrate various database locations within your account.
019d7616list database tokens
Lists all currently active JWT execution tokens associated with your databases.
019d7616list databases
Enumerates the complete, current registry of libSQL Edge Databases across your entire account.
019d7616list edge locations
Looks up and returns physical global Fly.io datacenter mappings (the available locations).
019d7616list organizations
Identifies all root organizational tenants within the Turso Edge SQLite system.
019d7616rotate database tokens
Revokes every pre-existing connection token for a specified database, forcing clients to get new credentials.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Turso, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Forget jumping between your terminal and your IDE just to manage your database stack. This server gives your AI client direct access to handle a distributed fleet of Serverless SQLite databases. You’ll provision resources, audit every connection token, and clean up unused instances—all conversationally.
To start, you need visibility. To see the whole picture, you can run list_organizations to identify all root tenants within the Turso Edge system. If you need to know where your data physically lives, list_edge_locations looks up every global Fly.io datacenter mapping available to you. You'll also use these discovery tools to get a clear picture of your architecture: run list_database_groups to enumerate the logical groups that orchestrate various database locations, and then list_databases gives you the complete registry of every single libSQL Edge Database instance across your account.
Need to dig deeper into one specific setup? get_database_details pulls up deep architectural metadata and specific traits for any target libSQL instance. You'll also know exactly which credentials are active by running list_database_tokens, which shows every JWT execution token currently associated with your databases.
When it comes to building out your data layer, you use create_database to provision a new, massively distributed Serverless SQLite database; you specify the organization slug, DB name, and target group when doing so. If you need to secure that new instance, the server mints a unique connection credential using create_database_token, generating a token tied only to that specific database.
You'll also manage access by running rotate_database_tokens for any specified database; this revokes every pre-existing connection token and forces your clients to grab brand new credentials.
If you mess up, or if an instance is totally deprecated, you use delete_database. Be careful with that one—it permanently wipes a global libSQL database, and there’s no undo button on that operation. Essentially, this server gives you full lifecycle control: you can provision resources using create_database, check the specific setup details with get_database_details, and permanently remove databases via delete_database.
How Turso MCP Works
- 1 Subscribe to the server and provide your Turso API Token.
- 2 Your AI client uses this token to authenticate all requests against your database fleet.
- 3 You ask your agent to perform an action (e.g., 'Check if the staging DB exists') and it runs the appropriate tool.
The bottom line is: Your agent becomes a full-stack command center for managing Turso resources, eliminating the need to copy/paste CLI commands into a separate window.
Who Is Turso MCP For?
Platform engineers and DevOps teams who spend too much time switching between their local terminal and monitoring dashboards. This server is for anyone needing to manage multi-region, distributed state without breaking flow or context.
Runs token rotation (rotate_database_tokens) after a security incident or validates group migration plans across multiple DBs.
Uses list_edge_locations and get_database_details to map physical data centers to specific libSQL instances for compliance checks.
Quickly provisions temporary test environments (create_database) or retrieves connection tokens for local debugging without leaving the IDE.
What Changes When You Connect
- Stop losing context. Instead of opening a separate CLI window to manage resources, your AI agent runs tools like
list_databasesandget_database_detailsright inside your IDE or chat client. It's all one flow. - Instant security response. If you suspect compromised credentials, run
rotate_database_tokens. This function immediately invalidates every old JWT token for a database without manual key management. - Global visibility on demand. Use
list_edge_locationsto check which physical data centers are available globally. You can't provision resources if you don't know where they're going. - No more guessing the setup. By running
list_organizationsfirst, your agent identifies the correct root tenant before attempting any provisioning or management action. - Speed up testing environments. Need a throwaway DB for a pull request? Use
create_databaseto provision it on the fly and get connection tokens withcreate_database_token—all in seconds.
Real-World Use Cases
Auditing Orphaned Resources
A system admin needs to clean up. They ask their agent: 'Show me all databases and which organizational tenants they belong to.' The agent runs list_databases and list_organizations, giving a complete manifest of potential zombie resources that need cleanup.
Scaling Out for New Regions
A platform engineer needs to expand their service globally. They ask the agent to check available locations, triggering list_edge_locations. This tells them exactly which physical datacenter mappings are ready for a new deployment group.
Debugging Connection Failures
A developer hits a '401 Unauthorized' error. They ask the agent to run rotate_database_tokens and then generate a fresh token using create_database_token. This instantly fixes the credential issue without touching any config files.
Validating Group Structure
A backend developer is migrating services. They ask the agent to 'list all logical groups and their current DBs.' The agent runs list_database_groups and compares the output against the expected group structure before starting migrations.
The Tradeoffs
Deleting without checking scope
Running 'delete database' on a critical production DB because you thought it was a test instance. You didn't check the associated groups or tokens first.
→
Before deleting, always run get_database_details and cross-reference with list_database_groups. This confirms which logical group owns the resource and verifies its current status.
Manual token rotation
Manually updating connection strings across dozens of services after an old key is compromised. Slow, error-prone, and time-consuming.
→
Use rotate_database_tokens. This single command instantly revokes all old credentials for the target database, ensuring immediate security coverage.
Assuming a DB exists
Trying to connect or provision resources without first verifying if the organization slug is correct.
→
Always start by running list_organizations and then use list_databases to verify the exact database name before attempting any write operations like create_database.
When It Fits, When It Doesn't
Use this MCP Server if your workflow involves complex, distributed infrastructure management—specifically, managing multiple environments across different global edge locations. You need tools that handle resource provisioning (create_database), security auditing (token rotation and listing), and discovery across an entire fleet.
You should not use this server if you are just running simple local SQLite scripts or only managing a single database instance on one machine. For basic, isolated tasks, your standard CLI or local library functions are faster. This tool is for the operations engineer dealing with system-wide state and distributed services.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Turso. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Managing global databases shouldn't require jumping between five different dashboards.
Today, managing a distributed database fleet means juggling logins: you check one dashboard for the organizational tenants, then switch to another CLI window to list all groups. If you need to provision or audit anything, you risk context-switching and losing your place in the operational flow.
With this MCP server, that whole sequence collapses into a single conversation with your agent. You ask it to check locations (`list_edge_locations`), then create a database (`create_database`), and get its token—all without leaving your chat window. It just works.
Turso MCP Server: Full Control Over Your Database State
The biggest headache goes away when you don't have to manually check token expiration dates or remember which groups own which databases. Running `list_database_tokens` and then using `rotate_database_tokens` becomes a two-line conversation instead of a multi-step, high-risk manual process.
This isn't just an API wrapper; it's your full operational command center for libSQL. You manage the entire lifecycle—from discovery to deletion—through simple prompts.
Common Questions About Turso MCP
How do I list all my databases using the Turso MCP Server? +
You run list_databases. This tool gives you a complete registry of every single libSQL Edge Database instance currently managed by your account.
What does 'token rotation' mean when I use rotate_database_tokens? +
Token rotation means the server revokes all existing JWT connection tokens for that database. Any client trying to connect with old credentials will be denied access immediately, forcing them to get a fresh token.
Can I find out which physical data centers are available using Turso MCP Server? +
Yes. Use list_edge_locations. This tool looks up all the global Fly.io datacenter mappings, showing you where your database can physically run.
What if I want to create a new test DB using create_database? +
You provide three parameters: the organization slug, the desired database name, and the target group. The server then provisions the massively distributed instance for you.
How do I use the `create_database_token` tool to restrict database access? +
The create_database_token tool mints a connection token that is strictly tied to one specific database instance. This means the generated JWT cannot be used against any other resources within your organization, vastly tightening security scope.
What precautions should I take before running the `delete_database` tool? +
This action is irreversible; always confirm the database slug and target group first. The tool permanently deletes a global libSQL instance, removing all associated data across its edge locations immediately.
What does the `get_database_details` tool show me about a specific database? +
This tool provides deep architectural traits for any target libSQL instance. You can inspect metadata like replication status, group membership, and current resource allocation without connecting to it.
How can I use `list_database_groups` to understand my database architecture? +
It shows the logical groups that orchestrate your distributed databases. This helps you map out how different physical locations and individual DBs are grouped together for management.
Can my AI agent provision a new database in a specific edge location? +
Yes. You can ask your agent to list available edge locations first, and then instruct it to create a new database in a logical group hosted in that region. Ensure you provide the target group name so the database is correctly allocated to your application fleet.
How can I quickly revoke database access if a token is compromised? +
Simply ask your agent to invalidate or rotate the tokens for that specific database name. The AI will hit the /invalidate endpoint, blocking all old tokens instantly. Afterwards, you can ask for a fresh secure token with a 24-hour expiration.
Can the agent check if I am approaching my dataset limits? +
Yes. When querying the details of a specific database, the agent retrieves storage metadata and group allocation facts. You can ask the AI to summarize your database sizes and flags to see which instances might need an upgrade or clean-up.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Notion
Manage your Notion workspace, databases, and pages via AI.
PeerTube (YouTube Alternative)
Interact with decentralized PeerTube instances — manage video feeds, download content, and handle user registration via AI.
Checkly
Manage application monitoring and E2E testing via Checkly — track API uptime, trigger checks, and monitor performance directly from any AI agent.
You might also like
Berg System CRM
Close more deals with a CRM built for financial advisors that tracks client relationships, policies, and follow-ups.
UK ONS Trade — International Trade & Business Activity
UK trade and business statistics: trade in goods by country and commodity (imports, exports, balance), business counts by industry and geography from the IDBR register, and experimental traffic camera activity indicators from the ONS.
Systran (Machine Translation API)
Professional machine translation and linguistic analysis via Systran — translate text, detect languages, and perform dictionary lookups.