Skip to main content

MCP Server

9 requirements · 23 scenarios

Stable Paragraph Identifiers

JR-mcp-server-001
The document editing server SHALL use persisted intrinsic paragraph identifiers as canonical anchor identity. Sequential indexes SHALL NOT be used as anchor identity.
4 test scenarios
  • Re-opening unchanged document yields same identifiers JR-mcp-server-001.1
  • Inserting new paragraph does not renumber unrelated identifiers JR-mcp-server-001.2
  • Identical paragraphs remain uniquely addressable JR-mcp-server-001.3
  • Missing identifiers backfilled on first open JR-mcp-server-001.4

Session-Based Re-Download

JR-mcp-server-003
The document editing server SHALL allow users to re-download previously generated artifacts by session without replaying edit operations.
2 test scenarios
  • Repeat download reuses cached artifacts JR-mcp-server-003.1
  • New edit invalidates previous artifact cache JR-mcp-server-003.2

Editing Formatting Fidelity

JR-mcp-server-011
The document editing server SHALL match the formatting fidelity of the reference editing pipeline for core operations, not merely structural validity.
3 test scenarios
  • Document read returns structured schema with structure columns JR-mcp-server-011.1
  • Edit preserves mixed-run formatting JR-mcp-server-011.2
  • Insert preserves header and definition semantics JR-mcp-server-011.3

Semantic Tag Rendering

JR-mcp-server-014
The server SHALL support semantic tags in inserted or replacement text and render them into concrete document formatting using role models discovered in the document.
1 test scenario
  • Defined term bolding applied via role model JR-mcp-server-014.1

Automatic Definition Styling

JR-mcp-server-015
The server SHALL automatically detect explicit definition patterns in inserted or replacement text and apply definition styling without requiring the caller to include semantic tags.
2 test scenarios
  • Auto-tagged definition receives role model styling JR-mcp-server-015.1
  • Header semantics accepted via tags for backward compatibility JR-mcp-server-015.2

Automatic Document Normalization

JR-mcp-server-019
The document editing server SHALL automatically normalize documents on open by consolidating fragmented formatting and simplifying tracked changes, improving text matching accuracy.
4 test scenarios
  • Document normalized on open by default JR-mcp-server-019.1
  • Normalization bypass available when requested JR-mcp-server-019.2
  • Normalization statistics included in session metadata JR-mcp-server-019.3
  • Paragraph identifiers stable across normalization JR-mcp-server-019.4

Formatting-Preserving Replacement

JR-mcp-server-024
The document editing server SHALL support formatting-preserving text replacement, with an option to consolidate fragmented formatting before searching.
2 test scenarios
  • Replacement preserves surrounding formatting JR-mcp-server-024.1
  • Fragmented formatting consolidated before search when requested JR-mcp-server-024.2

Document Validation and Auto-Repair

JR-mcp-server-027
The document editing server SHALL validate documents upon loading and auto-repair known safe issues during initialization.
3 test scenarios
  • Packed and unpacked document inputs validated JR-mcp-server-027.1
  • Redline validation runs when baseline provided JR-mcp-server-027.2
  • Known safe issues auto-repaired on load JR-mcp-server-027.3

Self-Contained Runtime Distribution

JR-mcp-server-030
The document editing server runtime SHALL be self-contained and SHALL NOT require external language runtimes or commercial library dependencies.
2 test scenarios
  • Runtime remains self-contained JR-mcp-server-030.1
  • Build-time tooling may be external but optional JR-mcp-server-030.2
All Specs