Integrations
One engine. Wherever you write code.
Agent memory is the sharp edge — but the same talk-to-it database is a whole backend you didn’t have to build. If you’re shipping a side project, exploring data, or replacing a CRUD service, nlqdb plugs into the place you’re already writing code.
Surfaces
Five universal surfaces, one shared engine. Pick the smallest one that fits the job.
Frameworks
Typed wrappers around the SDK. Install the one for your framework;
render <NlqData> server-side or client-side.
-
@nlqdb/reactReact
React 19 wrapper
Docs → -
@nlqdb/nextNext.js
Next 15 helpers + RSC server factory
Docs → -
@nlqdb/vueVue
Vue 3.5 component
Docs → -
@nlqdb/nuxtNuxt
Nuxt 4 module
Docs → -
@nlqdb/svelteSvelte
Svelte 5 component
Docs → -
@nlqdb/sveltekitSvelteKit
load() + <NlqHead>
Docs → -
@nlqdb/astroAstro
Astro 6 integration
Docs → -
@nlqdb/solidSolidJS
Solid component
Docs →
Other languages
Native SDKs outside the JavaScript ecosystem. Same
/v1/ask on the wire.
MCP hosts
Point any MCP-aware host at mcp.nlqdb.com and your
agent gets nlqdb_remember / nlqdb_recall
plus the ask tool. Tested against:
Install in your agent.
-
Settings → Connectors → Add custom connector — paste the URL.
-
Add to Cursor
Opens Cursor and asks you to confirm before writing the config.
-
Cascade → MCPs → Configure, or ~/.codeium/windsurf/mcp_config.json.
-
Agent Panel → Add Custom Server, or ~/.config/zed/settings.json.
Anonymous — the configs ship with the
pk_live_REPLACE_ME placeholder.
Sign in (free) to inline your live key →
Missing your stack? Every surface above is a thin client over
POST /v1/ask. Wire it up in any language with an
HTTP client — or tell us
which framework to ship next.