Website-to-Agent MCP Bridge

Author: divyuuu

Turn an existing website into a small set of reliable, permission-aware tools that AI agents can call through the Model Context Protocol (MCP), without rebuilding the website.

Status

Phase 0 — Foundation. See phases/00-overview.md for phase memory.

Related MCP server: AgentBridge MCP Server

Quick start

pnpm install
cp .env.example .env
pnpm db:migrate
pnpm dev

Other commands:

pnpm test
pnpm lint
pnpm typecheck

Database

SQLite file at DATABASE_PATH (default ./data/app.db). Never committed. Schema lives in packages/database/migrations/.

Structure

• apps/api — Admin REST API, health/readiness, workflows, executions

• apps/mcp-server — MCP Streamable HTTP endpoint (POST /mcp), per-tenant tools

• packages/config — typed env parsing

• packages/contracts — shared Zod schemas

• packages/database — SQLite migrations + tenant-scoped queries

• packages/inspection — Playwright localhost inspection + pnpm inspect

• packages/workflow-engine — schema, approval, Playwright runner

• packages/tool-registry — approved workflows mapped to MCP tools

• packages/test-fixtures/site — local demo site (pnpm fixture:dev, port 4100)

• phases/ — phase-wise build memory, source of truth for progress

• infra/ — local container config

MCP quick check

pnpm fixture:dev
pnpm mcp:dev

Point an MCP client at http://localhost:3001/mcp with header x-mcp-key: <key>. Create keys via the admin API: POST /mcp-keys { name, role } with owner rights. Roles: owner (keys + approve), operator (workflows + executions), viewer (read only). x-tenant-id header still works locally as an owner bootstrap unless ALLOW_HEADER_AUTH=false.

License

MIT — (c) divyuuu. See LICENSE.