Server data from the Official MCP Registry
Create and edit visual agendas for workshops, trainings, meetings, and events.
About
Create and edit visual agendas for workshops, trainings, meetings, and events.
Remote endpoints: streamable-http: https://sessionplan.de/mcp/
Security Report
Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
2 tools verified · Open access · No issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Found in Source Code
Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.
How to Connect
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"de-sessionplan-sessionplan": {
"url": "https://sessionplan.de/mcp/"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
Sessionplan
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
Features
- Visual timeline — Drag & drop blocks to build your agenda
- Multi-day plans — Up to 14 days in one plan, each with its own date, start time and agenda
- Automatic time calculation — Start times and durations update instantly
- Live mode — Follow your plan in real-time during sessions
- Block types & templates — Custom categories, default library, reusable templates
- Grouping & breakouts — Parallel sessions, configurable lanes, per-lane facilitators
- Share & export — Snapshot links, end-to-end encrypted Dynamic Links, JSON export/import, CSV export, print-ready PDF
- Keyboard shortcuts — Help dialog and on-screen hints; character keys can be switched off in the settings
- AI assistants — Generate plans with a copyable prompt or connect ChatGPT and Claude
- Offline-first — Works fully offline after first load (PWA)
- No registration — All data stays in your browser by default
Tech Stack
- Vite · TypeScript · React 18 · Tailwind CSS · shadcn/ui
- react-router-dom · react-i18next · @dnd-kit · Vitest
Getting Started
git clone <repository-url>
cd sessionplan
npm install
npm run dev
Open http://localhost:8080 in your browser.
Self-Hosting
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.
Dynamic-Link sessions API (optional)
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. The key and the write capability stay in
the URL fragment, which browsers do not send to the server. This build has no
server-side analytics or event logging integration.
Self-hosters who want persistent Dynamic Links need a PHP runtime that can
serve the data/ directory:
- Deploy the
data/directory so PHP can executedata/sessions.php(the shared modules underdata/_shared/are loaded by the endpoint). - Set
SP_SESSIONS_DIRon 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. - Optionally set
SP_ALLOWED_ORIGINto a single extra origin (exact match) if the planner is served from a staging or alternative hostname. - Block direct web access to
data/_shared/(e.g. via your Apache/Nginx config) — the shared modules are required bydata/sessions.phpbut 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 canonical base URL the API uses for Dynamic Links. Defaults tohttps://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 ofREMOTE_ADDR. Only enable this when a trusted front-end proxy sits in front of the API.
Server variables can also come from a .env file. The API reads the first file
it finds: one directory above the deployed root, then data/_shared/.env. Real
environment variables always win.
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.
Local development with the API (npm run dev:full)
To work on the planner together with the sessions API locally:
- Run
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. - Point the frontend at the API with
VITE_SESSIONS_API=http://localhost:8081/data/sessions.php(see.env.example; the planner falls back to the same-origindata/sessions.phppath in a same-origin deployment, which the Vite dev server cannot serve). - CORS:
dev:apisetsSP_ENV=development, which additionally allowslocalhost/127.0.0.1origins (any port). For a non-localhost staging check, setSP_ALLOWED_ORIGINinstead. - Storage: sessions default to
sessions_data/next to the checkout, in its parent directory. PointSP_SESSIONS_DIRat 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).
License
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.
Contributing
Bug reports and pull requests are welcome! See CONTRIBUTING.md for details.
Security
See SECURITY.md for reporting vulnerabilities.
Public distribution
This repository contains the frontend application, the optional Dynamic-Link
sessions API and neutral sample content. It has no analytics integration, legal
pages or operator-specific configuration. 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.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Scrapling
Freeby D4Vinci · Developer Tools
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
