Use the extension when you are reading live paper pages and want one-click capture into a structured research package.
AI research pre-processing workflow
Turn scattered papers into agent-ready research packages
Mdtero turns supported papers, preprints, and retrieval tasks into structured Markdown bundles, extracted figures, translation outputs, and reusable handoff packages for researchers and agents.
Research in
DOIsupported paper pagearXiv linklocal XML helperagent task
Research out
Evidence-preserving Markdown, figure folders, translated outputs, downloadable bundles, and workflow handoffs that your next agent step can actually use.
Entry Points
Start from the browser extension or your agent
Most users begin in one of two ways: capture a paper while reading, or let an agent continue the workflow for you.
Use the agent path when you want one copied instruction to connect Mdtero and continue directly into retrieval, translation, or review writing.
Standardized Output
Clean enough for people, structured enough for agents
Mdtero standardizes paper structure into Markdown bundles that preserve evidence, headings, figures, and download links instead of leaving you with brittle scraping artifacts.
Boundary Design
What stays local and what becomes reusable
Publisher-side acquisition stays on your side when required, while the resulting package, translation, and workflow metadata become reusable across the site and your agents.
Workflow
From discovery to literature work in four steps
Capture the paper you actually want
Start from a DOI, a supported paper page, arXiv, or a local retrieval helper and keep the acquisition path explicit.
Parse into a structured research package
Get Markdown, figures, downloadable artifacts, and machine-usable task results instead of a fragile one-off scrape.
Translate, organize, and preserve evidence
Use translation only when needed, while keeping the package auditable and ready for downstream review or synthesis.
Hand it off to your next agent step
Move straight into summarization, review drafting, weekly discovery loops, or your own research automation.
Use Cases
Three research pain points the current product already solves
Mdtero should feel like an entry point into AI research work, not just a parser. These examples map directly onto the current product surfaces.
Weekly Discovery
Pair Semantic Scholar discovery with a reproducible capture loop
Use Semantic Scholar to surface new papers, then feed the shortlisted links into Mdtero so each candidate becomes a consistent package for screening and note taking.
Every Friday, collect this week's promising papers from Semantic Scholar, send the selected links through Mdtero, and return a shortlist with package links and one-line relevance notes.
Translation
Translate a paper without losing its research structure
Instead of pasting a raw PDF into a chat, start from the Markdown package and produce a cleaner translation that still preserves figures, sections, and references.
Take this Mdtero package, translate the paper into Chinese, keep the section structure, and flag any equations, figures, or ambiguous terminology that need manual review.
Literature Review
Draft a literature review from evidence-preserving packages
Once a set of papers is normalized into the same package format, your agent can compare claims, extract methods, and draft a review without fighting format drift.
Compare these Mdtero packages, group them by method and evidence type, then draft a literature review outline with citations back to each paper package.
Pricing
Three plans for research work, one add-on for extra translation volume
Free
Free
Start with the core workflow.
- 30 parses / mo
- 3 translations / mo
- Source file downloads
Standard
$3.9 / month
A steady monthly plan for regular reading and translation work.
- 120 parses / mo
- 30 translations / mo
- Priority processing
Pro
$7.9 / month
More room for heavier review, comparison, and synthesis work.
- 300 parses / mo
- 100 translations / mo
- Priority processing
Translation Add-on
$2 / pack
Add this when you only need more translation volume.
- 20 translations / pack
- Translation only
- Best for topping up after plan quota
Agent Install
Use Mdtero with the agent you already have
Supported platforms are listed here. When you're ready, open Account and generate the install message there.
Supported platforms
OpenClaw (Recommended)
Open Account, choose a key, and copy a personalized install prompt for OpenClaw.
Claude Code
Open Account, choose a key, and copy a personalized install prompt for Claude Code.
Codex
Open Account, choose a key, and copy a personalized install prompt for Codex.
Gemini CLI
Open Account, choose a key, and copy a personalized install prompt for Gemini CLI.
Create or select a key in Account, then copy the prepared install message and paste it directly into your agent chat.
FAQ
What researchers usually ask before they commit a workflow to it
What is supported right now?
Today Mdtero already supports supported paper-page capture, DOI-led parsing, arXiv-friendly flows, translation, and agent/API handoff on the same product surface.
Do I have to change my whole research workflow to use it?
No. Mdtero is designed as a preprocessing layer that fits into your current reading, note-taking, API, and agent workflows.
Is translation mandatory?
No. Translation is optional. The core product is the structured package that makes the next research step easier.
How does payment work at launch?
Plans cover routine usage first with included monthly quota. Translation add-ons top up extra translation volume, balance remains available for flexible use, and API pay-as-you-go is there for product or automation workflows.