Skip to main content
Glama
kakalition

apollo-pdf-creator

by kakalition
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_pdfA

Render a document spec to a PDF and return metadata plus the inline file.

Args: spec: The document spec (schema v1); see the pdfcreator://schema resource. out: Output PDF path. Defaults to <output_dir>/<slug>.pdf. home: Data root. Defaults to $PDF_CREATOR_HOME or ~/.local/share/pdf-creator. theme: Override the spec theme (e.g. default, report, invoice). base_dir: Base for relative image/font paths. Defaults to the server cwd. allow_remote: Allow fetching remote images referenced by the spec. force: Overwrite an existing output file.

validate_specA

Validate a document spec without rendering it.

With strict, also resolve the spec through the engine and report the flowable count and engine warnings. Strict resolution needs reportlab.

from_markdownA

Convert Markdown text to a PDF and return metadata plus the inline file.

Args: markdown: Markdown source (headings, paragraphs, lists, tables, code, blockquotes, rules). title: Document title; also names the default output file. author: Document author. Defaults to the configured author setting. theme: Theme name for the document. toc: Insert a table of contents. number_headings: Number section headings. header: Running header text. footer: Running footer text (supports {page} and {pages}). out: Output PDF path. Defaults to <output_dir>/<title-slug>.pdf. home: Data root. Defaults to $PDF_CREATOR_HOME or ~/.local/share/pdf-creator. base_dir: Base for relative image/font paths. Defaults to the server cwd. allow_remote: Allow fetching remote images referenced by the spec. force: Overwrite an existing output file.

Prompts

Interactive templates invoked by user choice

NameDescription
make-pdfCompose and render a document spec with apollo-pdf-creator.

Resources

Contextual data attached and managed by the client

NameDescription
theme_listEvery built-in theme with its label and font family.
demo_listThe names of the bundled example specs.
schemaA concise reference for every document spec key and block type.
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 3 tools

Disambiguation5/5

Each tool serves a distinct purpose: validate_spec checks spec correctness, create_pdf renders a spec to PDF, and from_markdown converts Markdown to PDF. There is no overlap in functionality, making tool selection unambiguous.

Naming Consistency4/5

Two tools follow a clear verb_noun pattern (validate_spec, create_pdf), but from_markdown deviates by using a prepositional prefix. The inconsistency is minor and does not hinder readability.

Tool Count5/5

With only 3 tools, the server is tightly scoped to its core purpose of PDF creation. Each tool fills a necessary role, and the count falls within the ideal range for a focused server.

Completeness4/5

The server covers validation, spec-based PDF generation, and Markdown conversion, which are the essential workflows for a PDF creator. A minor gap is the lack of a tool for inspecting or managing generated PDFs, but this does not break core functionality.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources