Skip to content

v5.5.0 — local stdio MCP server

Choose a tag to compare

View all tags
@tomseidel tomseidel released this 23 Jul 12:35
· 21 commits to main since this release
v5.5.0
eacc99b

Adds a local stdio MCP server alongside the hosted remote endpoint. A thin REST client over api.slideforge.dev (holds no engine logic): the 7 tool schemas are baked in locally — so tools/list works with no network and no key — and each call forwards to the REST tool-dispatch endpoint (POST /v1/tools/{name}) authenticated with SLIDEFORGE_API_KEY.

  • For clients that boot MCP servers from a container/stdio, and for offline schema discovery.
  • Most agents should keep using the hosted remote server (https://api.slideforge.dev/mcp/, OAuth 2.1 or API key) — no install.
  • Ships pyproject.toml (console entry slideforge-mcp), the package under src/slideforge_mcp/, a prod contract snapshot, and a contract-parity test.
  • Replaces the previous mcp-remote-based Dockerfile with one that builds and runs the local server.

Install: pip install slideforge-mcp · Docker: docker build -t slideforge-mcp .

Assets 2
Loading