Lass KI-Assistenten LaTeX-Quellcode in publikationsreife PDF-Dokumente kompilieren und Dokumentvorlagen verwalten.
Auch bekannt als pressa-dev/mcp, mcp, @pressa/mcp
- Stars
- 0
- Tools
- 11
- Downloads, 30 Tage
- —
- Neueste Version
- 0.11.4
- Letzter Commit
- 28. Okt. 2026
- Lizenz
- MIT
Was ist Pressa MCP?
Pressa ist ein MCP server. Lass KI-Assistenten LaTeX-Quellcode in publikationsreife PDF-Dokumente kompilieren und Dokumentvorlagen verwalten. Er stellt 11 Tools bereit, etwa latex, compiler, list_public_templates.
Zusammenfassung generiert aus dem README des Projekts
Über Pressa MCP server
Pressa bietet eine spezialisierte Schnittstelle für KI-Assistenten, um LaTeX-Quellcode in professionelle PDF-Dokumente zu verwandeln. Entwickler können diesen MCP server in Clients wie Claude Desktop oder Cursor via npx integrieren oder sich über einen remote HTTP transport verbinden, um lokale Node.js-Installationen zu vermeiden. Der Server arbeitet in einem anonymen Modus, der keinen API-Key erfordert und drei erfolgreiche PDF-Kompilierungen pro Tag mit pdflatex unter Berücksichtigung spezifischer Limits für Seitenzahl und Quellgröße erlaubt.
Nutzer können upgraden, indem sie einen PRESSA_API_KEY hinterlegen, um Zugriff auf fortgeschrittene Compiler wie xelatex und lualatex zu erhalten, das monatliche Limit auf 50 Kompilierungen zu erhöhen und eigene Dokumentvorlagen zu verwalten. Das System enthält Tools zum Durchsuchen einer öffentlichen Galerie mit Vorlagen für Rechnungen, Lebensläufe und Berichte. Für fortgeschrittene Anwender unterstützt der Server das Speichern benutzerdefinierter Templates mit Liquid-Placeholder-Engines und detaillierten Agent-Instructions, um eine konsistente Dokumentenerstellung zu gewährleisten.
Was du damit machen kannst
- 1LaTeX-Quellcode kompilierenEin KI-Assistent kann rohe LaTeX-Strings entgegennehmen und sie in downloadbare PDF-Dateien umwandeln.
- 2Professionelle Geschäftsdokumente erstellenEntwickler können die öffentliche Template-Galerie nutzen, um schnell Lebensläufe, Rechnungen oder Zertifikate zu erstellen.
- 3Automatisches Ausfüllen von VorlagenEin Agent kann strukturierte JSON-Daten in ein vordefiniertes Template einfügen, um ein fertiges Dokument zu erzeugen.
- 4Kompilierungsfehler selbstständig korrigierenDer Server liefert strukturierte Fehlerdiagnosen, sodass eine KI fehlende Packages oder Syntaxfehler automatisch beheben kann.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du Pressa MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenPressa MCP in Claude Code installieren
$ claude mcp add --env 'PRESSA_API_KEY=<YOUR_PRESSA_API_KEY>' mcp -- npx -y @pressa/mcpPressa MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@pressa/mcp"
],
"env": {
"PRESSA_API_KEY": "<YOUR_PRESSA_API_KEY>"
}
}
}
}Pressa MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pressa/mcp"
],
"env": {
"PRESSA_API_KEY": "<YOUR_PRESSA_API_KEY>"
}
}
}
}Pressa MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@pressa/mcp"],"env":{"PRESSA_API_KEY":"<YOUR_PRESSA_API_KEY>"}}'Pressa MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@pressa/mcp"
],
"env": {
"PRESSA_API_KEY": "<YOUR_PRESSA_API_KEY>"
}
}
}
}Pressa MCP in Codex installieren
$ codex mcp add mcp --env 'PRESSA_API_KEY=<YOUR_PRESSA_API_KEY>' -- npx -y @pressa/mcpPressa MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@pressa/mcp"] [mcp_servers.mcp.env] PRESSA_API_KEY = "<YOUR_PRESSA_API_KEY>"
Pressa MCP in Gemini CLI installieren
$ gemini mcp add -s user -e 'PRESSA_API_KEY=<YOUR_PRESSA_API_KEY>' mcp npx -- -y @pressa/mcpPressa MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@pressa/mcp"
],
"env": {
"PRESSA_API_KEY": "<YOUR_PRESSA_API_KEY>"
}
}
}
}Pressa MCP tools 11
Erkannt aus dem READMElatexcompilerlist_public_templatesget_public_templaterender_public_templatenamelatex_contentdescriptioninstructionsplaceholder_engineid_or_name
| latex | — | |
| compiler | — | |
| list_public_templates | — | |
| get_public_template | — | |
| render_public_template | — | |
| name | — | |
| latex_content | — | |
| description | — | |
| instructions | — | |
| placeholder_engine | — | |
| id_or_name | — |
Konfiguration
PRESSA_API_KEYSecretOptional. Without it the server exposes compile and the public template gallery, which work keyless within a daily allowance. A free key from pressa.dev raises the limits and registers the saved-template, asset and render tools.
| Name | Beschreibung | Typ |
|---|---|---|
| PRESSA_API_KEY | Optional. Without it the server exposes compile and the public template gallery, which work keyless within a daily allowance. A free key from pressa.dev raises the limits and registers the saved-template, asset and render tools. | Secret |
Automatisierte Checks
Geluften am 13. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbarBestanden
- Open Source Lizenz (OSI)Bestanden
- Commit oder Release im letzten JahrBestanden
- Package-Name ähnelt keinem populären PackageBestanden
- Remote Endpoint nutzt HTTPSBestanden
- Destruktive Tools sind markiertBestanden
- Keine versteckten Anweisungen an das ModellBestanden
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenBestanden
README
Auf GitHub ansehen@pressa/mcp
MCP (Model Context Protocol) server for Pressa - LaTeX in, publication-quality PDF out. This server lets AI assistants compile documents through a standardized interface.
No API key required to start. Add the server, ask for a PDF, get one. A key raises the limits later.
Setup
Add this to your MCP client configuration (e.g. Claude Desktop, Cursor):
{
"mcpServers": {
"pressa": {
"command": "npx",
"args": ["-y", "@pressa/mcp"]
}
}
}
That is the whole configuration. The server starts in anonymous mode and
exposes the compile tool and the public template gallery, which work with no
credentials: 3 successful PDFs per day, and failed attempts do not count
against that, so an assistant can iterate on its LaTeX for free.
To unlock the rest, add a key:
{
"mcpServers": {
"pressa": {
"command": "npx",
"args": ["-y", "@pressa/mcp"],
"env": {
"PRESSA_API_KEY": "pressa_your_key_here"
}
}
}
}
Get a free key at pressa.dev. Takes about 30 seconds, no credit card. It raises the limit to 50 compilations per month and registers the template, asset and render tools.
Hosted server (no install)
The same tools are also served over Streamable HTTP at
https://api.pressa.dev/mcp, so a client that supports remote MCP servers
needs no Node.js and no local process:
claude mcp add --transport http pressa https://api.pressa.dev/mcp
Keyless, it exposes compile and the public template gallery
(list_public_templates, get_public_template, render_public_template). Send
an Authorization: Bearer <key> header to register the template, asset and
render tools as well.
Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
PRESSA_API_KEY |
No | - | Pressa API key (starts with pressa_). Without it the server runs in anonymous mode and exposes only compile and the public template tools. |
PRESSA_API_URL |
No | https://api.pressa.dev |
API base URL |
Anonymous mode
With no PRESSA_API_KEY set, the server starts anyway rather than refusing to
run, and registers only the tools that work without an account: compile,
list_public_templates, get_public_template and render_public_template.
Tools that need an account are not registered at all, because a tool that
cannot succeed is worse than an absent one.
Anonymous limits: pdflatex only, up to 3 pages, 30 KB of source, no image assets, and PDF links that expire after 1 hour.
Error handling
Compilation failures return a structured diagnosis rather than a raw TeX log:
the error class, the offending command, and a concrete suggested fix (often a
missing \usepackage). An assistant is expected to apply the fix and retry on
its own instead of showing the user a compiler log.
Tools
compile
Compile LaTeX source code into a PDF.
Input:
| Parameter | Type | Required | Description |
|---|---|---|---|
latex |
string | Yes | Complete LaTeX source code. Must contain \documentclass, \begin{document}, \input{}, or \include{}. Plain text, markdown, or raw notes are rejected with not_latex_source (422). The AI agent should generate LaTeX itself, not bounce back to the user. |
compiler |
string | No | "pdflatex" (default), "xelatex", or "lualatex" (Pro and Business plans only) |
Each plan has limits on pages per document, LaTeX source size, PDF output size, and compile timeout. If a compile exceeds your plan's page limit, the document does not count against your monthly quota and the MCP response includes the limit and an upgrade URL. Non-LaTeX input is rejected with a structured requirements list and an example_template so the LLM can self-correct without user intervention.
Output (success):
{
"job_id": "ffc2bd62-3b67-45d6-be14-b529c4b9489f",
"pdf_url": "https://api.pressa.dev/api/v1/pdfs/ffc2bd62...?sig=xxx&exp=xxx",
"expires_at": "2026-04-09T20:44:55Z",
"pages": 1,
"compilation_time_ms": 359,
"usage": {
"plan": "free",
"compilations_this_month": 9,
"monthly_limit": 50
}
}
Output (error): Compilation log and error line number.
list_public_templates, get_public_template, render_public_template
Pressa's public document templates (pressa.dev/templates): invoices, purchase orders, packing slips, delivery notes, receipts, reports, certificates, resumes and cover letters. No key needed.
list_public_templates: every template with a summary, a preview image URL and its colours. Designs of one document (document, e.g. five resume designs) take the same data.get_public_template(template: slug): the fields (JSON schema), sample data and filling instructions.render_public_template(template: slug,data: object shaped like the sample, optionalcolor): fills the template and returnspdf_url. A field that is missing or of the wrong type comes back as a list to fix, at no cost.
Each template also has plain instructions for assistants at https://pressa.dev/templates/<slug>/agent.md.
usage
Get current API usage statistics.
Input: None.
Output:
{
"user": {
"email": "user@example.com",
"username": "user",
"plan": "free"
},
"usage": {
"compilations_this_month": 9,
"monthly_limit": 50,
"remaining": 41,
"resets_at": "2026-04-30T23:59:59Z"
},
"api_key": {
"prefix": "pressa_a",
"name": "my-key",
"total_requests": 15,
"last_used_at": "2026-04-08T20:44:55Z"
}
}
save_template
Save or update a LaTeX template by name. Paid plans only. Upserts: a second call with the same name overwrites the first.
| Parameter | Type | Required | Description |
|---|---|---|---|
name |
string | Yes | Template name (max 100 chars). Unique per user. |
latex_content |
string | For a new template | Full LaTeX source for the template body. May be omitted when converting the saved source with placeholder_engine: "liquid". |
description |
string | No | Short human-readable summary (max 500 chars). Shown in list_templates. |
instructions |
string | No | Agent playbook (prose markdown, max 50000 chars). Describes how to fill the template - defaults, workflow rules, edge cases, conditional logic. Optional but recommended for templates with dynamic parts. See note below. |
placeholder_engine |
string | No | "liquid": the source contains Liquid placeholders ({{ amount }}) filled by render; on an existing raw LaTeX template this converts it in place (same id, name and instructions). "none": raw LaTeX whose braces only look like placeholders. Omit to keep the template's current kind. |
description vs instructions: description is the one-line UI summary ("Standard Toptal monthly invoice"). instructions is the longer playbook your AI agent reads alongside the LaTeX when filling the template ("Ask the user only for total amount; date is today; invoice number format YYYYMMDD-N where N is sequential count for the calendar year; for EU clients add VAT line"). They are different fields.
Raw LaTeX vs placeholder templates: a raw LaTeX template is compiled exactly as saved. A placeholder template is filled with JSON data by render, so the layout never changes. A source containing Liquid placeholders sent without placeholder_engine is refused with liquid_placeholders_in_v1_template, because raw LaTeX would print the braces literally in the PDF. If a placeholder save returns liquid_syntax_error, wrap the literal LaTeX that Liquid misreads (usually a comment right after a brace, \foo{%) in {% raw %}...{% endraw %}.
list_templates
List the user's saved templates. Does not include latex_content or instructions to keep the response small.
Input: None.
Each item in the returned array carries id, name, description, updated_at, latex_size_bytes, and has_instructions (boolean). Use the has_instructions flag to decide whether a follow-up get_template call will return a useful playbook.
get_template
Fetch a single template by ID or name. Returns the full latex_content plus instructions (if any) in one round trip - your agent gets the layout and the playbook together.
| Parameter | Type | Required | Description |
|---|---|---|---|
id_or_name |
string | Yes | Numeric ID or URL-safe template name. |
delete_template
Delete a template by ID or name.
| Parameter | Type | Required | Description |
|---|---|---|---|
id_or_name |
string | Yes | Numeric ID or URL-safe template name. |
Development
npm install
npm run build
npm start
License
MIT
Pressa MCP Fragen
Wie füge ich Pressa MCP zu Claude Code hinzu?
Führe claude mcp add --env 'PRESSA_API_KEY=<YOUR_PRESSA_API_KEY>' mcp -- npx -y @pressa/mcp in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich Pressa MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Welche Tools bietet Pressa MCP?
Er stellt 11 Tools bereit, darunter latex, compiler, list_public_templates, get_public_template, render_public_template.
Benötige ich einen API-Key, um Pressa zu nutzen?
Nein, du kannst im anonymen Modus ohne API-Key starten, der bis zu 3 erfolgreiche PDF-Kompilierungen pro Tag ermöglicht.
Was passiert, wenn meine LaTeX-Kompilierung fehlschlägt?
Der Server liefert statt eines rohen TeX-Logs eine strukturierte Diagnose, die die Fehlerklasse, den verursachenden Befehl und einen Lösungsvorschlag enthält.
Kann ich Vorlagen ohne Account nutzen?
Ja, der Server stellt eine öffentliche Template-Galerie mit Rechnungen, Lebensläufen und Berichten bereit, die ohne Zugangsdaten funktionieren.
Was sind die Limits für den anonymen Modus?
Der anonyme Modus ist auf pdflatex beschränkt, mit maximal 3 Seiten, 30 KB Quellcode, ohne Bild-Assets und mit PDF-Links, die nach 1 Stunde ablaufen.