Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenuSettings
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch

Sessionplan

by tim-petersversion 1.2.0i★ –iRuns in the cloud
Registry namede.sessionplan/sessionplan

Install

Overview

Description from the maker (original English)

Create and edit visual agendas for workshops, trainings, meetings, and events.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://sessionplan.de/mcp/

Run this in your terminal

claude mcp add --transport http sessionplan https://sessionplan.de/mcp/

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "sessionplan": {
      "url": "https://sessionplan.de/mcp/"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "sessionplan": {
      "type": "http",
      "url": "https://sessionplan.de/mcp/"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://sessionplan.de/mcp/

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain sessionplan.de (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 32466 servers in this category
  • Published to the registry more recently than 29% of the other 32466 servers in this category
  • Basic checks equal to or better than 100% of the other 32466 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Sessionplan safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.2.0) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

HotCodePush

by hotcodepush-team

Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.

Runs in the cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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:

  1. Deploy the data/ directory so PHP can execute data/sessions.php (the shared modules under data/_shared/ are loaded by the endpoint).
  2. Set 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.
  3. Optionally set SP_ALLOWED_ORIGIN to a single extra origin (exact match) if the planner is served from a staging or alternative hostname.
  4. Block direct web access to 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 canonical base URL the API uses for Dynamic Links. 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.

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:

  1. 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.
  2. 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-origin data/sessions.php path in a same-origin deployment, which the Vite dev server cannot serve).
  3. CORS: 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.
  4. Storage: sessions default to sessions_data/ next to the checkout, in its parent directory. 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).

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.

Ask PopNx