Slidespeak

Created By
SlideSpeaka year ago
Overview

what is Slidespeak?

Slidespeak is a tool designed to automate the process of creating and managing presentations using Docker and API integration.

how to use Slidespeak?

To use Slidespeak, you need to set up a Docker container with the provided configuration and obtain an API key from the Slidespeak website.

key features of Slidespeak?

  • Easy integration with Claude Desktop for automated presentation management.
  • Docker support for easy deployment and testing.
  • API key management for secure access.

use cases of Slidespeak?

  1. Automating the creation of presentation slides.
  2. Integrating with other applications for seamless presentation workflows.
  3. Local testing and development of presentation tools.

FAQ from Slidespeak?

  • How do I get an API key for Slidespeak?

You can obtain an API key by visiting the Slidespeak API page at https://slidespeak.co/slidespeak-api/.

  • Can I run Slidespeak without Docker?

Yes, you can run Slidespeak directly by following the provided configuration instructions.

  • How do I make a new release of Slidespeak?

Update the version in the specified files and create a new release on GitHub.

Server Config

{
  "mcpServers": {
    "slidespeak": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "SLIDESPEAK_API_KEY",
        "slidespeak/slidespeak-mcp:latest"
      ],
      "env": {
        "SLIDESPEAK_API_KEY": "YOUR-API-KEY-HERE"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
SlideSpeak
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago