The local MCP server for Topical Authority Engine. Installs into the user's Claude Code / Cursor / Cline / Windsurf via the Model Context Protocol. POSTs run summaries + map state to the hosted API in ../web/.

Status

Not yet scaffolded. Bootstrap pending. When created, this directory contains a TypeScript Node project with the MCP SDK.

Stack (per `memory/project_mcp_packaging.md`)

Node.js + TypeScript (ESM)
@modelcontextprotocol/sdk (official MCP SDK)
Pino logger → stderr (stdout is reserved for MCP JSON-RPC frames)
Vitest for tests
Published as @topicalauthority/mcp on npm, pinned at @1 major
14 tools total: 10 skill tools + 4 glue tools
Ships day-1 with Windows variant (per spec)

Local dev (when scaffolded)

cd apps/mcp
npm install
npm run dev     # tsx watch entry point

Publish

cd apps/mcp
npm run build
npm publish --access public

Scope @topicalauthority is verified available on npm but reservation is pending external user action — create the npm org at https://www.npmjs.com/org/create before first publish.

Why this lives under `apps/`

See ../../DECISIONS.md "Repo structure" and memory/project_repo_structure.md. Plain-folder monorepo, no orchestration tool. The MCP server has zero shared code with apps/web/ (Laravel/PHP can't import from TypeScript/Node), so an orchestration tool would add cost without benefit.