Skip to main content
Connect your coding agent to LambdaDB, then use it to explore and search your data. The LambdaDB CLI guides you through account and project setup and configures the agent’s MCP connection and LambdaDB skill.

Before you start

You need Node.js 22.14.0 or later, npm, and a supported coding agent. Account-based setup also needs an accessible OS credential store and a browser for sign-in and CLI approval.

Let your agent help you set up

Open your project in your coding agent and paste this prompt:
init requires an interactive terminal for account setup. Approve sign-in in the browser, then return to the terminal to select your organization and project. New project creation and key issuance require confirmation. Select your agent with Space, then use Enter to continue. Review the displayed file changes, scope, and write-tool setting before applying them. The guided setup defaults to user scope and enables MCP write tools; choose Change options to change either setting. Reload or restart your agent when prompted. The CLI checks authentication and collection-list access during setup; it does not create collections or documents, and a successful check does not establish search readiness. If the agent’s CLI cannot access its OS credential store, it can verify the configured MCP connection targets the same endpoint and project and continue through MCP. See CLI agent setup. The prompt asks your agent to demonstrate a search after setup. If you use an existing collection, choose the intended collection and read ref when asked. Sample data consumes project resources. Writes are asynchronous, so wait for indexing before searching; the agent should identify what it creates and how to clean it up.

Prefer to run setup yourself?

From your project directory, run:
Complete the browser and terminal steps above, then reload your agent and send:
This command runs the CLI without installing a global lambdadb command. Use npx --yes @functional-systems/lambdadb-cli@latest in place of lambdadb for later CLI commands, or see the CLI installation options if you prefer a persistent command. For SSH or a machine without a browser, run npx --yes @functional-systems/lambdadb-cli@latest init --no-browser and open the printed approval URL on another device. Browser approval is still required. For an existing project key or CI, see CLI configuration and non-interactive agent setup.

Next steps