F
licenseNot graded
qualityB
maintenanceEnables AI agents to create, convert, split, inspect, and edit PowerPoint and ODP presentations through typed MCP tools, including bundled cloud storage upload/download operations for a complete workflow.
-
ppt-mcp
by ZiChuanLan
Related Servers
Alternatives to ppt-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables creation of professional PowerPoint presentations with AI-generated content and images, supporting multiple LLMs and image services via MCP protocol.MIT
- AlicenseAqualityDmaintenanceExposes the MinerU document-to-markdown API as MCP tools for converting PDF, Word, PPT, and images into Markdown. It supports both local and remote file processing with integrated OCR capabilities for multiple languages.210MIT
- FlicenseBqualityDmaintenanceEnables Claude to read, create, and edit a single pre-bound PowerPoint file via MCP tools, with security bound to one specific .pptx file.10-
FileToPDF MCP serverofficial
AlicenseAqualityFmaintenanceEnables conversion of files, HTML, and Markdown to PDF through natural language, using the FileToPDF API.441 npm2MIT
mcp-ToseaAIofficial
AlicenseBqualityBmaintenanceOfficial MCP server for ToseaAI that enables document-to-presentation workflows including PDF parsing, outline generation, and slide rendering. It provides a stable tool surface for AI agents to create, manage, and export presentations directly within their environment.211MIT
TDQS
B3.4/5.0
Scored across 16 tools
Disambiguation4/5
Most tools have clearly distinct purposes, but ppt_list_route_models and ppt_list_ai_models overlap conceptually, and ppt_check_route vs ppt_create_job may be confused as both initiate workflows. However, descriptions clearly differentiate high-level guided flow from low-level escape hatch, reducing real ambiguity.
Naming Consistency5/5
All tools share a consistent 'ppt_verb_noun' snake_case pattern, with clear action-object pairs. Verbs are consistent (list, get, set, create, download, check) and objects are specific, making the naming predictable and readable.
Tool Count4/5
16 tools is slightly above the ideal 3-15 range, but each tool maps to a distinct step in either the high-level guided workflow or low-level job management. The two parallel flows justify the count, making it reasonable.
Completeness5/5
The tool surface covers the full lifecycle: route selection, workflow state management, job creation, status tracking, cancellation, and result/artifact download. Both high-level and low-level paths are represented, leaving no critical gaps for the PDF-to-PPT conversion domain.
Maintenance
ActivityInactive
ResponsivenessNo issues