PlanPro demo (unofficial, AetherStack)

io.github.piksliviksiPublished by GitHub account piksliviksiv0.1.0Updated Oct 27, 2026

Unofficial demo: PlanPro-style work plans, KPIs and risks over synthetic data, with OAuth.

The publisher's own server: demo.st

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Unofficial demo MCP endpoint exposing PlanPro-style work plans, KPIs and risks over synthetic data, with OAuth sign-in.

What you can do
  • Access PlanPro-style work plans, KPIs and risk information through a hosted MCP endpoint.
  • Work with synthetic demo data rather than a real PlanPro workspace.
  • Connect via OAuth, as described in the registry entry.
  • No tool list is published, so the exact operations available are not documented.
When to use it
Worth trying when you want to explore how an assistant could work with plan, KPI and risk data in a PlanPro-like setup without touching real business data. Not intended for production or real planning records.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. The registry declares no environment variables or headers, and the description mentions OAuth, so an OAuth sign-in flow is likely required. Network access to the hosted endpoint.
Before you install
It is an unofficial demo built on synthetic data, so results should not be treated as real plans, KPIs or risks. OAuth grants the server access to your account context; review the consent screen before authorizing. No tool list is published, so what it can read or change is unclear.

Installation

In SourceWeft

  1. Open PlanPro demo (unofficial, AetherStack) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.piksliviksi%2Fplanpro-demo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "planpro-demo-unofficial-aetherstack": {
      "type": "http",
      "url": "https://mcp-plnpro.thekratt.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestOct 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Demo integrations