LectureForge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_presentationA | Validate complete Presentation IR without writing files. Call this before render_presentation. Set include_canonical when the model needs LectureForge's normalized form with default theme fields filled in. |
| render_presentationA | Render complete Presentation IR into an editable PPTX and source bundle. Omit project_id for a new project. For a revision, pass the existing project_id and its current version as expected_base_version. Each successful call creates a new immutable version; it never overwrites an earlier deck. |
| list_projectsA | List locally rendered presentation projects, most recently updated first. |
| get_projectB | Get one project's current state, immutable versions, and artifact references. |
| list_versionsC | List all successfully rendered versions of a presentation project. |
| get_presentation_irC | Read the canonical Presentation IR for a project version or the latest version. |
| get_artifactC | Get safe metadata and resource/file URIs for one generated artifact. Artifact choices are powerpoint, source_bundle, presentation_ir, manifest, validation, and python_source. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| author_presentation | Create a reliable workflow for authoring and rendering a new presentation. |
| revise_presentation | Create a safe immutable workflow for revising an existing presentation. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| presentation_schema | The authoritative JSON Schema for complete Presentation IR. |
TDQS
Scored across 7 tools
Each tool targets a distinct object: projects (list_projects, get_project), versions (list_versions), IR content (get_presentation_ir), validation, rendering, and artifacts (get_artifact). Mild overlap exists because get_project returns artifact references and versions, which could be confused with get_artifact and list_versions, but the descriptions differentiate them well.
All tools use consistent snake_case with a predictable verb_noun pattern: list_projects, get_project, list_versions, get_artifact, get_presentation_ir, validate_presentation, render_presentation. No deviations in style or casing.
Seven tools is well-scoped for a presentation rendering pipeline covering project listing/inspection, version listing, IR retrieval, validation, rendering, and artifact access. Each tool earns its place with no redundancy.
The lifecycle is largely covered: create (render_presentation), read (get_project, get_presentation_ir, get_artifact), list, and validate, with immutability handled via versioning. Minor gaps exist (no delete/prune for projects or versions, no export beyond PPTX), but core workflows are complete.