Mdtero Public Surface

The public local-client and install surface for Mdtero.

This repository is the public home for Mdtero's user-side installables.

This repo is now the intended SSOT for the browser extension and the wider public install surface.

The frontend repo may keep a compatibility mirror under mdtero-frontend/apps/extension, but long-lived extension changes should start here.

The product and backend SSOT still live in separate private repos:

• frontend product repo: JonbinC/mdtero
• backend parsing repo: JonbinC/mdtero-backend

This repo stays focused on what users install or run locally.

Mdtero turns papers into reusable Markdown research packages.

Use this repository when you specifically need public local capture, helper setup, or public install guidance.

This Repo Contains

• the public extension code in extension
• helper-facing public assets in helper
• skill-facing public assets in skills
• public install entry points in install
• shared client contract in shared
• public docs in docs/public
• archived legacy assets in archive

When To Use The Extension

• you are already reading a supported paper page locally
• the paper page needs to stay on your own machine
• you want a quick path to paper.md, figures, and a reusable bundle
• you already have a local PDF or EPUB and want to keep the same package flow
• local PDF intake currently defaults to GROBID; Docling and MinerU remain selectable fallbacks

PDF is optional input. The default handoff format remains the Markdown package.

Repo Boundary

• use this repo for public extension packaging, helper/setup assets, and user-side install guidance
• do not treat this repo as the source of truth for dashboard UX or backend implementation
• if something is meant to be downloaded, installed, or run by end users locally, default it here
• legacy MCP code is archived and is not an actively maintained surface

Install

1. Install Mdtero from the Chrome Web Store or Edge Add-ons.
2. Sign in inside Mdtero settings and keep the default API URL unless you are testing locally.
3. Open the article locally or start from your own PDF/EPUB when needed.
4. Use manual unpacked loading only for development or review builds.

Repo Map

• extension: extension source, tests, build output, and manifest
• helper: helper-facing public assets and MCP/runtime utilities
• archive: deprecated or historical public assets kept only for reference
• skills: public skill-facing install guidance
• install: top-level install entry docs
• shared: public client contract used by local clients
• docs/public: stable public-facing docs

Public Links

• Chrome Web Store: Mdtero on Google Chrome
• Edge Add-ons: Mdtero on Microsoft Edge
• Product guide: mdtero.com/guide
• OpenClaw install guide: ./helper/openclaw/INSTALL.md
• Codex install guide: ./skills/codex/INSTALL.md

Local Development

npm install
npm test
npm run build

Build output lives in extension/dist.

Notes

• the extension and website are public clients; the production backend stays private
• the extension does not need the website UI open to parse papers
• local helper or extension should handle publisher-side local acquisition when required
• permissions stay scoped to local downloads, supported paper tabs, native helper messaging, and the supported publisher/API host list
• for the local helper, download the installer, inspect it locally, then run it
• if repo responsibilities ever conflict, frontend/backend SSOT wins over this public packaging repo