lopebase

lopebase

Set up LopeBase from your project's own folder.
Your coding agent does the steps. It stops for you only when it has to.

Website · For agents · Pricing · @lopebase/adapter

LopeBase is one place to see and run all of your products: traffic, search, signups, revenue, and errors side by side, with a weekly summary and an agent that can help. This CLI connects a project to it in a few minutes.

Quick start

In the folder of any project you run:

npx lopebase

• Scan. After you say yes, it reads your dependency names, config file names, and the variable names in example env files, then shows your stack, the services you already use, and what it did not find (for example analytics or error logging). You see each thing it reads as it reads it.
• Connect this computer. It opens LopeBase in your browser and shows a short code. Sign in, or create a free account if you are new, check the code matches, and press Connect. No address to type: it finds your workspace. For a custom domain or your own server, add --url https://your-address.
• Pick what to connect. Services already in your code are ticked; the ones you do not use yet are offered, never forced.
• Hand over to your agent. It finds the coding agents you have installed (Claude Code, Codex, Gemini CLI, opencode, Cursor Agent), gives the one you choose the LopeBase tools, and starts it with what the scan found. The agent does the setup and asks you when it needs a sign-in, a key, or a decision.

No agent installed? It prints the prompt for you to paste instead.

It animates a little in an interactive terminal. --no-motion or LOPEBASE_NO_MOTION=1 turns that off; CI and pipes never animate.

What it recognizes

Made for web products, and fine with anything else:

• Frameworks: Next.js, Astro, SvelteKit, Remix, React Router, Nuxt, Gatsby, Docusaurus, Eleventy, Hugo, Jekyll, Angular, SolidStart, Qwik, TanStack Start, Vue, React and Vite apps, plain static sites, Django, Flask, FastAPI, Rails, Laravel, WordPress, Express, Fastify, NestJS, Hono, Expo, and Electron.
• Languages: JavaScript and TypeScript, Python, Ruby, PHP, Go, and Rust, from their own manifests.
• Hosting, data, email, billing, and sign-in: Cloudflare, Vercel, Netlify, Fly.io, Render, Railway, Firebase, Amplify, Heroku, GitHub Pages, and Docker; Supabase, Convex, Neon, Postgres, MySQL, MongoDB, D1, Prisma, Drizzle, and more; Resend, Sequenzy, SendGrid, Postmark; Stripe, Polar, Lemon Squeezy, Paddle; Clerk, WorkOS, Better Auth, Auth.js, and others.
• Ready to connect to LopeBase: PostHog, Google Analytics, Sentry, Stripe, Polar, Supabase, Resend, Sequenzy, and GitHub when your code uses them; plus Search Console, Bing, and an uptime check for any website.
• Your site's address, from homepage, wrangler routes, CNAME, a framework config (site, siteUrl, baseURL), or the canonical tag in index.html. Your GitHub repo, from the git remote.

Commands

Command	What it does
npx lopebase	Scan, connect, choose, and hand over to your agent.
npx lopebase login	Connect this computer to your workspace with a short code, creating an account if you need one. --paste to paste an agent token instead.
npx lopebase update	Update this project's LopeBase Adapter: what is new, then your agent does it.
npx lopebase scan	Show what the scan found. --json for scripts.
npx lopebase prompt	Print the setup prompt instead of starting an agent.
npx lopebase mcp	Run the LopeBase tools as a local MCP server (stdio) for any agent.
npx lopebase adapter secret	Print a new signing secret for @lopebase/adapter. Pipe it straight into your secret store.
npx lopebase adapter check <url>	Test a running adapter, local or deployed, before you connect it.

What it reads, and what it keeps

• Reads: package.json files (and requirements.txt, pyproject.toml, Gemfile, composer.json, go.mod, Cargo.toml) at the root, in your workspace folders, and in apps/, packages/, and similar folders; config file names such as wrangler.toml or vercel.json; the site address in a few config files; your git remote's address; and the variable names in .env.example style files.
• Never reads a real .env file, and never sends a value anywhere. Only names leave your machine, and only to your own workspace.
• Keeps one thing: an agent token in ~/.config/lopebase/auth.json, readable only by you. It lasts 30 days, acts as the workspace admin who approved it, is limited to what that admin allowed, and can be revoked any time under Settings, Agent access.
• LOPEBASE_TOKEN and LOPEBASE_URL override the saved values, for CI or another machine.

Use it with any agent

npx lopebase sets this up for you. To add the tools by hand, register this as a stdio MCP server in your agent:

npx -y lopebase mcp

Or point an agent that supports remote MCP straight at your workspace, for example https://yourteam.lopebase.com/api/mcp. It will ask you to sign in.

Requirements

Node 18 or newer. Works on macOS, Linux, and Windows.

Help

Questions or problems: [e-mail]. Privacy: app.lopebase.com/legal/privacy.

LopeBase is made by Jackalope Digital.