Log inSubmit server
Aldine logo

Aldine

MCP access to an Aldine LaTeX workspace for Claude-driven editing, typesetting, and PDF review.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Aldine

Pick your client, then add it in one click or paste the config.

No confirmed install command yet

We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for Aldine, and we’d rather show nothing than a guess you’d paste into your client.

Open setup steps on GitHub

Overview

Aldine MCP server connects Claude to a self-hosted Aldine LaTeX workspace, where Claude can edit documents, typeset projects, and display the resulting PDF. The optional built-in MCP service is enabled with `ALDINE_MCP=1` and works with claude.ai, Claude Desktop, Cowork, and Claude Code over MCP. Each Claude change becomes a git commit authored as "Claude", with review and revert controls in Aldine. Reach for it when an agent needs to work directly on a versioned LaTeX project rather than only generate text.

Use cases

  • Edit a LaTeX document through Claude
  • Typeset an Aldine project from a chat
  • Review Claude-authored Git commits
  • Inspect a generated PDF after agent changes

Key features

  • Built-in MCP service
  • Claude-driven LaTeX editing
  • Project typesetting
  • PDF display in supported chats
  • Git commits authored as Claude
  • Review and revert workflow

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

5/5 checks healthy over the last 9d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars105Stargazers on the source repository.
Last commit2d agoMost recent push to the default branch.

How Aldine works

What Aldine does

Aldine exposes a LaTeX editing workspace to Claude through an optional built-in MCP server. The surrounding Aldine application is a self-hosted collaborative editor in which every project is a real Git repository. Through MCP, Claude can modify the open document, run a typeset, and present the generated PDF in the conversation.

The integration is intended for agent-assisted work on existing LaTeX projects. It fits workflows where changes should remain visible and reviewable in the editor instead of being applied as untracked filesystem modifications.

How it works

Enable the MCP service on an Aldine instance with ALDINE_MCP=1, then connect that instance to a supported Claude client over MCP. The README names claude.ai, Claude Desktop, Cowork, and Claude Code as connection targets. PDF results appear inline in claude.ai, Claude Desktop, and Cowork; elsewhere, Aldine provides a signed link.

Claude's edits are recorded as Git commits using the author name "Claude". Aldine shows those commits in the editor's history and provides a review-and-revert notification, allowing a collaborator to inspect or undo the agent's work. Typesetting uses Aldine's existing LaTeX compilation workflow, which runs TeX Live and latexmk in a restricted, no-egress container.

Setup and configuration

Run Aldine as a self-hosted installation and enable its MCP functionality by setting:

  • ALDINE_MCP=1

After the service is enabled, connect the Aldine instance from the Claude product being used. The integration is optional; Aldine remains usable as a collaborative LaTeX editor without it. MCP setup, reachability, and security details are part of Aldine's agent API documentation.

Tools and capabilities

The MCP integration supports the core actions demonstrated for Claude:

  • Edit the open LaTeX document.
  • Typeset the project.
  • Show the resulting PDF in the chat or through a signed link.
  • Leave changes as identifiable Git commits for review.
  • Revert agent changes from the Aldine editor.

These capabilities build on Aldine's project model: branches, Git history, collaborative editing, and sandboxed compilation. The server is therefore most useful when the target project already lives in Aldine and the agent needs to make changes that can be checked in the normal project history.

Limitations and notes

The MCP service is an optional feature controlled by an Aldine server setting. Its behavior depends on the Aldine instance being reachable by the selected Claude client. Claude-authored changes are committed automatically, so teams should use the editor's review and revert controls when validating generated work. Aldine is licensed under AGPL-3.0.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Aldine

Aldine is an MCP server that connects Claude to a self-hosted Aldine LaTeX workspace. Its main tools let Claude edit the open document, typeset the project, and show the resulting PDF in chat or through a signed link. Each change is saved as a Git commit authored as Claude for review or revert.

Enable it by setting `ALDINE_MCP=1` on the Aldine server, then connect the instance to a supported Claude client over MCP. Aldine documents setup, reachability, and security for the agent API.

Yes, Aldine names Claude Desktop as a supported MCP connection target. Generated PDFs can appear inline there, and Claude's edits are recorded as Git commits in the Aldine project.

Yes, the MCP integration can typeset the Aldine project and show the resulting PDF. Compilation uses Aldine's TeX Live and latexmk workflow in a restricted, no-egress container.

Yes, Claude's changes become Git commits authored as "Claude", and Aldine provides a review-and-revert control in the editor. This lets collaborators inspect agent changes before keeping them.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAldine AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/aldine?style=directory)](https://allmcps.com/mcp/aldine)
HTML Embed
<a href="https://allmcps.com/mcp/aldine"><img src="https://allmcps.com/api/badge/aldine?style=directory" alt="Aldine on AllMCPs" /></a>