Mr. Decoupler: a private seam between AI and any database. No SQL, only views you approve.
MCPpedia last refreshed this data
io.github.Meador793/the-nothing is an MCP server that mr. Decoupler: a private seam between AI and any database. No SQL, only views you approve. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 89/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"the-nothing": {
"args": [
"-y",
"the-nothing-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Mr. Decoupler: a private seam between AI and any database. No SQL, only views you approve.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked the-nothing-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in data
Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite
Manage Supabase projects — databases, auth, storage, and edge functions
A cross-platform desktop application for managing AI Agents and MCP Servers. 一款用于管理AI智能体与MCP服务器的跨平台桌面应用程序。
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
MCP Security Weekly
Get CVE alerts and security updates for io.github.Meador793/the-nothing and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
a.k.a. Mr. Decoupler: the fastest private way to connect AI to a database.
Sometimes less is more.
Most database MCP servers hand the AI a query tool. The AI writes SQL, rows pour into the context window, and every question costs another round trip, more tokens and more exposure.
The Nothing turns that around. It holds the database connection privately, on your side, and gives the AI one minimal, read-only tool that can't run SQL:
read_view schema: tables, columns and row counts. Structure only, never records.read_view <name>: a view you approved ahead of time, row-capped. Optional.The AI can't write queries, browse tables, or change anything. It understands the shape of your data without dragging the data itself into the conversation. That's the decoupling, and it's why we call it Mr. Decoupler.
With no database around, it does exactly what the name says: nothing.
Open a project and it connects on its own, checking in this order:
THE_NOTHING_DB, if you set itDATABASE_URL in the environmentTHE_NOTHING_DB or DATABASE_URL in the project's .env fileNothing found means nothing connected. Auto-detection only looks inside a project folder, never your home folder or a drive root. Turn it off with THE_NOTHING_AUTODETECT=off.
Your database / dataset ──(private, read-only)──▶ The Nothing ──(read_view: schema + approved views)──▶ AI
Postgres · MySQL · SQL Server │
SQLite · CSV · TSV · JSONL └─ the AI can't write SQL, browse or change data
| Guarantee | How |
|---|---|
| One tool, no SQL | read_view accepts only a name from a fixed list: schema or a view you approved. |
| No records by default | The schema is table names, columns and row counts. Rows appear only in views you wrote. |
| Read-only | Views must be a single SELECT/WITH. Postgres and MySQL run them in a READ ONLY transaction; SQL Server in a transaction that is always rolled back; SQLite files open read-only. |
| Bounded | Every view is row-capped (default 50, max 1000). |
| Credentials stay put | The connection string never appears in tool output, instructions or error messages. |
| Strictest mode | THE_NOTHING_VIEW_TOOL=off removes the tool entirely: zero tools, and data enters the chat only when you attach a resource yourself. |
| Connection | Source |
|---|---|
postgres://user:pass@host:5432/db | PostgreSQL and compatible services (Supabase, Neon, Aurora, CockroachDB…) |
mysql://user:pass@host:3306/db or mariadb://… | MySQL, MariaDB and compatible services (PlanetScale, Aurora MySQL, TiDB…) |
mssql://user:pass@host:1433/db, sqlserver://…, or Server=…;Database=…;User Id=…;Password=… | SQL Server, Azure SQL |
file.db, .sqlite, .sqlite3, sqlite:/path, or file:./dev.db (Prisma style) | SQLite |
data.csv, .tsv, .jsonl | Datasets, loaded into a private in-memory table named after the file |
Use a read-only database account. The Nothing enforces read-only on its side too, but a read-only account means nothing could write even by mistake.
When you want the AI to see actual numbers, approve views in a JSON file and point THE_NOTHING_VIEWS at it (see examples/views.example.json):
{
"views": {
"revenue_by_month": {
"description": "Total revenue per month.",
"sql": "SELECT
... [View full README on GitHub](https://github.com/meador793/the-nothing#readme)