# Claude Scholar > Semi-automated research assistant for academic research and software development. Supports Claude Code, Codex CLI, Kimi Code CLI, and OpenCode across ideation, coding, experiments, writing, and publication. - **Type:** MCP server - **Install:** `agentstack add mcp-galaxy-dawn-claude-scholar` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [Galaxy-Dawn](https://agentstack.voostack.com/s/galaxy-dawn) - **Installs:** 0 - **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [Galaxy-Dawn](https://github.com/Galaxy-Dawn) - **Source:** https://github.com/Galaxy-Dawn/claude-scholar ## Install ```sh agentstack add mcp-galaxy-dawn-claude-scholar ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About Language: English | 中文 | 日本語 Supported Platforms: Claude Code | Codex CLI | Kimi Code CLI | OpenCode > Semi-automated research assistant for academic research and software development, especially for computer science and AI researchers. Supports [Claude Code](https://github.com/anthropics/claude-code), [Codex CLI](https://github.com/openai/codex), [Kimi Code CLI](https://github.com/MoonshotAI/kimi-code), and [OpenCode](https://github.com/opencode-ai/opencode) across literature review, coding, experiments, reporting, writing, and project knowledge management. Branch note: the main branch is the Claude Code workflow. If you use Codex CLI, please see the codex branch. If you use Kimi Code CLI, please see the kimi branch. If you use OpenCode, please see the opencode branch. ## Recent News - **2026-06-03**: **Kimi Code CLI branch added with strong support from Kimi** — added the `kimi` branch as the Kimi Code CLI edition of Claude Scholar and thank the Kimi team for their strong support of this project. - **2026-05-14**: **`expression-skill` made the communication core, `planning-with-files` restored as the default persistence layer, and the Nature writing stack expanded** — made [`expression-skill`](./skills/expression-skill/README.md) the explicit conclusion-first discipline for reporting, planning, file operations, and multi-step technical work; reintroduced [`planning-with-files`](./skills/planning-with-files/SKILL.md) as the default on-disk planning and progress-tracking workflow for complex tasks; introduced [`nature-writing`](./skills/nature-writing/README.md) for section drafting and argument construction; refreshed [`nature-polishing`](./skills/nature-polishing/README.md) to the latest upstream article-pattern release; and kept [`nature-response`](./skills/nature-response/README.md) plus [`nature-data`](./skills/nature-data/README.md) in the journal-writing stack. - **2026-05-13**: **Evidence-gated research workflow and `Sources/Papers` routing tightened** — added a shared `research-contract.md` for Evidence Records, claim strength, and Claim Promotion Gates; connected research ideation, Zotero ingestion, literature synthesis, results reporting, writing, and rebuttal workflows to that contract; and clarified that project paper notes live under `Sources/Papers` before promoted claims move into `Knowledge` or `Writing`. - **2026-04-24**: **Project-scoped Obsidian KB workflow consolidated** — rebuilt Obsidian project knowledge management into a vault-first workflow, consolidated the older overlapping memory skills into four focused skills, kept repo-local project binding metadata as a runtime layer, and made project navigation human-first instead of a machine registry dump. - **2026-04-22**: **Lean core, pruned default agents, safer install lifecycle, and cleaner paper discovery** — replaced large always-on `CLAUDE.md` / `AGENTS.md` files with compact core instructions, pruned the default agent set to the retained core agents, added safe install-state based uninstall support, generalized `daily-paper-generator` to broader topics with arXiv / bioRxiv support and a fixed Top 10 -> Top 3 -> Top 1 selection flow. - **2026-04-15**: **pubfig and pubtab introduced** — introduced [`pubfig`](https://github.com/Galaxy-Dawn/pubfig), a Python package for publication-grade scientific figures, and [`pubtab`](https://github.com/Galaxy-Dawn/pubtab), a Python package for publication-ready tables and Excel↔LaTeX workflows. Together they provide a cleaner production stack for paper figures, benchmark tables, export control, and final artifact QA. View older changelog - **2026-04-15**: **[`publication-chart-skill`](./skills/publication-chart-skill/SKILL.md) integrated into Claude Scholar** — wrapped [`pubfig`](https://github.com/Galaxy-Dawn/pubfig) + [`pubtab`](https://github.com/Galaxy-Dawn/pubtab) into [`publication-chart-skill`](./skills/publication-chart-skill/SKILL.md), added the skill to the repository, and connected it to Claude Scholar's analysis and writing boundaries so publication-grade figure/table work now has an explicit handoff route instead of being mixed into general analysis or prose skills. - **2026-03-31**: **Zotero smart-import workflow docs aligned** — updated Claude Scholar's research-facing docs around the latest `zotero-mcp` public surface: `zotero_add_items_by_identifier` is now the default paper-import path, `zotero_reconcile_collection_duplicates` is the standard post-import cleanup step, source-aware PDF cascade behavior is documented more accurately, and public vs internal diagnostics are now clearly separated. - **2026-03-31**: **README onboarding refreshed** — clarified that Claude Scholar is especially well-suited to computer science and AI researchers, added practical getting-started scenarios after installation, improved prerequisite and branch guidance, and made the “existing local md files must be manually merged” expectation much more explicit. - **2026-03-31**: **Installer and hook behavior tightened** — the installer now preserves existing local `CLAUDE.md` while installing the repo-managed version as `CLAUDE.scholar.md`, and the default hook summaries were trimmed to reduce noisy temp-file / uncommitted-file output while keeping safer write-guard behavior. - **2026-03-31**: **Japanese documentation added** — added Japanese docs for the main README plus `AGENTS`, `MCP_SETUP`, and `OBSIDIAN_SETUP`, so the OpenCode branch now has a more complete multilingual documentation surface. - **2026-02-25**: **Codex CLI** support — added `codex` branch supporting [OpenAI Codex CLI](https://github.com/openai/codex) with config.toml, 40 skills, 14 agents, and sandbox security - **2026-02-23**: Added `setup.sh` installer — backup-aware incremental updates for existing `~/.opencode`, auto-backup `opencode.jsonc`, additive `agent/mcp/permission/plugin` merge - **2026-02-21**: **OpenCode** support — Claude Scholar now supports [OpenCode](https://github.com/opencode-ai/opencode) as an alternative CLI; switch to the `opencode` branch for OpenCode-compatible configuration - **2026-02-20**: Bilingual docs — maintained English and Chinese entry documents for broader readability - **2026-02-15**: Zotero MCP integration — added `/zotero-review` and `/zotero-notes` commands, updated `research-ideation` skill with Zotero integration guide, enhanced `literature-reviewer` agent with Zotero MCP support for automated paper import, collection management, full-text reading, and citation export - **2026-02-14**: Hooks optimization — restructured `security-guard` to two-tier system (Block + Confirm), `skill-forced-eval` now groups skills into 6 categories with silent scan mode, `session-start` limits display to top 5, `session-summary` adds 30-day log auto-cleanup, `stop-summary` shows separate added/modified/deleted counts; removed deprecated shell scripts (lib/common.sh, lib/platform.sh) - **2026-02-11**: Major update — added 10 new skills (research-ideation, results-analysis, citation-verification, review-response, paper-self-review, post-acceptance, daily-coding, frontend-design, ui-ux-pro-max, web-design-reviewer), 7 new agents, 8 research workflow commands, 2 new rules (security, experiment-reproducibility); restructured the main configuration docs; 89 files changed - **2026-01-26**: Rewrote all Hooks to cross-platform Node.js; completely rewrote README; expanded ML paper writing knowledge base; merged PR #1 (cross-platform support) - **2026-01-25**: Project open-sourced, v1.0.0 released with 25 skills (architecture-design, bug-detective, git-workflow, kaggle-learner, scientific-writing, etc.), 2 agents (paper-miner, kaggle-miner), 30+ commands (including SuperClaude suite), 5 Shell Hooks, and 2 rules (coding-style, agents) ## Quick Navigation | Section | What it helps with | |---|---| | [Why Claude Scholar](#why-claude-scholar) | Understand the project positioning and target use cases. | | [Core Workflow](#core-workflow) | See the end-to-end research pipeline from ideation to publication. | | [Quick Start](#quick-start) | Install Claude Scholar in full, minimal, or selective mode. | | [Getting Started Scenarios](#getting-started-scenarios) | See a few realistic first-use scenarios after installation. | | [Integrations](#integrations) | Learn how Zotero and Obsidian fit into the workflow. | | [Primary Workflows](#primary-workflows) | Browse the main research and development workflows. | | [Supporting Workflows](#supporting-workflows) | See the background systems that strengthen the main workflow. | | [Documentation](#documentation) | Jump to setup docs, configuration, and templates. | | [Citation](#citation) | Cite Claude Scholar in papers, reports, or project docs. | ## Why Claude Scholar Claude Scholar is **not** an end-to-end autonomous research system that tries to replace the researcher. Its core idea is simple: > **human decision-making stays at the center; the assistant accelerates the workflow around it.** That means Claude Scholar is designed to help with the heavy, repetitive, and structure-sensitive parts of research — literature organization, note-taking, experiment analysis, reporting, and writing support — while still keeping the key judgments in human hands: - which problem is worth pursuing, - which papers actually matter, - which hypotheses are worth testing, - which results are convincing, - and what should be written, submitted, or abandoned. In other words, Claude Scholar is a **semi-automated research assistant**, not a “fully automated scientist.” ## Who This Is For Claude Scholar is especially well-suited to: - **computer science researchers** who move between literature review, coding, experiments, and paper writing, - **AI / ML researchers** who need one assistant workflow spanning ideation, implementation, analysis, reporting, and rebuttal, - **research engineers and graduate students** who want stronger workflow structure without giving up human judgment, - and **software-heavy academic projects** that benefit from Zotero, Obsidian, CLI automation, and reproducible project memory. It can still help in other research settings, but its current workflow design is most aligned with computer science, AI, and adjacent computational research. ## Core Workflow Claude Scholar routes research work through a traceable path: `question -> evidence -> experiment -> analysis -> claim -> writing`. Each stage should preserve what is known, what is uncertain, and what decision should happen next. - **Ideation**: turn a vague topic into concrete questions, research gaps, and an initial plan. - **Literature**: search, import, organize, and read papers through Zotero collections. - **Paper notes**: convert papers into structured reading notes and reusable claims. - **Knowledge base**: route durable knowledge into Obsidian across `Sources / Knowledge / Experiments / Results / Results/Reports / Writing / Daily / Maps`. - **Experiments**: track hypotheses, experiment lines, run history, findings, and next actions. - **Analysis**: generate strict statistics, real scientific figures, and analysis artifacts with `results-analysis`. - **Reporting**: produce a complete post-experiment report with `results-report`, then write it back into Obsidian. - **Writing and publication**: carry stable findings into literature reviews, papers, rebuttals, slides, posters, and promotion. ## Quick Start ### Requirements - [Claude Code](https://github.com/anthropics/claude-code) - Git - (Optional) Python + [uv](https://docs.astral.sh/uv/) for Python development - (Optional) [Zotero](https://www.zotero.org/) + [Galaxy-Dawn/zotero-mcp](https://github.com/Galaxy-Dawn/zotero-mcp) for literature workflows - (Optional) [Obsidian](https://obsidian.md/) for project knowledge-base workflows ### Option 1: Full Installation (Recommended) ```bash git clone https://github.com/Galaxy-Dawn/claude-scholar.git /tmp/claude-scholar bash /tmp/claude-scholar/scripts/setup.sh ``` **Windows**: please use Git Bash or WSL to run the installer. The installer is **backup-aware and incremental-update friendly**: - updates repo-managed `skills/commands/agents/rules/hooks/scripts/CLAUDE*.md`, - backs up overwritten files to `~/.claude/.claude-scholar-backups//`, - backs up `settings.json` to `settings.json.bak`, - preserves an existing `~/.claude/CLAUDE.md` and installs the repo-managed version as `~/.claude/CLAUDE.scholar.md`, - preserves an existing `~/.claude/CLAUDE.zh-CN.md` and installs the repo-managed version as `~/.claude/CLAUDE.zh-CN.scholar.md`, - preserves your existing `env`, model/provider settings, API keys, permissions, and current `mcpServers` values, - adds missing hook entries instead of replacing your entire hook set. **Important CLAUDE note**: if you already maintain your own `~/.claude/CLAUDE.md` or `~/.claude/CLAUDE.zh-CN.md`, review `~/.claude/CLAUDE.scholar.md` and `~/.claude/CLAUDE.zh-CN.scholar.md` after installation and manually merge the Claude Scholar sections you want into your own files. Do not assume the sidecar files are applied automatically. To update later: ```bash cd /tmp/claude-scholar git pull --ff-only bash scripts/setup.sh ``` To uninstall later: ```bash cd /tmp/claude-scholar bash scripts/uninstall.sh ``` The installer now writes: - `~/.claude/.claude-scholar-manifest.txt` for the exact files managed by Claude Scholar - `~/.claude/.claude-scholar-install-state` for install ownership metadata used by safe uninstall The uninstaller removes only files and settings entries recorded in that install state. It does not guess ownership from the current repo checkout. ### Option 2: Minimal Installation Install only a small research-focused subset: ```bash git clone https://github.com/Galaxy-Dawn/claude-scholar.git /tmp/claude-scholar mkdir -p ~/.claude/hooks ~/.claude/skills cp /tmp/claude-scholar/hooks/*.js ~/.claude/hooks/ cp -r /tmp/claude-scholar/skills/ml-paper-writing ~/.claude/skills/ cp -r /tmp/claude-scholar/skills/research-ideation ~/.claude/skills/ cp -r /tmp/claude-scholar/skills/results-analysis ~/.claude/skills/ cp -r /tmp/claude-scholar/skills/results-report ~/.claude/skills/ cp -r /tmp/claude-scholar/skills/review-response ~/.claude/skills/ cp -r /tmp/claude-scholar/skills/writing-anti-ai ~/.claude/skills/ cp -r /tmp/claude-scholar/skills/git-workflow ~/.claude/skills/ cp -r /tmp/claude-scholar/skills/bug-detective ~/.claude/skills/ ``` **Post-install**: minimal/manual install does **not** auto-merge `settings.json`; copy only the hooks or MCP entries you want from `settings.json.template`. If you already have your own `~/.claude/CLAUDE.md` or `~/.claude/CLAUDE.zh-CN.md`, also merge the relevant sections from this repo's Claude files into yours instead of blindly overwriting them. ### Option 3: Selective Installation Copy only the parts you need: ```bash git clone https://github.com/Galaxy-Dawn/claude-scholar.git /tmp/claude-scholar cd /tmp/claude-scholar cp hooks/*.js ~/.claude/hooks/ cp -r skills/latex-conference-template-organizer ~/.claude/skills/ cp -r skills/architecture-design ~/.claude/skills/ cp agents/paper-miner.md ~/.claude/agents/ cp rules/coding-style.md ~/.claude/rules/ cp rules/agents.md ~/.claude/rules/ ``` **Post-install**: selective/manual install does **not** auto-merge `settings.json`; copy only the hooks or MCP entries you actually want from `settings.json.template`. If you already have your own `~/.claude/CLAUDE.md` or `~/.claude/CLAUDE.zh-CN.md`, merge the relevant sections from this repo's Claude files into yours instead of blindly overwriting them. ### Option 4: Plugin Marketplace Installation **Step 1: Install the Plugin** ```bash /plugin marketplace add Galaxy-Dawn/claude-scholar /plugin install claude-scholar@claude-scholar ``` This auto-loads all skills, commands, agents, and hooks. During installation, you can choose the scope: user (all projects) or project (single project). **Step 2: Install Rules (Required)** … ## Source & license This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [Galaxy-Dawn](https://github.com/Galaxy-Dawn) - **Source:** [Galaxy-Dawn/claude-scholar](https://github.com/Galaxy-Dawn/claude-scholar) - **License:** MIT Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/mcp-galaxy-dawn-claude-scholar - Seller: https://agentstack.voostack.com/s/galaxy-dawn - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.