Skip to main content
Glama
hulin42

keynote-harvest-mcp

by hulin42
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to keynote-harvest-mcp

No user-submitted related servers found.

    Related Servers

    • KPA

      alvelda
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides an MCP server for programmatic reading, authoring, editing, designing, and optimization of Apple Keynote presentations.
      MIT

    • keynote-mcp

      tszaks
      F
      license
      A
      quality
      C
      maintenance
      Local macOS MCP server that reads, edits, and exports Apple Keynote presentations via JXA. Enables Claude to visually analyze slides, apply design changes, and iterate on presentations directly.
      19
      1
      -

    • docx_mcp_server_ts

      Mavline
      A
      license
      C
      quality
      C
      maintenance
      Enables programmatic processing of DOCX/OOXML files through MCP, covering text, tables, images, headers/footers, structured data tags, comments, and track changes.
      29
      44 npm
      MIT

    • Keynote-MCP

      betancur
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to control Keynote presentations through AppleScript automation, supporting slide operations, theme-aware content management, and export functions.
      11
      MIT
    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

    A3.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources