keynote-harvest-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KEYNOTE_HARVEST_ROOT | No | The harvest root directory. Defaults to .harvests if not set. | |
| KEYNOTE_HARVEST_LIST_SOURCE | No | Set to '1' to list source PDFs as MCP resources. Source PDFs are unlisted by default. | |
| KEYNOTE_HARVEST_POPPLER_PATH | No | Path to a directory containing Poppler binaries (pdfinfo, pdftoppm, pdftotext, pdfimages) if they are not found in the default search locations. | |
| KEYNOTE_HARVEST_RESOURCE_SCHEME | No | The URI scheme used for MCP resources. Configurable. | |
| KEYNOTE_HARVEST_WORKING_DIRECTORY | No | The working directory for the MCP server. Overrides the caller's current directory for resolving relative input and output paths. | |
| KEYNOTE_HARVEST_COMMAND_TIMEOUT_MS | No | Timeout in milliseconds for long-running harvest commands. Defaults to 600000 (10 minutes). | |
| KEYNOTE_HARVEST_MAX_RESOURCE_BYTES | No | Maximum file size in bytes for resource reads. Defaults to 10485760 (10 MB). |
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": true
} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_keynote_appsC | List installed Keynote-like macOS apps and the recommended explicit app path for native export. |
| export_keynote_to_pdfB | Export a native Keynote .key file to PDF using macOS Keynote automation. |
| harvest_keynote_pdfC | Harvest an exported Keynote PDF into a KeynoteHarvestManifest using the local PDF-first pipeline. |
| get_harvest_manifestB | Read summary metadata from a KeynoteHarvestManifest. Defaults to display-safe source metadata; use redactionMode local-debug or raw for local paths. |
| list_harvest_outputsC | List known harvest output folders and whether they contain a harvest manifest. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool occupies a distinct stage in the Keynote-to-manifest pipeline: app discovery, PDF export, harvesting, manifest reading, and output listing. No two tools share overlapping responsibilities, so an agent can confidently select the right one based on the current workflow step.
All tool names follow a consistent verb_noun pattern with domain-specific context (list_, export_, harvest_, get_, list_). The naming is uniform and predictable, with only minor formatting differences that do not hinder readability.
With exactly 5 tools, the server maps to a focused and complete workflow without unnecessary bloat. Each tool contributes a necessary step or query, making the count well-scoped for the server's purpose.
The tool set covers the full lifecycle from identifying Keynote apps, exporting to PDF, harvesting into a manifest, reading its metadata, and listing output directories. There are no obvious dead ends or missing operations for the stated purpose of Keynote PDF harvesting and manifest access.