> For the complete documentation index, see [llms.txt](https://docs.quadratichq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quadratichq.com/connections/mariadb.md).

# MariaDB

## MariaDB

You can create your MariaDB connection from either your team's dashboard or directly inside a spreadsheet. From the Dashboard, navigate to the Connections menu item. Or from inside a spreadsheet, press `/` and then Manage connections.

MariaDB connections use the same details as MySQL.

### Connection details

To connect to your MariaDB database, enter the following parameters in the Team connections modal:

* **Connection name** — the display name for your connection across Quadratic and your team
* **Hostname** — your database's host, an IP address or URL
* **Port** — typically `3306`
* **Database** — the database name
* **Username / Password** — credentials with the access you want available in Quadratic

### IP allow-list

{% hint style="info" %}
You must whitelist both Quadratic IP addresses to make connections, which are:\
44.240.255.40\
54.68.134.35

* These IP addresses do not apply to self-hosted instances
  {% endhint %}

Once you've made your connection, you can use it directly in spreadsheets to read data to your spreadsheets. Learn how in SQL - getting started.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.quadratichq.com/connections/mariadb.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.