Skip to main content
Glama
ZiChuanLan

ppt-mcp

by ZiChuanLan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MINERU_API_TOKENNoAPI token for Mineru (if needed).
PPT_API_BASE_URLNoBase URL of the PDF2PPT API service.http://127.0.0.1:8000
SILICONFLOW_API_KEYNoAPI key for SiliconFlow (if needed).
PPT_API_BEARER_TOKENNoBearer token for the PDF2PPT API if required by the main service.
PPT_API_TIMEOUT_SECONDSNoTimeout in seconds for API requests.120
PPT_MCP_ROUTE_WORKFLOW_STORE_DIRNoDirectory for persisting workflow state.var/route-workflows
PPT_MCP_ROUTE_WORKFLOW_TTL_SECONDSNoTTL in seconds for workflow persistence.3600

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
ppt_health_checkB

Check whether the wrapped local ppt API is reachable.

ppt_list_routesA

List human-friendly routes for the user to choose from.

Do not choose, infer, or recommend a route on the user's behalf. The next step is to ask the user to pick one route, then call ppt_check_route with that route and route_confirmed=true.

ppt_check_routeA

Lock a high-level route workflow after the user explicitly confirms it.

This is step 1 of the high-level guided flow. It only locks the route and returns a route_workflow_id. Then use ppt_set_conversion_target, ppt_list_route_models if needed, ppt_set_route_options, and finally ppt_convert_pdf.

ppt_set_conversion_targetA

Write pdf_path and page range decisions into a locked route workflow.

This is step 2 of the high-level guided flow. Use it to persist conversion target state so weaker models do not have to remember page ranges from chat history. pdf_path must be a real local PDF path explicitly provided by the user. Do not treat the page scope as complete until page_range_confirmed=true is explicitly written for the currently selected pages.

ppt_set_route_optionsA

Write scanned-page, footer, and AI model decisions into the workflow.

This is step 3 of the high-level guided flow. Use ppt_list_route_models first when the user wants to select a non-default AI OCR model. Do not use this tool before pdf_path and page range are confirmed.

ppt_convert_pdfC

Submit the locked high-level workflow after target and options are ready.

ppt_create_jobA

Create a PDF-to-PPT conversion job from a local pdf_path.

The PDF is read from local disk by this MCP server, then uploaded to the running ppt API. This is the low-level escape hatch. For normal use prefer ppt_list_routes -> ppt_check_route -> ppt_set_conversion_target -> ppt_list_route_models (if needed) -> ppt_set_route_options -> ppt_convert_pdf.

Never use this tool unless the user explicitly asks to bypass the guided route workflow and confirms low_level_override_confirmed=true. The pdf_path must be a real existing local PDF path explicitly provided by the user.

ppt_list_jobsB

List recent conversion jobs from the wrapped local ppt API.

ppt_get_job_statusA

Get the current status, stage, progress, and errors for a job.

ppt_cancel_jobB

Cancel a pending or running conversion job.

ppt_get_job_artifactsB

Return debug/process artifact metadata for a job.

ppt_download_resultC

Download the completed PPTX result to a local output path.

ppt_download_artifactC

Download a retained artifact file to a local output path.

ppt_list_route_modelsA

List candidate models for the currently locked high-level route workflow.

Only use this after pdf_path and page range are already confirmed on the same route_workflow_id.

ppt_list_ai_modelsA

Low-level raw model discovery. Prefer ppt_list_route_models in normal OCR flows.

Only repeat the exact returned model IDs to the user. Do not invent provider categories, unofficial aliases, or recommendations.

ppt_check_ai_ocrC

Probe whether a model can work on the current AI OCR chain.

Prompts

Interactive templates invoked by user choice

NameDescription
ppt_conversion_intakeAsk for conversion decisions one by one before calling ppt_convert_pdf.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

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

Resources