Skip to content
Back to search

pascal

MarketplaceWorks with Claude CodeGitHub

Public Pascal workflows for MCP-capable agents.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026. Its scripts were only partly scanned.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/pascalorg/editor with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/pascalorg/editor'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/pascalorg-editor/badge.svg)](/listings/pascalorg-editor)

HTML

<a href="/listings/pascalorg-editor"><img src="/api/listings/pascalorg-editor/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Development

Run the development server from the **root directory** to enable hot reload for all packages:

# Install dependencies
bun install

# Run development server (builds packages + starts editor with watch mode)
bun dev

# This will:
# 1. Build @pascal-app/core and @pascal-app/viewer
# 2. Start watching both packages for changes
# 3. Start the Next.js editor dev server
# Open http://localhost:3002

**Important:** Always run `bun dev` from the root directory to ensure the package watchers are running. This enables hot reload when you edit files in `packages/core/src/` or `packages/viewer/src/`.

Building for Production

# Build all packages
turbo build

# Build specific package
turbo build --filter=@pascal-app/core

Publishing Packages

Releases run from `.github/workflows/release.yml` (`workflow_dispatch`, with `bump` and `dry-run` inputs). Every package shares one version: the workflow bumps all eight, rewrites the internal `@pascal-app/*` ranges, checks that each one already exists on npm (a package never published fails the run before anything is built), builds, publishes in dependency order (`core` → `geometry-script` → `viewer` → `editor` → `nodes` → `mcp` → `ifc-converter` → `cli`), then commits the release and pushes one tag per package with the release deploy key, which the `main` ruleset lets through. A dry run validates the builds without touching the registry. [Releasing to npm](wiki/npm-release.md) covers authentication, adding a package, the deploy key, recovering a partial run, publishing by hand and the follow-ups.

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 24 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "$schema": "https://json.schemastore.org/claude-code-marketplace.json",
  3. "name": "pascal",
  4. "version": "0.1.11",
  5. "description": "Public Pascal workflows for MCP-capable agents.",
  6. "owner": {
  7. "name": "Pascal"
  8. },
  9. "plugins": [
  10. {
  11. "name": "pascal-agent-skills",
  12. "source": "./skills",
  13. "description": "Create, inspect, validate, and assess furniture layouts with bounded next actions in Pascal through MCP.",
  14. "author": {
  15. "name": "Pascal",
  16. "email": "support@pascal.app",
  17. "url": "https://pascal.app"
  18. },
  19. "version": "0.1.11",
  20. "category": "productivity",
  21. "skills": ["./pascal-3d", "./furniture-fit", "./architect"]
  22. }
  23. ]
  24. }
README.md · README · 336 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # Pascal Editor — open-source 3D architecture software for AECO
  2. Create and edit 3D building models in your browser, run Pascal locally with its CLI, or connect
  3. AI agents through the Model Context Protocol (MCP).
  4. Pascal Editor is a local-first, MIT-licensed building editor for architecture, engineering,
  5. construction, and operations (AECO) work. Model sites, buildings, levels, walls, slabs, roofs,
  6. openings, rooms, and furniture; bring 3D scans in as reference layers for scan-to-BIM workflows
  7. and model editable building elements over them; and let an agent read, edit, validate, and save
  8. the same scenes. Built with React Three Fiber and WebGPU.
  9. [![MIT License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
  10. [![npm @pascal-app/core](https://img.shields.io/npm/v/@pascal-app/core?label=%40pascal-app%2Fcore)](https://www.npmjs.com/package/@pascal-app/core)
  11. [![npm @pascal-app/viewer](https://img.shields.io/npm/v/@pascal-app/viewer?label=%40pascal-app%2Fviewer)](https://www.npmjs.com/package/@pascal-app/viewer)
  12. [![npm @pascal-app/cli](https://img.shields.io/npm/v/@pascal-app/cli?label=%40pascal-app%2Fcli)](https://www.npmjs.com/package/@pascal-app/cli)
  13. [![Discord](https://img.shields.io/badge/Discord-Join%20Server-5865F2?logo=discord&logoColor=white)](https://discord.gg/XRKsDcpqgS)
  14. [![X (Twitter)](https://img.shields.io/badge/follow-%40pascal-black?logo=x&logoColor=white)](https://x.com/pascal)
  15. https://github.com/user-attachments/assets/063c0891-9ae5-4173-bd08-a101d9c3352b
  16. ## Start here
  17. - **Run the editor locally** — `npx @pascal-app/cli editor`. See [Run the editor locally](#run-the-editor-locally).
  18. - **Self-host it** — one container with SQLite storage. See [Self-host it](#self-host-it).
  19. - **Embed the packages** — use the viewer or full editor in your React app. See [Use the published packages](#use-the-published-packages).
  20. - **Connect an AI agent** — Claude Code, Cursor, Codex, or any MCP client. See [Connect an AI agent (MCP)](#connect-an-ai-agent-mcp).
  21. ## Connect an AI agent (MCP)
  22. MCP is an open protocol that lets AI assistants call tools in other applications; Pascal's MCP
  23. server gives an agent tools to inspect, edit, validate, and save building scenes.
  24. Choose where the projects live:
  25. - **Local (no account)** — the Pascal CLI runs an MCP service on your machine. Agents connect
  26. with `pascal mcp connect`, projects stay in `~/.pascal/data/pascal.db`, and nothing is uploaded.
  27. No Pascal account or API key is needed.
  28. - **Hosted workspace** — `https://editor.pascal.app/api/mcp` works in your Pascal account or
  29. organization and needs that account's authorization. How a client authenticates depends on the
  30. client: the Cursor plugin uses browser sign-in, while Claude Code, Codex, and other clients send
  31. an API key created in [Pascal Settings](https://editor.pascal.app/settings). Some hosted
  32. operations, such as Architect runs, consume Pascal credits.
  33. The local commands below need the `pascal` command on your `PATH` (Node.js 22.23.4+ on 22.x,
  34. 24.22.1+ on 24.x, or 26.12.1+):
  35. ```bash
  36. npm install --global @pascal-app/cli
  37. ```
  38. > [!IMPORTANT]
  39. > Use one active agent client per local CLI service. The standalone local HTTP runtime shares
  40. > active scene state between clients; use separate `PASCAL_HOME` directories and service
  41. > processes when independent concurrent work is required. The hosted endpoint uses a separate
  42. > session-isolated bridge.
  43. ### Claude Code
  44. Register the local server (this runs `claude mcp add --scope user pascal -- pascal mcp connect`):
  45. ```bash
  46. pascal mcp setup claude
  47. ```
  48. Or install the plugin, which bundles the skills, the local `pascal` server, and a hosted
  49. `pascal-hosted` server that prompts for an optional Pascal API key and stores it in the OS
  50. keychain (leave it empty to stay local-only):
  51. ```text
  52. /plugin marketplace add pascalorg/editor
  53. /plugin install pascal-agent-skills@pascal
  54. ```
  55. Use one or the other. Claude Code 2.1.258 loads both the user-scoped `pascal` server created by
  56. `pascal mcp setup claude` and the plugin-provided server. Remove the manual entry
  57. before reloading or restarting Claude Code so only the plugin owns the connection lifecycle:
  58. ```bash
  59. claude mcp remove --scope user pascal
  60. ```
  61. Use `/mcp` to remove or disable any project- or local-scoped Pascal connection too. Leaving both
  62. connections active violates the one-active-agent-client-per-local-service requirement.
  63. ### Cursor
  64. Install [Pascal from the Cursor marketplace](https://cursor.com/marketplace/pascal). It adds the
  65. skills, a local `pascal` server launched through `npx` (no global install needed), and a hosted
  66. `pascal-hosted` server. For hosted work, open **Customize → MCPs** and choose **Authenticate**
  67. beside `pascal-hosted`; Pascal opens in your browser to sign in and choose a workspace. No API
  68. key is needed. Leave `pascal-hosted` disconnected for local-only work.
  69. Without the plugin, add the servers you want to `.cursor/mcp.json`:
  70. ```json
  71. {
  72. "mcpServers": {
  73. "pascal": {
  74. "type": "stdio",
  75. "command": "npx",
  76. "args": ["--yes", "--package=@pascal-app/cli", "pascal", "mcp", "connect"]
  77. },
  78. "pascal-hosted": {
  79. "type": "http",
  80. "url": "https://editor.pascal.app/api/mcp",
  81. "auth": {
  82. "CLIENT_ID": "pascal-cursor",
  83. "scopes": ["openid", "profile", "offline_access", "scene:read", "scene:write", "architect:run"]
  84. }
  85. }
  86. }
  87. }
  88. ```
  89. The plugin's own configuration is [`.cursor-plugin/mcp.json`](.cursor-plugin/mcp.json).
  90. ### Codex
  91. Register the local server (this runs `codex mcp add pascal -- pascal mcp connect`):
  92. ```bash
  93. pascal mcp setup codex
  94. ```
  95. Or install the plugin, which adds the skills and the same local server:
  96. ```bash
  97. codex plugin marketplace add pascalorg/editor
  98. codex plugin add pascal-agent-skills@pascal
  99. ```
  100. For a hosted workspace, register the endpoint with an API key held in an environment variable
  101. (Codex stores the variable name, not the key):
  102. ```bash
  103. codex mcp add pascal-hosted \
  104. --url https://editor.pascal.app/api/mcp \
  105. --bearer-token-env-var PASCAL_API_KEY
  106. ```
  107. ### Other MCP clients
  108. Print the generic configuration with `pascal mcp config`:
  109. ```json
  110. {
  111. "mcpServers": {
  112. "pascal": {
  113. "command": "pascal",
  114. "args": ["mcp", "connect"]
  115. }
  116. }
  117. }
  118. ```
  119. The connector discovers the local service's port and private token itself. Check it with
  120. `pascal mcp status` or `pascal doctor`. For hosted access, point a Streamable HTTP client at
  121. `https://editor.pascal.app/api/mcp` with an `Authorization: Bearer <api key>` header.
  122. ### Agent skills
  123. [![Install with skills](https://skills.sh/b/pascalorg/editor)](https://skills.sh/pascalorg/editor)
  124. The plugins above include Pascal's public agent workflows. To install only the skills with
  125. [skills.sh](https://skills.sh):
  126. ```bash
  127. npx skills add pascalorg/editor \
  128. --skill pascal-3d \
  129. --skill furniture-fit
  130. ```
  131. [`pascal-3d`](skills/pascal-3d/SKILL.md) covers safe local or hosted MCP setup and verified scene
  132. work. [`furniture-fit`](skills/furniture-fit/SKILL.md) produces a bounded, evidence-based
  133. footprint assessment. OpenClaw installation becomes available after the skills are published
  134. under Pascal's ClawHub publisher.
  135. ### More on agents
  136. - [MCP documentation](https://editor.pascal.app/docs/developers/mcp) and [local editor documentation](https://editor.pascal.app/docs/developers/local-editor)
  137. - [llms.txt](https://editor.pascal.app/llms.txt) — documentation index for language models
  138. - [skills/README.md](skills/README.md) — every plugin channel, per-host setup, and validation
  139. - [`server.json`](server.json) — the `app.pascal/editor` manifest, published on the [official MCP Registry](https://registry.modelcontextprotocol.io/v0.1/servers/app.pascal%2Feditor/versions/latest)
  140. ## Run the editor locally
  141. Create a persistent local Pascal installation without cloning this repository:
  142. ```bash
  143. npx @pascal-app/cli editor
  144. ```
  145. The CLI starts the editor and an authenticated MCP service in the background, selects
  146. collision-free loopback ports, and keeps projects in `~/.pascal/data/pascal.db`. The web editor
  147. runtime is downloaded once per version on the first command that starts the editor and verified
  148. against a digest published inside the package; `pascal mcp connect` needs no download. See
  149. [Run Pascal locally](https://editor.pascal.app/docs/developers/local-editor) for pnpm/Bun
  150. commands, project management, updates, offline installs, storage paths, and troubleshooting.
  151. ## Self-host it
  152. The editor ships as one container, `ghcr.io/pascalorg/pascal-editor`, tagged with the same
  153. version as the npm packages (`latest` follows stable releases). Projects live in SQLite under
  154. `/data`; one admin password protects the instance; `PASCAL_PUBLIC_URL` is read at runtime, so the
  155. same image serves any domain.
  156. ```bash
  157. docker run -d -p 3000:3000 -v pascal-data:/data \
  158. -e PASCAL_ADMIN_PASSWORD=change-me \
  159. -e PASCAL_PUBLIC_URL=https://pascal.example.com \
  160. ghcr.io/pascalorg/pascal-editor:latest
  161. ```
  162. See [SETUP.md, "Self-hosting"](SETUP.md#self-hosting) for the compose file, the variables, agent
  163. access and public embeds.
  164. To have the container hosted and managed for you, deploy it on Elestio:
  165. <a href="https://dash.elest.io/deploy?soft=Pascal&id=595"><img src="https://elest.io/images/logos/deploy-to-elestio-btn.svg" alt="Deploy on Elestio" height="32"></a>
  166. ## Use the published packages
  167. Install the full built-in viewer set, then load the built-in plugin once before mounting
  168. `<Viewer>`:
  169. ```bash
  170. npm install @pascal-app/core @pascal-app/viewer @pascal-app/editor @pascal-app/nodes
  171. ```
  172. ```typescript
  173. import { loadPlugin } from '@pascal-app/core'
  174. import { builtinPlugin } from '@pascal-app/nodes'
  175. await loadPlugin(builtinPlugin)
  176. ```
  177. See the [`@pascal-app/viewer` quick start](packages/viewer/README.md#usage) for a React example,
  178. and [`@pascal-app/editor`](packages/editor/README.md) to embed the full editor. Capture sessions
  179. ship as the optional `@pascal-app/core/capture` and `@pascal-app/viewer/capture` subpaths.
  180. [`@pascal-app/ifc-converter`](packages/ifc-converter/README.md) converts IFC files into Pascal
  181. scene graphs.
  182. ## Develop from source
  183. Run from the repository root so the package watchers hot-reload changes in `packages/*`:
  184. ```bash
  185. bun install
  186. bun dev # builds the packages, watches them, and serves the editor at http://localhost:3002
  187. ```
  188. Build everything with `turbo build`, or one package with `turbo build --filter=@pascal-app/core`.
  189. See [SETUP.md](SETUP.md) for prerequisites and environment variables,
  190. [docs/architecture.md](docs/architecture.md) for how the packages fit together, and
  191. [docs/releasing.md](docs/releasing.md) for npm, container, and MCP Registry publishing.
  192. ### Build a plugin
  193. A plugin ships node kinds (schema, 3D/2D rendering, placement tools, inspector parametrics) and
  194. left-rail panels through the same `Plugin` manifest the built-ins use. Start with the
  195. [plugin guide](https://editor.pascal.app/docs/developers/plugins) and the worked example
  196. [`pascalorg/plugin-trees`](https://github.com/pascalorg/plugin-trees).
  197. ## A first look at Pascal Next
  198. [Explore the live demo](https://editor.pascal.app/next) — a real home reconstructed
  199. in detail, from its rooms and finishes to the structure and systems behind the walls.
  200. This hosted preview explores the direction of the next Pascal editor; the experience
  201. shown here is not yet part of the open-source editor release.
  202. | Exploded view — see how the home fits together | Cut view — slice through the building |
  203. | --- | --- |
  204. | [![Roof lifted above the reconstructed home](docs/media/next-demo/exploded.gif)](https://editor.pascal.app/next) | [![A section cut reveals the roof framing and interior](docs/media/next-demo/cutview.gif)](https://editor.pascal.app/next) |
  205. | **X-ray — reveal the modeled systems** | **Walkthrough — step inside at eye level** |
  206. | [![Building systems isolated with the walls hidden](docs/media/next-demo/xray.gif)](https://editor.pascal.app/next) | [![Walking through the home toward the pool terrace](docs/media/next-demo/walkthrough.gif)](https://editor.pascal.app/next) |
  207. | **Interactions — open doors and explore** | **Environment — change the light and atmosphere** |
  208. | [![Interacting with doors in the reconstructed home](docs/media/next-demo/interactions.gif)](https://editor.pascal.app/next) | [![Changing the lighting around the reconstructed home](docs/media/next-demo/environment.gif)](https://editor.pascal.app/next) |
  209. We are exploring what this could make possible for facility management, home services,
  210. architecture, home building, and infrastructure.
  211. [Join the discussion on X](https://x.com/pascal/status/2102097655031558496)
  212. and tell us where you would use it.
  213. Making a video, tutorial, article, or social post about Pascal? You are welcome to use and edit
  214. this footage, including in monetized content, under [CC BY 4.0](docs/media/next-demo/LICENSE.md).
  215. Credit Pascal, link the license, and note your edits; no separate permission is needed.
  216. [Download the six original videos and see the creator guide](docs/media/next-demo/README.md).
  217. ## FAQ
  218. **What is Pascal Editor?**
  219. An open-source 3D building editor for architecture, engineering, construction, and operations. It
  220. runs in the browser, locally through its CLI, or self-hosted, and exposes the same scenes to AI
  221. agents over MCP.
  222. **Is it free and open source?**
  223. Yes. The editor, packages, CLI, and MCP server in this repository are MIT-licensed. Hosted
  224. services at editor.pascal.app are separate from the open-source release and have their own
  225. account terms.
  226. **Does it work offline?**
  227. The local CLI keeps projects on your machine, and its MCP service needs no network download.
  228. Starting the editor downloads its web runtime once per version; for a host without network
  229. access, pass `--runtime <directory-or-archive>`. See the
  230. [local editor documentation](https://editor.pascal.app/docs/developers/local-editor).
  231. **How do AI agents connect?**
  232. Through MCP. Local agents run `pascal mcp connect` with no account; hosted workspaces use
  233. `https://editor.pascal.app/api/mcp` with the client's sign-in or API key. See
  234. [Connect an AI agent (MCP)](#connect-an-ai-agent-mcp).
  235. **Does it support IFC?**
  236. IFC import is provided by [`@pascal-app/ifc-converter`](packages/ifc-converter/README.md), which
  237. converts IFC files into Pascal scene graphs. Sites, buildings, levels, walls, doors, windows,
  238. slabs, columns, and spaces become native Pascal nodes when their parameters can be recovered;
  239. other elements are kept as selectable imported meshes.
  240. ## Contributing
  241. Bug fixes, features, docs and ideas are all welcome. Start with [CONTRIBUTING.md](CONTRIBUTING.md)
  242. for setup, code style and the PR flow.
  243. - New node kinds and sidebar panels ship as [plugins](https://editor.pascal.app/docs/developers/plugins) rather than edits to the built-ins
  244. - Questions and ideas go to [Discussions](https://github.com/pascalorg/editor/discussions); reproducible bugs go to [Issues](https://github.com/pascalorg/editor/issues)
  245. - Participation is covered by our [Code of Conduct](CODE_OF_CONDUCT.md)
  246. - Security problems go to [SECURITY.md](SECURITY.md), not a public issue
  247. ## Contributors
  248. <a href="https://github.com/Aymericr"><img src="https://avatars.githubusercontent.com/u/4444492?v=4" width="60" height="60" alt="Aymeric Rabot" style="border-radius:50%"></a>
  249. <a href="https://github.com/wass08"><img src="https://avatars.githubusercontent.com/u/6551176?v=4" width="60" height="60" alt="Wassim Samad" style="border-radius:50%"></a>
  250. <a href="https://github.com/sudhir9297"><img src="https://avatars.githubusercontent.com/sudhir9297?v=4" width="60" height="60" alt="Sudhir" style="border-radius:50%"></a>
  251. ---
  252. <a href="https://trendshift.io/repositories/23831" target="_blank"><img src="https://trendshift.io/api/badge/repositories/23831" alt="pascalorg/editor | Trendshift" width="250" height="55"/></a>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.