Lingsu Slides MCP Server
Related Servers
Alternatives to Lingsu Slides MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible agents to generate, edit, export, and preview AI slide decks through tool calls. Supports deck generation from topics or reference material, per-slide and deck-wide edits, and HTML export.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read and edit live PowerPoint presentations on Windows through a real, visible desktop PowerPoint window, covering slides, text, shapes, notes, tables, and file operations. Supports MCP over stdio and HTTP, plus HTTP/OpenAPI and CLI access, with readback, screenshots, and a Chinese operation log for verifying results.PolyForm Noncommercial 1.0.0

ToolsEnabled Slidesofficial
AlicenseNot gradedqualityBmaintenanceEnables building and editing real PowerPoint decks from any MCP host with a live local browser studio, slide locks, human-only pause/resume/undo/redo controls, and export to PPTX, PDF, or PNG. It preserves imported decks in one editable model while requiring no model calls, accounts, or API keys.MIT- FlicenseNot gradedqualityDmaintenanceFull-featured PowerPoint MCP server with cross-platform support (Windows native, macOS designed). Control PowerPoint programmatically via the Model Context Protocol — 153 tools covering slides, shapes, text, formatting, charts, tables, animations, and more.-
- FlicenseNot gradedqualityAmaintenanceEnables 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.-
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to create, inspect, and edit PowerPoint presentations programmatically using tools for slides, text, shapes, images, tables, and search-and-replace operations.-
TDQS
Scored across 46 tools
Most tools target distinct slide, shape, document, or app operations, and descriptions clarify slide-level versus shape-level actions. However, there are several overlapping pairs: remove_slide versus delete_slides, copy_slide/paste_slide versus copy/paste for shapes, and duplicate_slide versus duplicate for shapes. These boundaries are inferable but create real misselection risk.
Names consistently use a namespace.action snake_case convention such as document.get_slide, app.save_document_as, and clipboard.peek. Minor inconsistencies appear with remove_slide/delete_slides and shape clipboard tools named copy/cut/paste rather than copy_shapes/cut_shapes/paste_shapes, but the overall pattern is predictable.
With 46 tools, the surface is very large for a slide-editing server and includes many granular operations that could be consolidated or handled through properties/scripting. While the breadth supports a full editor, the count is heavy enough to burden tool selection and maintenance.
The server covers document lifecycle, slide CRUD/duplication/reordering, shape CRUD/grouping/alignment/z-order, text and property editing, clipboard operations, export, and undo/redo. Minor gaps remain, such as inserting a slide at an arbitrary index, richer table/cell editing, and slide layout/master operations, but core workflows are complete.