Pascal 3D Editor

io.github.pascalorgPublished by GitHub account pascalorgv0.6.1Updated Oct 11, 2026

Create, inspect, validate, and save editable 3D building scenes with Pascal's hosted MCP server.

The publisher's own server: Pascal 3D Editor

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Lets an assistant create, inspect, validate, and save editable 3D building scenes through Pascal's hosted editor.

What you can do
Pascal 3D Editor is a hosted MCP server that works with editable 3D building scenes. According to the registry description, it lets an assistant create, inspect, validate, and save such scenes. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it
Worth adding when you want an assistant to help build or review 3D building scenes in Pascal's editor rather than doing it by hand. It suits workflows where scenes need to be checked for validity before being saved.
Requirements
A remote MCP endpoint at editor.pascal.app over streamable HTTP. It requires an Authorization header carrying a Bearer API key created in Pascal Settings, in the form Bearer sk_live_... . No local runtime or packages are needed.
Before you install
The server asks for a live API key sent as the Authorization header; treat it as a secret and avoid exposing it in logs or shared configuration. The description mentions saving scenes, so assistant actions may change stored work. No payment or wallet details are shown in the input.

Installation

In SourceWeft

  1. Open Pascal 3D Editor 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.pascalorg%2Feditor/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": {
    "pascal-3d-editor": {
      "type": "http",
      "url": "https://editor.pascal.app/api/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v0.6.1LatestSep 16, 2026

Score

28% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Pascal integrations