# @pascal-app/mcp Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server. - **Type:** MCP server - **Trust:** 85/100 (A), scored on the package rubric - **Verification:** verified (build provenance) - **Version:** 1.0.6 - **Author:** app.pascal - **License:** Unknown - **npm:** @pascal-app/mcp - **Endpoints:** streamable-http https://editor.pascal.app/api/mcp - **Source:** https://github.com/pascalorg/editor - **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport) ## Trust 85/100 (A), scored on the package rubric - Publisher verified: no - Build provenance: verified attestation - npm trusted publishing (OIDC): yes - Install scripts: nothing suspicious found - Prompt-injection scan: not run - Obfuscation scan: not run - Evidence age: 0 days ## Security scan - **Status:** clean - **Scanned:** 2026-10-25T09:24:59.475Z - **Version scanned:** 1.0.6 - **CVEs:** none found by OSV at scan time ## Tools 27 declared. Statically extracted from the shipped source — a floor on the surface, not a census. - `analyze_floorplan_image` — Defer to the MCP host (via sampling) to extract walls, rooms, and approximate dimensions from a floor-plan image. Requires host support for sampling. - `analyze_room_photo` — Defer to the MCP host (via sampling) to extract approximate dimensions, fixtures, and windows from a single-room photograph. Requires host support for sampling. - `apply_patch` - `check_collisions` — Assess declared item footprints with a rotation-aware plan AABB test. Supports an explicit minimum clearance and reports units, source dimensions, skipped evide - `create_story_shell` — Create one level-owned building shell from a footprint: the perimeter walls. The floor plate and the ceiling are DERIVED from the rooms the walls enclose — neve - `create_from_template` — Instantiate a seed Pascal scene template into the bridge. Regenerates all ids before applying. When `save: true` and a SceneStore is wired, also persists the ne - `create_house_from_brief` — High-level hosted workflow for external agents: choose a starter house from a brief, create/save/publish it, and return the editor URL. Use semantic tools after - `create_project` — Create a browser-visible Pascal project for the authenticated user. Use this before save_scene when the user asks for a new project. - `create_unit` — Create a named unit in a building, optionally referencing zones across its levels. - `delete_scene` — Remove a stored scene by id. In Pascal this never deletes the project: it hides it from Pascal's public listings until it is next saved with content, and answer - `export_glb` — GLB export is not available in headless mode — it requires the Three.js renderer, which is browser-only. Returns a structured `not_implemented` tool error. - `export_json` — Return the scene as a serialized JSON string. Pass `pretty: true` to indent with 2 spaces. - `generate_variants` — Generate N variations of a base scene by forking and applying seeded mutations. Example: "give me 5 variations of this kitchen". If `save=true`, each variant is - `get_project_status` — Authoritative status/debug call for a Pascal project: editor URL, browser-visible version, latest saved version, published version, node count, and graph hash. - `get_scene` — Returns the full scene graph: flat node dictionary, root node IDs, collections, and explicit installed plugin IDs when present. - `list_scenes` — List scenes in the SceneStore. Optionally filter by `projectId` and cap results with `limit` (default 100). - `list_templates` — List the seed Pascal scene templates available to `create_from_template`. Returns the id, display name, one-line description and node count for each. - `list_units` — List units with their member zones and current area reports, optionally filtered by building. - `load_scene` — Load a scene from the SceneStore into the bridge. Returns the scene metadata. Throws `scene_not_found` if the id does not exist. - `measure` - `photo_to_scene` — Orchestrator: analyse a floor-plan photo via MCP sampling, translate the structured vision result into a Pascal SceneGraph (site → building → level with walls a - `redo` — Redo the next N previously-undone steps (default 1). Returns the number of steps actually redone. - `rename_scene` — Rename a scene in the SceneStore. Returns the updated SceneMeta. Optionally pass `expectedVersion` for optimistic concurrency. - `save_scene` — Save the current scene (or a provided graph) to the SceneStore. Without id or projectId it saves to the project this session is bound to (create_project or load - `set_unit_members` — Replace the zones referenced by a unit. Every zone must belong to a level in the same building. - `set_zone` — Create a polygonal zone on the given level. label is stored as the zone name and properties are merged into metadata. A polygon along walls that already enclose - `undo` — Undo the most recent N steps in the scene history (default 1). Returns the number of steps actually undone. ## Install **Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured. **Config** (claude-code): ```json "{\n \"mcpServers\": {\n \"mcp\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@pascal-app/mcp\"\n ]\n }\n }\n}" ``` ## Blast radius Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs commands; runs locally and hosted. - Floor 50, ceiling 78 (tier: unknown) - `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low. - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/%40pascal-app%2Fmcp - Install plan: https://forgeregistry.com/api/v1/packages/%40pascal-app%2Fmcp/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/%40pascal-app%2Fmcp - HTML page: https://forgeregistry.com/registry/%40pascal-app%2Fmcp - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.