Data
Give your agent read-only, dialect-aware SQL access to PostgreSQL, MySQL, or SQL Server through ThinAir’s hosted MCP without opening write paths to production.
Overview
co.thinair/data is an MCP server for the Build phase that provides read-only PostgreSQL, MySQL, and SQL Server access through 24 dialect-aware hosted tools.
What is this MCP server?
- 24 dialect-aware hosted MCP tools for read-only database work
- PostgreSQL, MySQL, and SQL Server in one remote endpoint
- Bearer auth via DSN-derived key from https://data.thinair.co/connect
- Streamable HTTP at https://data.thinair.co/mcp
- Read-only access model reduces accidental mutation risk
- 24 dialect-aware hosted tools
- 3 database engines: PostgreSQL, MySQL, SQL Server
- Server version 2.1.3
What problem does it solve?
Agents cannot safely inspect live relational data when every question means manual SQL in a desktop client or risky write-capable connections.
Who is it for?
Solo builders with an existing SQL database who want MCP-driven schema and query help without granting write access.
Skip if: Greenfield projects with no database yet, teams that need mutations/ETL writes, or shops standardizing on document-only data stores.
What do I get? / Deliverables
After you connect your DSN and add the MCP remote, your assistant can run read-only, engine-aware database operations through ThinAir’s hosted tools.
- Registered read-only MCP connection to your relational database
- Agent-usable dialect-aware SQL and metadata operations (24 tools)
- Faster schema and data questions without custom internal APIs
Recommended MCP Servers
Journey fit
Build is the canonical home for wiring data sources into products and agent tooling, even when you later use the same connection for ops questions. Integrations matches a hosted MCP bridge that connects assistants to existing database DSNs.
How it compares
Hosted read-only SQL MCP bridge—not a local Postgres skill or full ORM codegen workflow.
Common Questions / FAQ
Who is co.thinair/data for?
Indie developers and small teams running PostgreSQL, MySQL, or SQL Server who want agents to query and explore data read-only via MCP.
When should I use co.thinair/data?
Use it while building or operating a data-backed app when you need fast, dialect-correct SQL assistance tied to a real DSN.
How do I add co.thinair/data to my agent?
Paste your database DSN at https://data.thinair.co/connect, copy the Bearer ta_data_ key, set the Authorization header on https://data.thinair.co/mcp, and register the remote in your MCP client.