Turso MCP server

What the model can do

Turso hosted SQLite (libSQL) management: the organization's databases with group, primary region, protection and blocked reads or writes, a database's configuration, instances and replicas, its usage (rows read and written, storage) and top queries, groups and their locations, available locations, the organization's plan, usage and limits, members and roles, and the audit log. It never reads table data. When you ask, can create, configure or delete a database, create, protect, unarchive, upgrade or delete a group, add or remove a group's locations, and invite, re-role or remove members.

Reads

• turso_list_databasesTurso databases in the organization (listDatabases): name, id, group, primary region, delete protection, blocked reads or writes…
• turso_get_databaseOne Turso database in full: group, region, protection and blocks (getDatabase), its configuration (size limit…
• turso_database_usageA Turso database's activity over a period (getDatabaseUsage): rows read and written, storage and bytes synced, in total and per instance…
• turso_list_groupsTurso groups (listGroups): name, id, primary location, locations and delete protection.
• turso_list_locationsLocations where Turso can create or replicate a group (listLocations): code and name.
• turso_get_usageThe Turso organization's plan and this billing cycle (getOrganization, getOrganizationSubscription, getOrganizationUsage): plan, billing timeline…
• turso_list_membersMembers of the Turso organization (listOrganizationMembers): username and role (owner, admin, member, viewer).
• turso_list_audit_logsThe Turso organization's audit log, newest first (listOrganizationAuditLogs): what happened (code such as db-create, group-delete, org-member-add)…

Acts, when you ask

These change something in Turso. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• turso_create_databaseCreates a new, empty Turso database in an existing group (createDatabase), or a copy of another database in the organization…
• turso_update_databaseChanges a Turso database's configuration (updateDatabaseConfiguration): size limit, delete protection, blocking all reads or all writes…
• turso_delete_databaseDeletes a Turso database and its data (deleteDatabase).
• turso_create_groupCreates a Turso group with its primary in the location given (createGroup), to hold databases.
• turso_delete_groupDeletes a Turso group and every database in it (deleteGroup), and revokes every token scoped to it.
• turso_set_group_protectionTurns a Turso group's delete protection on or off (updateGroupConfiguration).
• turso_unarchive_groupUnarchives a Turso group that was archived for inactivity (unarchiveGroup), so its databases serve again.
• turso_upgrade_groupUpgrades every database in a Turso group to the latest libSQL server version (updateGroupDatabases).
• turso_add_group_locationAdds a location to a Turso group (addLocationToGroup), creating a replica of every database in the group there.
• turso_remove_group_locationRemoves a location from a Turso group (removeLocationFromGroup), deleting the replicas of its databases there…
• turso_invite_memberInvites a person to the Turso organization with a role (inviteOrganizationMemberV2).
• turso_cancel_inviteDeletes a pending invite to the Turso organization by email (deleteOrganizationInviteByEmailV2); the invite link stops working.
• turso_update_member_roleChanges a Turso organization member's role to admin, member or viewer (updateMemberRole), widening or narrowing what they can do.
• turso_remove_memberRemoves a member from the Turso organization (removeOrganizationMember); they lose access to its databases at once.

Connect it

First connect Turso on Dashboard → Connections, then add Memtro to your client once. The Turso tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Turso connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which databases read the most rows this month?
• › How close is the organisation to its plan's database and storage limits?
• › Which locations does the production group replicate to?
• › Who are the admins in our Turso organisation?
• › Turn on delete protection for the production group.

Questions

Is this an official Turso MCP server?

No. It is Memtro's MCP server with Memtro's Turso connector behind it: the connector reads Turso through its API with the credentials you connect on Dashboard → Connections, and Turso publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Turso?

Only when you ask, and only what it has been granted: create a database in a group, optionally copied from another database (counts toward plan limits); change a database's size limit, delete protection, or block its reads or writes; delete a database; create a group in a location (counts toward plan limits); delete a group and every database in it; turn a group's delete protection on or off; unarchive a group archived for inactivity; upgrade every database in a group to the latest libSQL version; add a location (replica) to a group; remove a location from a group; invite a person to the organization by email or username; cancel a pending invite; change a member's role; remove a member from the organization. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Databases and warehouses

• Postgres MCP server
• MySQL and MariaDB MCP server
• SQL Server MCP server
• BigQuery MCP server
• Snowflake MCP server
• AWS Athena MCP server