Generate simulation assets from text, images, or CAD without leaving your coding workflow.
This is Palatial's public thin client: a command-line application and a local MCP server. It uploads selected inputs to the existing Palatial API, tracks assets, and downloads export ZIPs. Generation, provider orchestration, and proprietary prompts remain on Palatial's servers. No proprietary SKILL.md is distributed.
Release status: Public preview. API contract tests and MCP transport tests are included. A paid, live generation-to-simulator acceptance run has not been performed for this release. An API READY status means outputs are available; it does not certify your simulation task.
You need a Palatial workspace API key. The coding agent calls the local MCP client, which authenticates requests to Palatial’s existing hosted API at https://dashboard.palatial.cloud/api/v1/external/. Palatial performs the generation on its servers. The client checks the returned asset ID and downloads the completed export.
flowchart LR
A["Codex CLI or Claude Code"] --> B["Local Palatial MCP client"]
B -->|"Workspace API key over HTTPS"| C["Existing Palatial API"]
C --> D["Generation on Palatial servers"]
C -->|"Status and export"| B
B --> E["Asset files in your project"]
MCP provides the tools the coding agent can call; it does not replace the Palatial API. This release uses your existing API and requires no new customer-hosted service. A Palatial key is separate from your OpenAI or Anthropic credentials. The isolated fixture tests do not use a real Palatial key; a live integration test does.
You need Node.js 22 or newer, a Palatial workspace API key, and Codex CLI or Claude Code. Generation and export use your Palatial workspace credits. Your coding agent's subscription or API charges are separate.
Install the versioned package from the official GitHub Release:
npm install --global <https://github.com/PalatialSim/palatial-agent-tools/releases/download/v0.1.0/palatial-agent-tools-0.1.0.tgz>
palatial-agent --version
palatial-agent login
palatial-agent doctor
login prompts for your workspace API key with input hidden, checks it through a read-only API call, and saves it locally. Obtain the key in Palatial dashboard workspace settings. Do not paste it into your coding-agent conversation.
The npm-compatible package is distributed through GitHub Releases. It is not yet published to the npm registry. The package name @palatial/agent-tools is metadata, not a currently verified npm installation target.
palatial-agent setup --client codex
codex
Start a fresh session, then ask:
List the Palatial tools and run palatial_doctor. Do not generate or export anything yet.
palatial-agent setup --client claude-code
claude
Use /mcp to inspect the connection, then ask for the same read-only check.