Skip to main content
Glama
pdf-chapter-splitter

pdf-chapter-splitter

by keigoly

pdf-chapter-splitter

An MCP (Model Context Protocol) server that splits PDFs by chapters/sections and reads them in Claude-friendly chunks. Designed for use with Claude Code to enable structured reading of large PDF documents.

PDFをチャプター単位で分割し、Claudeが扱いやすいサイズで読み込めるMCPサーバーです。Claude Codeと組み合わせて、大きなPDFの構造化された読み込みを実現します。

How it works / 仕組み

[You / ユーザー] → provide a PDF file path / PDFファイルパスを指定
  ↓
[pdf-chapter-splitter MCP] → analyze structure & extract text / 構造解析&テキスト抽出
  ↓
[Claude Code] ← receives chapter text + metadata / チャプターテキスト+メタデータで返却 → analyzes content / 内容を分析

Related MCP server: Co-Reading MCP

Prerequisites / 前提条件

  • Node.js >= 18

No external binaries required. Uses pdfjs-dist (pure JavaScript).

外部バイナリは不要です。pdfjs-dist(ピュアJavaScript)で動作します。

Installation / インストール

claude mcp add pdf-chapter-splitter -- npx -y pdf-chapter-splitter

This registers the MCP server with Claude Code. No manual configuration needed.

npx (Direct execution / 直接実行)

npx -y pdf-chapter-splitter

Manual installation / 手動インストール

git clone https://github.com/keigoly/pdf-chapter-splitter.git
cd pdf-chapter-splitter
npm install
npm run build

If you installed manually, add the following to your .mcp.json (project-level) or ~/.claude/settings.json (global):

{
  "mcpServers": {
    "pdf-chapter-splitter": {
      "command": "node",
      "args": ["/path/to/pdf-chapter-splitter/dist/index.js"]
    }
  }
}

Tools / ツール

get_pdf_info

Get PDF metadata (title, author, page count, file size).

Parameter

Type

Description

file_path

string (required)

Absolute path to the PDF file

get_toc

Extract table of contents (bookmarks/outline) from a PDF. Returns hierarchical chapter structure with page numbers.

Parameter

Type

Description

file_path

string (required)

Absolute path to the PDF file

list_chapters

List chapters/sections detected from the PDF. Uses TOC if available, otherwise splits by pages.

Parameter

Type

Default

Description

file_path

string (required)

-

Absolute path to the PDF file

level

number (optional)

top-level only

Max TOC depth level to include (0=top level only)

read_chapter

Read the text content of a specific chapter by its index (from list_chapters).

Parameter

Type

Description

file_path

string (required)

Absolute path to the PDF file

chapter_index

number (required)

Chapter index from list_chapters output

level

number (optional)

Max TOC depth level (must match list_chapters)

read_pages

Read text content from a specific page range.

Parameter

Type

Description

file_path

string (required)

Absolute path to the PDF file

start_page

number (required)

Start page number (1-based)

end_page

number (required)

End page number (1-based, inclusive)

detect_headings

Detect heading candidates by analyzing font sizes. Useful for PDFs without TOC/bookmarks.

Parameter

Type

Description

file_path

string (required)

Absolute path to the PDF file

3-level fallback strategy / 3段階フォールバック

  1. TOC/Bookmarks → Use as chapter structure / そのままチャプター構造として利用

  2. Font size analysis → Detect headings from larger text / フォントサイズからヘディング検出

  3. Auto-split → Split every 20 pages / 20ページ単位で自動分割

Constraints / 制約

Item

Limit

Supported format

.pdf

Max response size

200,000 chars / 1,800 lines

Auto-split chunk

20 pages

External deps

None (pdfjs-dist only)

Use cases / ユースケース

  • Structured reading: Read technical books chapter by chapter / 技術書をチャプターごとに読む

  • Document review: Review specific sections of specs or reports / 仕様書やレポートの特定セクションをレビュー

  • Paper analysis: Analyze academic papers section by section / 学術論文をセクション単位で分析

  • Cross-PDF search: Get TOCs from multiple PDFs to find relevant chapters / 複数PDFの目次から関連章を検索

License

MIT

Available Tools

6 tools
detect_headingsA

Detect heading candidates by analyzing font sizes. Useful for PDFs without TOC/bookmarks to understand document structure before reading.

Inputs: file_path (required).

get_pdf_infoA

Get PDF metadata (title, author, page count, file size)

Inputs: file_path (required).

get_tocB

Extract table of contents (bookmarks/outline) from a PDF. Returns hierarchical chapter structure with page numbers.

Inputs: file_path (required).

list_chaptersA

List chapters/sections detected from the PDF. Uses TOC if available, otherwise splits by pages. Returns chapter index, title, page range, and estimated line count.

Inputs: file_path (required), level.

read_chapterA

Read the text content of a specific chapter by its index (from list_chapters). Automatically truncates to stay within Claude Code's context limits.

Inputs: file_path (required), chapter_index (required), level.

read_pagesA

Read text content from a specific page range. Use this for fine-grained control or when chapters are too large.

Inputs: end_page (required), file_path (required), start_page (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools are clearly distinct: metadata, TOC extraction, chapter listing, and raw page reading each have a clear purpose. get_toc, list_chapters, and detect_headings all relate to structure, but their descriptions clarify raw bookmarks vs. detected chapters vs. heading candidates.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: get_pdf_info, get_toc, list_chapters, read_chapter, read_pages, detect_headings. The verbs are varied but predictable based on the action, making the set easy to navigate.

    Tool Count5/5

    Six tools is a well-scoped size for this server. Each tool covers a distinct aspect of PDF chapter analysis without unnecessary redundancy or overwhelming breadth.

    Completeness2/5

    The toolset thoroughly covers analyzing a PDF and reading chapter content, but the server is named 'pdf-chapter-splitter' and provides no actual split, extract, or export operation. An agent could identify chapters and read them, but could not produce split chapter files as the server's name implies.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that reads PDFs and exposes them as structured Markdown, metadata, outlines, images, and tables to LLM consumers via tools like pdf_read_markdown and pdf_info.
      Apache 2.0
    • F
      license
      A
      quality
      B
      maintenance
      A local MCP server for low-token co-reading: import a book, split it into chapter-sized chunks, read it chunk by chunk, and keep notes so a session can resume without re-reading the whole book.
      12
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that extracts text-layer content from PDF files, enabling AI agents to inspect, extract text, outlines, and page content.
      -