console

AEO Toolkit Console

The unified SaaS surface — every tool, MCP endpoint, and the blogging cron in one Next.js app, deployed as a single Vercel project on one domain.

What's inside

Path	What
/	Dashboard / tool launcher
/tools/audit · /tools/eeat · /tools/llms-txt · /tools/chat · /tools/graph	the 5 web tools
/api/audit/*, /api/generate, /api/chat, /api/auth/google/*, /api/graph/*	tool APIs (Node runtime)
/api/mcp/{ai-visibility,ga-gsc,backlink}/mcp	remote MCP servers (via mcp-handler); the trailing /mcp is the transport path and is required
/.well-known/*	MCP OAuth discovery for Claude.ai connectors
/api/cron/blogging	the autonomous blogging agent, run by a Vercel Cron (see vercel.ts)

All logic lives in the shared @advance-labs/* packages; this app is the thin composition layer.

Run

pnpm --filter @advance-labs/console dev

Deploy (single Vercel project)

• Import the repo → Root Directory = apps/console, framework Next.js, install at repo root with pnpm.
• Set the env vars from .env.example (one set for the whole suite).
• Crons are declared in vercel.json. Add the backing services (Supabase, Upstash, Google OAuth) per ../../docs/DEPLOYMENT.md.

The Chrome extension (apps/chrome-extension) is built separately and offered as a download — it runs in the browser, not on Vercel.

Status

✅ Live at https://aeo.advancelabs.dev (Vercel team Advance Labs, root directory apps/console). Supabase is provisioned via the Vercel Marketplace and the schema is applied. The audit / E-E-A-T / llms.txt / graph tools and the ai-visibility + backlink MCP servers work now; /tools/chat, the ga-gsc MCP, and the blogging cron come online once Google OAuth + LLM keys are added. See ../../docs/DEPLOYMENT.md for the current state and the full runbook.