nlqdb — analytical memory for AI agents

Name: nlqdb — analytical memory for AI agents
Author: nlqdb

by nlqdbversion 0.1.1i★ –iRuns in the cloud

Registry namecom.nlqdb/nlqdb

Install

Overview

Description from the maker (original English)

Analytical memory for AI agents: a real Postgres queried in plain English over MCP. One command.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.nlqdb.com/mcp

Run this in your terminal

claude mcp add --transport http nlqdb https://mcp.nlqdb.com/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "nlqdb": {
      "url": "https://mcp.nlqdb.com/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "nlqdb": {
      "type": "http",
      "url": "https://mcp.nlqdb.com/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.nlqdb.com/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain nlqdb.com (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Search & AI memoryi

More stars than 0% of the other 7233 servers in this category
Published to the registry more recently than 24% of the other 7233 servers in this category
Basic checks equal to or better than 100% of the other 7233 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is nlqdb — analytical memory for AI agents safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated 3 days ago

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 44 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

nlqdb — your autonomous DBA.

nlqdb attaches to the Postgres or Cloudflare D1 database you already run, proposes the changes it needs, applies the ones you approve, measures them, and reverts any that regress.

Why it exists: the mission — encapsulate the trial-and-error journey every company walks to a good database infrastructure.

Where it is going (docs/END_GOAL.md): paste a connection string — on nlqdb.com, with the CLI, through the SDK, or from your coding agent over MCP — and the first proposals arrive within minutes, each with its expected effect, cost and inverse. Apply is one click; nlqdb then measures p95 on the same queries and keeps the change or reverts it, never on your app's request path. That loop is being built (Roadmap); what is live today is the hosted product below.

No backend to build. You write HTML; each component asks for what it wants in plain English; nlqdb infers the schema, writes the SQL, runs it, and renders the result. There is no backend for you to build.

Two actions. That's the whole product:

Create a database — one word: a name (or a goal).
Talk to it in plain English.

<script src="https://elements.nlqdb.com/v1.js" type="module"></script>

That's the entire backend for a live order list — no API to write, no schema to define, no JSON to parse. Engine choice (Postgres / Mongo / Redis / DuckDB / pgvector / …), schema inference, indexing, backups, and auto-migration between engines based on your real workload are background concerns you never have to see.

Status — early, open

nlqdb is early and built in the open, but fully public — no gate, no invite code. The marketing site, the /v1/ask pipeline, the / elements, the chat app, the TypeScript SDK, the hosted MCP server, and the nlq CLI are all live in some form (see the surface table below). Natural-language → SQL accuracy is still climbing toward our public bar (BIRD ≥ 0.65, Spider 2.0 ≥ 0.75 on the free model chain), so answers can be wrong — every response carries a confidence signal and the SQL it ran.

Use it

Connecting an agent over MCP? On Claude Code, one marketplace add wires the hosted server *and* both memory skills in a single step:

/plugin marketplace add nlqdb/nlqdb

/plugin install nlqdb-memory@nlqdb

On any other MCP host, connect your agent with one browser-OAuth approval; headless hosts skip the browser with npx -y @nlqdb/mcp and an sk_mcp_* MCP key (MCP setup). @nlqdb/sdk and @nlqdb/mcp are both published and importable from npm.

The 60-second walkthrough — plain HTML, CLI, and ten framework wrappers — lives at docs.nlqdb.com. Start with the HTML tutorial or the CLI tutorial.

You don't generate an API key separately: describe your database at nlqdb.com, and the chat hands you a snippet with the key already inlined.

Examples

examples/ — minimal scaffolds in plain HTML, Next.js, Nuxt, SvelteKit, Astro, plus a CLI-only walkthrough. Each is the smallest valid integration around one element or one CLI session.

What makes it different

Four things every release has to move, none allowed to regress (GLOBAL-025):

Engine quality — natural-language → SQL accuracy (measured continuously on BIRD + Spider 2.0 + an internal eval), plus the multi-engine layer that moves your data to the right engine for your workload.
Onboarding — landing to first answer in under a minute, no card, no config.
UX — see the diff before any write, see the SQL behind every answer, and on low confidence get a one-click clarify — a guided turn, never a dead-end, and never a silent guess.
Performance — sub-400 ms cached, sub-1.5 s cold.

The bet: get this right on free, open models and it only gets better on frontier ones — the scaffolding compounds with whatever model is underneath.

Models & plans

Free forever on the built-in open-model chain — queries, embeds, and the elements, no card required.
Bring your own LLM key (Anthropic / OpenAI / Gemini / Grok / OpenRouter) on any tier, at no markup.
Hosted premium models on paid plans, when you'd rather not manage a key of your own.
Self-host the source — the engine, CLI, MCP server, and SDKs are source-available under FSL-1.1-ALv2: free to self-host for any non-competing use, bring your own LLM key, no per-call fees. The license auto-converts to Apache 2.0 two years after each release.

The hosted-premium model lane went live 2026-08-14. The full model strategy is in GLOBAL-026.

Surfaces at a glance

Surface	Status	Where
HTTP API (`POST /v1/ask`, `POST /v1/run`, `POST /v1/insert`)	✓ shipped	`apps/api/src/ask/**`
+ elements	✓ shipped (v0.1)	`packages/elements/**`
`@nlqdb/sdk` (TypeScript)	✓ shipped (incl. `runSql` + cross-tenant grant + pack-import runner verbs) — installable from npm; `insert()` and `runSql` `params` publish in `0.5.0`	`packages/sdk/**`
Framework wrappers (React / Next / Vue / Nuxt / Svelte / SvelteKit / Astro / Solid + Swift)	~ built + CI-tested; npm / SPM publish pending	`packages/{react,next,…}/**`
Chat app `nlqdb.com/app`	✓ shipped	`apps/web/**`
Hosted MCP server `mcp.nlqdb.com/mcp`	✓ shipped (host auto-detect pending)	`apps/mcp/`, `packages/mcp/`
Local stdio MCP server `@nlqdb/mcp`	✓ shipped — `npx -y @nlqdb/mcp` with an `sk_mcp_*` key	`packages/mcp/**`
Droppable agent artifacts (AGENTS.md · Claude Code skill + plugin · Cursor rules · Codex config)	✓ shipped — `/plugin marketplace add nlqdb/nlqdb` installs the server + skills in one step	`apps/web/public/agent-artifacts/**`
`nlq` CLI (Go)	✓ shipped (core verbs; device-login pending)	`cli/**`

Full integration matrix in docs/progress.md.

Packages on npm

Published to the public npm registry with build provenance (SK-CIPERM-003). Version badges are live from npm; the table itself is generated from the workspace by scripts/sync-readme-packages.mjs, so it lists exactly the packages that are un-gated ("private" removed) and nothing that isn't.

Package	What it is	Source
`@nlqdb/cli`	Shim that installs the nlq CLI binary for the host platform.	`packages/cli-shim`
`@nlqdb/mcp`	Analytical-memory MCP server for nlqdb — a real database your AI agent can GROUP BY / JOIN / aggregate over in natural language, not just recall.	`packages/mcp`
`@nlqdb/sdk`	Typed HTTP client for the nlqdb /v1 API — works in browsers, Node, Bun, Workers.	`packages/sdk`

Roadmap

The section below is the live focus; the numbered phases after it are the hosted product's roadmap, kept until the GLOBAL-043 deletion series. Canonical plan + exit gates: docs/phase-plan.md. Legend: ✓ shipped · ~ in progress · ◯ planned.

This roadmap is yours to shape. Want something added, reprioritised, or

dropped? Open a PR editing this section (and

docs/phase-plan.md if it's engine-facing), or open

an issue to float it first. Say why now — which of the four north-star

pillars (engine quality, onboarding, UX, performance) it moves. New to the

codebase? Point your coding agent at this repo and paste:

`

Read README.md and docs/phase-plan.md, then propose a roadmap change:

add/change " " under the right section in one line, with a

"why now" naming which north-star pillar it moves. Open a PR with just

that edit — no code.

`

Setup, branch naming, and the CLA are in CONTRIBUTING.md.

Now — attach to the database you already run (`GLOBAL-043`)

One loop — observe → propose → apply → verify → revert — on your Postgres (Supabase, Neon, RDS) or Cloudflare D1. Plan, KPIs and exit gate: GLOBAL-043.

~ /app/dba change ledger — every change with its inverse, newest first; Apply / Reject on each proposal
~ Attach product on synthetic databases — observer, create_index proposal, apply → verify → auto-revert, the four doors (the web door, paste a Postgres string at /app/connect then Apply / Reject in /app/dba, the API door, POST /v1/attach / client.attach() with client.applyProposal() / rejectProposal(), the CLI door, nlq attach / nlq proposals / nlq apply / nlq reject, and the MCP door, nlqdb_connect_database / nlqdb_list_proposals / nlqdb_apply_proposal / nlqdb_reject_proposal; the web, API, CLI and stdio MCP (@nlqdb/mcp 0.4.0) doors are live; hosted mcp.nlqdb.com serves the MCP tools once its held deploy runs; verify runs on its own once an applied proposal's 72 h window has passed; on D1 the API door attaches, applies and rejects so far), tested in CI
~ Postgres spike — one index proposed, applied and measured (before/after p95) on a real-traffic database (the spike DB attaches read-only in CI, first proposal in 2.7 s; no index applied yet)
◯ D1 attach on the real rateme12 — the dogfood
◯ The playbook — unused-index drops, bloat, retypes, partitioning, retention, placement

Phase 0 — Foundations ✓

Worker skeleton · KV + D1 + R2 bindings · Neon adapter + OTel · LLM router (free chain) · Better Auth (GitHub + Google + magic link) · /v1/ask end-to-end · events queue + drain · Stripe webhook · CI/CD + PR preview environments.

Phase 1 — On-ramp

A stranger lands on nlqdb.com, creates a DB in plain English, embeds it, and shares the link — in under 60 seconds, no card, no config.

✓ Marketing site (Astro, live at nlqdb.com)
✓ + elements (v0.1)
✓ Sign-in — magic link + GitHub + Google
✓ Chat surface — streaming three-part response (answer / data / trace), anonymous mode
✓ Anonymous mode — 72h token, adopted onto your account on sign-in
✓ Hosted db.create pipeline (table-card embeddings stubbed pending the pgvector slice)
✓ API keys dashboard (/app/keys)
◯ Hello-world tutorial polish

Phase 1.5 — Trust + telemetry

✓ Diff preview on writes + visible SQL trace on every response
✓ Demand-signal telemetry on every "not yet" path
◯ Confidence floor (clarify-on-low-confidence — a guided turn, not a dead-end) — lands with quality-eval

Phase 2 — Distribution (agent + developer surfaces)

✓ Hosted MCP server (mcp.nlqdb.com/mcp) — host auto-detect pending; local stdio @nlqdb/mcp is on npm, so npx -y @nlqdb/mcp with an sk_mcp_* key is a headless route in with no browser consent step (/agents now carries it; the per-host instal

Only the beginning is shown; read the rest in the repo

nlqdb — analytical memory for AI agents

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

nlqdb — your autonomous DBA.

Status — early, open

Use it

Examples

What makes it different

Models & plans

Surfaces at a glance

Packages on npm

Roadmap

Now — attach to the database you already run (GLOBAL-043)

Phase 0 — Foundations ✓

Phase 1 — On-ramp

Phase 1.5 — Trust + telemetry

Phase 2 — Distribution (agent + developer surfaces)

Now — attach to the database you already run (`GLOBAL-043`)