Turso

Turso MCP integration

Finds the closest Turso region, validates an API token and its expiry, and streams committed table changes on request.

3actions available

What your agent can do with Turso

Every action runs live through MCP. Nothing to build, nothing to maintain.

  • Listen to changes

    Lyro monitors committed table changes in a Turso database in real-time. Teams stay informed about data updates without polling.

  • Closest region

    Lyro identifies the nearest Turso region based on a client's location. Teams optimize database performance by routing to the fastest endpoint.

See all 3 actions

How businesses use Turso + Lyro

Each card is one request a support team gets, and the Turso actions Lyro runs to close it.

  • Place a database where the reads are

    Lyro resolves the closest Turso region to a given client location, so a decision about where to deploy or replicate is based on the nearest region rather than on whichever one was picked first.

    Closest RegionValidate API Token
  • Catch a token before it expires

    Lyro validates the API token and reads back its expiration timestamp, or -1 when the token never expires, so a credential question is answered from the token itself rather than from when someone thinks it was issued.

    Validate API TokenClosest Region
  • Watch a table for committed changes

    Lyro streams insert, update, and delete events for a specific table through the beta listen endpoint, so a change in the database can be surfaced as it commits instead of at the next poll.

    Listen To ChangesValidate API Token
  • Fall back to a health check when streaming is off

    Where the listen endpoint is unavailable, the action falls back to a pipeline health check, so Lyro still reports whether the database is responding rather than returning nothing at all.

    Listen To ChangesClosest Region

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Turso actions it has and picks the ones a request needs.

  1. 01

    Connect Turso

    Authorize the Turso account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.

  2. 02

    Tell your agent what you need

    Describe the job the way you would hand it to a teammate. Lyro maps it to the Turso actions that close it and chains as many as the request needs.

  3. 03

    Watch it work

    The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.

    Get started free
Turso · Lyro

Everything else about Turso

Setup, permissions, and the limits of what Lyro can do inside Turso.

  • No. The /beta/listen endpoint is not available on AWS regions for the Free, Developer, and Scaler plans. Where it is unavailable, Listen To Changes falls back to a /v2/pipeline health check, so Lyro reports reachability instead of a live event stream.

Every action available in Turso

All 3 actions your agent can call on Turso, straight from the live MCP connection.

  • Closest region

    Get the closest Turso region based on client location.

  • Listen to changes

    Listen to committed table changes in a Turso database via the /beta/listen endpoint.

  • Validate API token

    Validates a Turso API token and retrieves its expiration time.

Ready to connect Turso?

Authorize the account and your agent has all 3 actions from the first conversation.

Support agent working at a laptop next to the Lyro mascot