Where it fits
Architects and developers who want local-first 3D editing with MCP and AI workflows through a CLI.
- Install the CLI and run pascal mcp connect.
- Edit a 3D architectural model locally.
- Use the hosted endpoint with a Pascal API key.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with Pascal Editor
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Explore what the user wants, what they assume, and which approach is worth committing to before any creative work. Use before building a feature, component, plan, or other new work where a wrong direction is costly.
Shared vocabulary for designing deep modules. Use it to design or improve a module's interface, find opportunities to deepen one, decide where a seam goes, or make code easier to test and navigate with AI, or when another skill needs the deep-module vocabulary.
Produces several sharply different interface designs for the same module, with sub-agents working in parallel. Use it when someone wants to design an API, survey interface options, weigh different module shapes, or says design it twice.
No skills found
Try a different search term or clear the filters.
Local CLI and MCP
After installing, run pascal mcp connect, or pascal mcp setup claude/codex. Local projects stay in ~/.pascal/data/pascal.db and need no account. Hosted clients must send an API key created in Pascal Settings; Codex uses --bearer-token-env-var PASCAL_API_KEY.
- Install the CLI
Install the Pascal CLI globally.
npm install --global @pascal-app/cli - Register the local server
Connect the local stdio server to your client, or use a client-specific setup command.
pascal mcp connect - Or authenticate the hosted server
Create an API key in Pascal Settings and pass it as Authorization: Bearer. Codex can use --bearer-token-env-var PASCAL_API_KEY.
Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.
Endpoint and configuration
The installer uses the server name pascal-editor. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
pascal-editorappears and that the tools match the provider documentation. - 2Run one small request.
Start with: Install the CLI and run pascal mcp connect. Check the result before you give the server more access.
- 3Check permissions.
Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
- The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider source
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
Pascal Editor repositoryhttps://github.com/pascalorg/editor