propresenter

This MCP server provides full programmatic access to ProPresenter via the ProPresenter API. It exposes 231 REST endpoints grouped into 27 API groups, implemented through modular client classes to allow fine-grained control over presentations, timers, media, looks, playlists, and many other ProPresenter features. Clients can connect through the MCP layer using the configured ProPresenter URL and optional password, issuing commands to query status, trigger actions, or modify presentations in real time. The server acts as a bridge between your automation or assistant tools (such as Claude or custom integrations) and ProPresenter, encapsulating the OpenAPI surface into convenient MCP client modules.

To use it, configure a local MCP server entry (for example in Claude Desktop or VS Code) pointing at the built server binary, and supply the ProPresenter connection details via environment variables PROPRESENTER_URL and PROPRESENTER_PASSWORD. Once connected, you can query status information (version, active slides, screen status), control presentations (go to slides, trigger timelines, manage playlists), manage audio and media (playlists, items, playback controls), and access specialized groups like Stage, Messages, Timers, Themes, Transport, and more. Refer to the API documentation (api/api.md) for the complete list of endpoints and their usage patterns.

Typical workflows include: inspecting ProPresenter state to decide next actions, triggering slides or timelines in response to external cues, updating stage messages or announcements, and orchestrating complex presentation sequences through a combination of the MCP client calls. The server is designed to be integrated into automation pipelines, desktop assistants, or custom UI tools that require robust, programmatic control of ProPresenter.

Prerequisites:

• Node.js 18 or higher installed on your machine
• ProPresenter 7 with API enabled and network access from the host running the MCP server

Installation steps:

1. Clone the repository or download the source code.
2. Install dependencies:

npm install

3. Build the project:

npm run build

4. Run the server (example):

npm run start

5. Verify the server starts and can reach ProPresenter at the URL configured via PROPRESENTER_URL. If you need to customize the environment, create an environment file or export variables before launching the server, for example:

export PROPRESENTER_URL=http://localhost:50000
export PROPRESENTER_PASSWORD=your-password-if-needed
node build/index.js

Notes:

• Ensure ProPresenter API is enabled and accessible from the host running this MCP server.
• If the ProPresenter port or password changes, update PROPRESENTER_URL and PROPRESENTER_PASSWORD accordingly.

Environment variables:

• PROPRESENTER_URL: URL of the ProPresenter API (default http://localhost:50000)
• PROPRESENTER_PASSWORD: Optional API password configured in ProPresenter

Troubleshooting:

• If the server cannot connect, verify ProPresenter is running, API is enabled, and network connectivity between the MCP host and ProPresenter is open (port 50000 by default).
• Rebuild after changes with npm run build.
• Check logs for API endpoint availability and authentication issues.

NPM package: alxpark-propresenter-mcp (if publishing as a package, adjust according to your registry naming).