Listaro Docs

Local engine development

Start and verify the local Listaro MCP engine without exposing it publicly.

Prerequisites

  • Node.js 22 or newer
  • A local PostgreSQL instance using the repository's isolated development configuration
  • Repository access to DeItGuy23/listaro-ai
  • A trusted machine for browser operations, with the documented local security limits

1. Check out and install

From the repository root:

npm ci

Do not run the nested commercial Next.js application as a substitute for the MCP service. They are separate processes and packages.

2. Configure the isolated database

Review compose.dev.yml and the repository .env requirements. Keep credentials out of Git. The PostgreSQL data volume is persistent; do not wipe it during routine development.

Once the local database is running and the environment is configured:

npm run db:migrate

3. Run the engine

In separate terminal sessions, use the root scripts:

npm run dev:pg
npm run dev:mcp

The engine has historically used loopback REST at http://127.0.0.1:4319 and MCP at http://127.0.0.1:4320/mcp. Confirm the listening ports from the live process and environment. Do not expose either service to the public network.

4. Verify tool registration

npm run verify
npm run smoke:mcp

The smoke command uses a real MCP client and should enumerate nineteen exact tool names. It does not replace per-tool positive/negative, browser-egress, security, fault-recovery, scale and provider certification.

5. Explore the developer console

Open the commercial preview. This is a separately developed Next.js application. Some views are read-only or request previews until authenticated adapters are implemented. Hosted signup and billing are not active.

On this page