Data & Storage · Integration
MySQL
Add MySQL to your product for your customers, and give your AI agents governed access to it.
Embed a MySQL integration so your product can read and write data your customers keep in their own database, without you building and securing a connection layer per customer. Schemas differ per customer and change without warning, so table and column mapping is configuration rather than code, and access is limited to the database user the customer grants. fastn stores credentials encrypted per tenant, handles connection pooling, paginated reads and query throttling, so a large read does not compete with the customer's own application traffic.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own MySQL database so your product queries the tables they choose to expose.
Write or update rows from your product within a scoped database user's permissions.
Map each customer's schema as configuration, so a column rename on their side is not a release on yours.
Keep reads paginated and throttled so a bulk load does not slow the database their product runs on.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent runs a scoped read-only query before it answers a question about the customer's data.
An agent inspects table and column names so it writes a valid query rather than guessing.
An agent performs an approved write within governed permissions, with the statement logged per tenant.
Example prompt
Query this week's failed transactions from the payments table and group them by error code.
Set up MySQL in 4 steps
- 01Open the MySQL connector from your fastn dashboard.
- 02Have each customer supply their own connection details and a scoped database user, stored encrypted per tenant.
- 03Map the tables, columns and queries your product uses, then enable the actions you need.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the MySQL integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a MySQL integration without building it. Your customers connect their own MySQL account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a MySQL update is not your on-call problem.
- One integration serves your product and your agents. The same governed MySQL connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
PostgreSQL
MongoDB AtlasOften used alongside
Tools the same teams tend to run next to MySQL, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceMySQL integration FAQ
How do I add a MySQL integration to my product?
Enable the MySQL connector in your fastn dashboard, then let each customer authenticate their own MySQL account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no MySQL client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own MySQL account?
Yes. Every connection is scoped to the individual customer, so each authorises their own MySQL account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this MySQL integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent runs a scoped read-only query before it answers a question about the customer's data.
Who maintains the MySQL integration?
fastn does. When MySQL changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the MySQL integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large MySQL reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the MySQL integration?
A common starting point: connect their own MySQL database so your product queries the tables they choose to expose. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the MySQL integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding MySQL does not change your per-connector cost. You can start free with 3 connected accounts.
Add MySQL to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.