de.sessionplan由 sessionplan.de 發布官方發布者v1.2.0更新於 Oct 27, 2026
Create and edit visual agendas for workshops, trainings, meetings, and events.
Sessionplan MCP 伺服器，讓助理為工作坊、培訓、會議與活動建立並解析視覺化議程的分享連結。
Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/de.sessionplan%2Fsessionplan/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"sessionplan": {
"type": "http",
"url": "https://sessionplan.de/mcp/"
}
}
}Sessionplan is a free, browser-based Progressive Web App for visually planning workshops, trainings, meetings, and events using an interactive timeline.
→ Try it live at sessionplan.de
Open http://localhost:5173 (or the port Vite assigns) in your browser.
Sessionplan is a static web app. Install dependencies, build it and serve the generated files from any static web server. Plans remain in the browser and can be shared as URL links or exported as JSON.
The public distribution ships a single PHP API at data/sessions.php plus the
_shared modules it needs. The API is strictly server-blind — every
Dynamic Link is encrypted in the browser before upload; the server stores only
the encrypted envelope, the title, technical metadata and a hash of the write
capability, never the encryption key. There is no recovery-key escrow and no
server-side analytics or event logging integration in this build.
Self-hosters who want persistent Dynamic Links need a PHP runtime that can
serve the data/ directory:
data/ directory so PHP can execute data/sessions.php (the
shared modules under data/_shared/ are loaded by the endpoint).SP_SESSIONS_DIR on the PHP process to a path outside the webroot
(e.g. /var/lib/sessionplan/sessions). The directory must be writable by
the PHP process; the API persists one JSON file per session there.SP_ALLOWED_ORIGIN to a single extra origin (exact match) if
the planner is served from a staging or alternative hostname.data/_shared/ (e.g. via your Apache/Nginx
config) — the shared modules are required by data/sessions.php but are
not meant to be served as standalone URLs.Additional optional environment variables (both default to safe values and can be left unset for direct-internet deployments):
SP_PUBLIC_BASE_URL — overrides the base URL used when reconstructing a
tracked dynamic-link URL for analytics. Defaults to https://sessionplan.de.SP_TRUSTED_CLIENT_IP_HEADER — when set to a safe header name
(e.g. CF-Connecting-IP, X-Real-IP), the rate-limit + per-IP capacity
counters use that header's value instead of REMOTE_ADDR. Only enable
this when a trusted front-end proxy sits in front of the API.A reference Apache configuration is provided in public/.htaccess. Without
the PHP runtime, the planner continues to work locally and shares plans via
URL fragments or JSON export.
npm run dev:full)To work on the planner together with the sessions API locally:
npm run dev:full — starts the Vite dev server (port 8080) and the
PHP built-in server for the API (port 8081) side by side.VITE_SESSIONS_API=http://localhost:8081/data/sessions.php
(see .env.example; the planner falls back to the same-origin data/sessions.php
path in a same-origin deployment, which the Vite dev server cannot serve).dev:api sets SP_ENV=development, which additionally allows
localhost/127.0.0.1 origins (any port). For a non-localhost staging
check, set SP_ALLOWED_ORIGIN instead.sessions_data/ in the repository root
(gitignored). Point SP_SESSIONS_DIR at a directory outside any served
document root for anything beyond local experiments.Run the two servers separately with npm run dev and npm run dev:api if
you prefer individual terminals (PHP ≥ 7.4 required).
Sessionplan is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0).
The AGPL ensures that modifications distributed as a network service must also be open-sourced, protecting the project from commercial forks while allowing free self-hosting.
See LICENSE for the full text.
Bug reports and pull requests are welcome! See CONTRIBUTING.md for details.
See SECURITY.md for reporting vulnerabilities.
This repository contains the frontend application and neutral sample content.
It has no analytics integration, operator-specific contact details, legal pages
or server implementation. Static sample content in public/data/ is independent
of production content.
.public-export.json lists the files generated in this export and carries a
content-derived publicRevision marker plus a generated date. It identifies
the distribution without exposing private commit references or per-file hashes.
A working-tree-preview source is for review only; published exports should
come from a committed release revision.
來源：README.md，提交 78baf6a
Create Sessionplan
Use this when the user wants a new Sessionplan for a workshop, training, meeting, event, or other timed session, or a revised link after decoding an existing Sessionplan. Pass a complete session object matching inputSchema; partial updates and patches are not accepted. The returned structuredContent.link is an opaque snapshot URL and must be presented verbatim.
session必填Open Sessionplan
Use this whenever the user provides a Sessionplan URL, URL hash, or v2 snapshot code and wants it read, summarized, reviewed, validated, or changed. The validated structuredContent.session is the source of truth. For changes, modify the complete decoded session and pass it to create_session_link; the existing snapshot is not modified in place.
link必填已滿足適用檢查項的 100%
該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。
git clone <repository-url>cd sessionplannpm installnpm run dev