Terminal-first developer workflow
From platform question to verified project—without a credential
The Mappls Developer CLI packages the canonical portal catalog into one offline tool. Search every published surface, create the correct platform seam, and prove its evidence and credential boundaries before a live adapter exists.
A clean first loop
Download. Verify. Discover. Create. Inspect.
The archive is self-contained and dependency-free at runtime. Its catalog snapshot is generated from the same source used by the website, global search, API, and starter downloads. The checksum verifies the archive; the included tests verify behavior.
A green doctor report proves project hygiene—not Mappls entitlement, package compatibility, regional availability, quota, or production approval.
curl -O https://developer.mappls.com/downloads/mappls-developer-cli.zip
curl -O https://developer.mappls.com/downloads/mappls-developer-cli.zip.sha256
shasum -a 256 -c mappls-developer-cli.zip.sha256
unzip mappls-developer-cli.zip -d mappls-developer-cli
cd mappls-developer-cli && npm testNine bounded commands
Small enough to trust. Useful enough to keep.
No login, telemetry, provider request, credential flag, hidden install, or automatic live-mode promotion.
platformsList all 13 exact platform starters with readiness and language.
search <query>Rank the complete local documentation catalog without network access.
starter listShow the canonical starter identity for every published platform.
starter show <id>Inspect scope, source, credential boundary, files, and portal path.
starter create <id>Write one clean fixture-first or contract-only project into an empty directory.
manifest createLock one of 624 use-case, platform, and operating-depth decisions to source evidence.
manifest validate [path]Fail CI when canonical fields drift, identity is unknown, or an application overlay leaks restricted evidence.
dossier validate [path]Verify integrity and reject leaked material, missing authority, or attempted production self-approval.
doctor [path]Fail on missing controls, unknown identity, credentials, unsafe files, or workstation leakage.
Project doctor
Turn “it looks fine” into bounded evidence.
The doctor recognizes the canonical starter identity, requires every project file, validates the manifest-to-platform link, scans a bounded set of regular text files, skips symlinks, and surfaces selection-required or entitlement-required readiness as a warning.
Canonical manifest and platform identityRequired source, evidence, environment, and acceptance filesPopulated credential, bearer, private-key, and production-style key patternsDeveloper workstation paths and unscanned symbolic linksLive-call declaration and non-public readiness gates
The next boundary stays deliberate
The CLI creates a seam, not a production claim.
Continue with the platform quickstart, bind only the company-approved distribution or endpoint, exercise hostile paths, and attach the resulting evidence to release governance.