M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
C

Codex Slides

Community
The open-source AI slide studio that lives inside Codex
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #26 of 438
Stars
★ 941 Very popular
Transport
stdio (local process)
Runtime
Node.js 20+
Credentials
No credential needed
License
MIT
Last commit
Tools
38
67FMRS · C

Codex Slides brings the entire slide-production chain into Codex: browser-first, fully visible, and durable on disk. It runs on your existing codex login with zero extra API keys, exposes 38 typed MCP tools plus an equivalent Node CLI, and ships 45 templates, 73 community styles, and 24 guided scenarios; Fast mode parallelizes rendering to land a 10+ slide deck in about 4–5 minutes. The main limitations are that exported PPTX slides are full-slide images rather than editable shapes, and live collaboration has not shipped yet. It suits Codex-heavy users who value visual fidelity and local data ownership.

Strongest · Documentation 17/20 Weakest · Reliability 11/20

Reliability
11/20
Security and permissions
12/20
Maintenance
14/20
Documentation
17/20
Setup experience
13/20
Why each score
Reliability 11/20
Only the README and repository description were readable; the server manifest is not cached, so the claim of 38 typed MCP tools cannot be checked against real behavior. The README asserts verification gates (typecheck, test, check:i18n, check:project-sync, check:skill, check:mcp, electron:check, build) and a release-desktop.yml workflow that boots the packaged server on three platforms and requires HTTP 200 from core routes — file-level evidence of intended reproducibility — yet no actual CI workflow content or committed test files covering the server's key paths are visible in this review. Under the static calibration rule, reliability must not exceed 12. Error and dependency handling is described concretely (90-second heartbeat timeout with retry of only pending/failed pages, resumable interrupted generation, cross-tab polling plus focus/visibility refresh) and dependencies are controllable (Node 20+, existing codex login, no extra API key). Missing visible test evidence and unverifiable tool parity drive the deduction. Scored 11.
Security and permissions 12/20
No red line is triggered: no malware, credential theft, covert exfiltration, or unconfirmed destructive defaults were found, and no install example contains real tokens or secrets. Credential handling is restrained — it reuses the existing codex login session and explicitly states no separate API key is stored and no .env is required; project data defaults to the repo's data/ directory with a warning not to commit personal project data or uploaded source material. However, permissions are only partially scoped: the MCP auto-start targets a loopback service (127.0.0.1:4311), but there is no allowlist or least-privilege statement covering outbound network use for web research and image generation; no explicit confirmation step is documented for side-effecting operations such as export, template/project deletion, or bulk rendering; and third-party community preview assets retain upstream CC BY 4.0 terms that the MIT license does not relicense, creating redistribution compliance risk. Incomplete scoping and confirmation warrant a deduction to 12.
Maintenance 14/20
The repository is not archived, has 881 stars and 7 open issues, ships an explicit MIT license, and includes SECURITY.md, CONTRIBUTING.md, CODE_OF_CONDUCT.md plus a private vulnerability reporting channel — a reasonably complete governance frame. The README shows a horizon-grouped roadmap (shipped / in progress / next / exploring) and a versioned release path (pnpm release, a manually triggered 'Release desktop apps' workflow producing a draft release and SHA256SUMS.txt), giving a clear version and update story. All of this is self-reported README evidence, though: static review cannot verify commit cadence, issue response latency, dependency update practice, or actual release history, so full marks are not justified. Scored 14.
Documentation 17/20
Documentation is the strongest dimension. Install (GitHub marketplace and local checkout), auth (codex login, no extra key), usage (first deck, file-sourced decks, modifying existing decks, mark-based edits, brand system), a grouped CLI/MCP tool table, an environment-variable table, on-disk data layout, local and desktop development commands, lifecycle commands, and troubleshooting (plugin invisible, app fails to start, stale tab, stuck rendering, non-editable PPTX text) plus a verification command list are all itemized. Limitations are disclosed fairly honestly: full-slide-image PPTX export with non-editable shapes is stated up front and listed on the roadmap, unnotarized desktop builds come with the exact bypass steps, and the media kit carries explicit safe-to-claim / do-not-claim guardrails. Deductions: per-tool parameter detail requires the referenced CAPABILITY_MATRIX.md, which is not visible here, and cost/latency is only characterized as roughly 4–5 minutes. Scored 17.
Setup experience 13/20
The install path is short and clear: two commands (codex plugin marketplace add, then codex plugin add), with a local clone plus pnpm dev alternative. Prerequisites are stated (Codex with plugin support, Node 20+, a prior codex login, Git), the port and URL are fixed at 127.0.0.1:4311, and environment variables have usable defaults. The dependency chain is still relatively heavy — Node 20 or newer, corepack/pnpm, and an existing authenticated Codex session — and the whole workflow is tightly bound to the Codex plugin system and the Codex in-app Browser; no configuration examples are given for other mainstream MCP clients (Claude Desktop, Cursor, etc.), and cross-client portability is unaddressed. With no verifiable in-file execution evidence, the static calibration caps setup at 15; whether a connection actually succeeds in a mainstream client cannot be confirmed, yielding 13.

Static review · not runListed 2026-09-10

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesWrites / deletes local filesRuns commands or codeUses the networkControls a browser

Best for

  • Developers and teams already using Codex who want decks made inside their coding agent
  • Workflows that need image-native slides with high visual fidelity
  • Reports and launches that turn research, data, or documents into PPTX/PDF
  • Users who want project data on their own disk with no extra API keys

Not for

  • Users who need individually editable PowerPoint shapes and text boxes (export is currently full-slide images)
  • Users on clients other than Codex, such as Claude Desktop (installation is a Codex plugin)
  • Users needing live collaboration or shareable read-only present links (not shipped)
  • Users needing video or animated slide export (still exploring)

Required permissions

  • Read and write the local project data directory (default <repo>/data, or the OS app-data directory for desktop builds)
  • Access the local HTTP service (default http://127.0.0.1:4311)
  • Network access for deep web research and image generation
  • Reuse existing codex login credentials for text, research, and image generation

Risks and side effects

  • Exported PPTX text is not editable because each slide is a full-slide image
  • Slide quality depends on the underlying models and prompts, so regeneration may be needed
  • Project data, uploaded sources, and generated images stay on disk and can contain sensitive material — do not commit them
  • Community-style previews keep their upstream licenses and attribution; the project's MIT license does not relicense them, so check source terms before redistributing
  • Downloaded desktop builds are not notarized, so macOS and Windows may require manual approval on first launch

Setup

Before you start

Runtime：Node.js 20+

Other optional settings (6)
CODEX_SLIDES_URL optional Browser and local API base URL, defaults to http://127.0.0.1:4311.
CODEX_SLIDES_HOME optional Source checkout used by the portable Skill; auto-detected.
CODEX_SLIDES_APP_DIR optional Source checkout used by the MCP server; defaults to the plugin root.
CODEX_SLIDES_LOG optional Where the auto-start server log is written; defaults to the OS temp directory.
CODEX_SLIDES_NO_AUTO_START optional Set to 1 to disable MCP auto-start.
CODEX_SLIDES_DATA_DIR optional Project/template data root; defaults to <repo>/data.
  1. Ensure you have Codex with plugin support, Node.js 20 or newer, and an account authenticated once with codex login.
  2. Install from the GitHub marketplace:

codex plugin marketplace add nexu-io/codex-slides
codex plugin add codex-slides@codex-slides

  1. Or install from a local checkout:

git clone https://github.com/nexu-io/codex-slides.git
cd codex-slides
codex plugin marketplace add "$PWD"
codex plugin add codex-slides@codex-slides

  1. Restart Codex or the ChatGPT desktop app, then start a new task.
  2. To update a Git-backed installation: codex plugin marketplace upgrade codex-slides, then remove and re-add the plugin, and restart Codex.
  3. For local development run pnpm install then pnpm dev (Web + Desktop) or pnpm dev:web (Web only, default http://127.0.0.1:4311).

Check that it works

After installing via `codex plugin marketplace add nexu-io/codex-slides` and `codex plugin add codex-slides@codex-slides`, restart Codex, run `codex plugin list` to confirm codex-slides is enabled, then send "Open Codex Slides and build me a 6-slide deck about …" — the tool open_codex_slides should appear and the local app at http://127.0.0.1:4311 should open.

Troubleshooting

  1. Codex does not see the plugin: run codex plugin list to confirm codex-slides is enabled, reinstall after version or Skill changes, restart Codex, and start a new task (existing tasks may keep the old Skill snapshot).
  2. The local app does not start: verify node --version is 20+, run pnpm install, pnpm build, pnpm start, and inspect the log at CODEX_SLIDES_LOG or the OS temp directory.
  3. A browser tab shows stale slides: project pages poll the canonical project and refresh on focus; if an older build is open, restart the local server and reload both tabs, and check the API with curl http://127.0.0.1:4311/api/projects/<project-id>.
  4. A project is stuck rendering: Codex Slides only resumes after 90 seconds without a disk heartbeat, so reopen the project — rendered pages are preserved and only pending or failed pages retry.
  5. MCP auto-start issues: set CODEX_SLIDES_NO_AUTO_START=1 to disable auto-start, or point CODEX_SLIDES_URL at an existing service.

Things to try

Once connected, you can ask your AI assistant things like:

  • Open Codex Slides in the Codex Browser and build a 12-slide market report on the 2026 humanoid robotics market — research first, then stop at the outline before rendering.
  • Turn the attached dataset into a 9-slide data story that leads with the headline metric, and confirm the outline first.
  • Open my latest Codex Slides project, rewrite slide 3 for an executive audience, and regenerate only that slide.
  • Save this project as a reusable template, then export the deck to PPTX and PDF.

Tools 38

open_codex_slides read-only
Open the Codex Slides interface in the Codex Browser
start_project writes
Create a new durable project from a topic and page count
get_capabilities read-only
List the available capabilities of the CLI/MCP surface
list_projects read-only
List local projects
get_project read-only
Get details of a specific project
start_project_run writes
Start a durable project run
get_project_run read-only
Check the status of a project run
wait_project_run read-only
Wait for a project run to finish
Show 30 more tools
cancel_project_run writes
Cancel a project run
list_scenarios read-only
List the 24 guided scenarios
upload_material writes
Upload source material into a project
list_design_files read-only
List the project's Design Files
read_design_file read-only
Read a Design File's contents
write_design_file writes
Write or modify a Design File
upload_design_file writes
Upload a Design File
list_templates read-only
List built-in deck templates
list_project_templates read-only
List reusable project templates
save_project_as_template writes
Save the current project as a reusable visual-system template
delete_project_template destructive
Delete a project template
get_onboarding_questions read-only
Get tailored clarification questions for the brief
deep_research writes
Run multi-round web research and produce an editable Markdown brief
create_outline writes
Create a presentation outline from the brief
revise_outline writes
Revise the outline based on feedback
rank_inspiration read-only
Rank community styles against the topic and outline
get_brand_design_system read-only
Read the project's Brand & Design System settings
update_brand_design_system writes
Update brand identity, palette, typography, imagery, and spacing rules
create_deck writes
Create a full deck in one call (unattended fast path)
render_deck writes
Render the deck's slides
edit_deck writes
Edit slides through conversational instructions
restyle_deck writes
Redraw the whole deck in a new visual direction
manage_slide writes
Add, duplicate, move, delete slides, or set transitions
regenerate_slide writes
Regenerate a specific slide
upload_slide_image writes
Upload a slide image
mark_edit_slide writes
Regenerate a slide from on-canvas marks, labels, and comments
export_deck writes
Export to PPTX or PDF with speaker notes preserved
get_speaker_notes read-only
Get speaker notes
update_speaker_notes writes
Update speaker notes
generate_speaker_notes writes
Generate speaker notes automatically

Use cases

Describe a deck in one prompt and get 10+ high-quality slides in about 4–5 minutes
Turn PDFs, spreadsheets, Markdown, or repo files into a presentation
Review and revise the outline and visual direction before anything renders
Draw arrows and comments on a slide in Mark mode and regenerate just that page
Save a project as a reusable template with its brand rules, base style, and reference renders
Drive deck creation headlessly through the typed MCP tools from Codex

Supported clients

Codex

Listed from the project's documentation, not tested by this site.

Overview

Codex Slides is an open-source slide studio built for coding agents, running inside Codex with a browser-first workspace. It drives the whole chain live and steerable — research, outline, style, render, edit, present, and export to PDF/PPTX. Every slide is image-native: composed as a full visual canvas. Fast mode renders every page in parallel, so a 10+ slide deck lands in roughly 4–5 minutes. It ships 45 curated deck templates, 73 community styles, and 24 guided scenarios, runs on your existing codex login with zero extra API keys, and keeps every project on your own disk. The repository exposes two equivalent automation transports: a portable Node CLI at skills/codex-slides/scripts/codex-slides.mjs and a typed MCP server at mcp/server.mjs with 38 tools, including durable run start/status/wait/cancel.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 63.3k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision dbc2a5992e93 Data synced 2026-10-19 Read the FMRS scoring method