Snaptrude

Build a Snaptrude plugin — first-turn onboarding for vague requests

FIRST-TURN ONBOARDING for vague plugin requests. Call this for exact or near-exact prompts like "build a snaptrude plugin", "build a plugin", "make me a plugin", "create a plugin", "help me build a plugin", "how do I get started", "how do I build a snaptrude plugin", "what can you do", "help", "hi", or any first message that does not name the plugin's target behavior. Returns the Snaptrude Plugin Lab welcome / starter-choices message. Emit the returned 'message' field VERBATIM as your reply — d

Sign in to Snaptrude — start the authentication / login flow

Start Snaptrude authentication. Sign in / log in / authenticate the user via the browser-approval device-code flow. Returns a browser URL the user must open and approve, plus an opaque sessionId to carry forward on every auth-requiring tool call. The access token stays server-side; only the sessionId is exposed. Call this whenever an auth-gated tool returned AUTH_REQUIRED or AUTH_EXPIRED, or when the user explicitly asks to sign in / log in / authenticate. After this returns, surface the browse

Complete Snaptrude sign-in — verify the user approved in the browser

Complete Snaptrude authentication. Verify that the user has approved the sign-in / login in their browser. Call this after starting an authentication flow, repeatedly every few seconds, until the status returns 'complete' (sign-in approved) or 'expired' (request timed out, start over). Args: - sessionId (string): the sessionId from the pending authentication flow Returns one of: - { status: 'pending' } — user has not yet approved; call again in a few seconds - { status: 'expired' } — the

Show the current Snaptrude session user

Verify a sessionId is still authenticated and return the user's identity + token expiry. Useful for confirming a stored session is valid before doing real work. Args: - sessionId (string) - response_format ('markdown' | 'json'): default 'markdown' Returns: { loggedIn: true, user, environment, expiresAt? } Errors: AUTH_REQUIRED, AUTH_EXPIRED.

Log out of Snaptrude — clear the current server-side session

Clear the Snaptrude authentication session for the given sessionId. Use when the user asks to log out, sign out, switch accounts, or stop using the current Snaptrude account from this chat. This clears the MCP server's session entry. It does not revoke backend refresh tokens, but the old sessionId can no longer be used by MCP tools after this call. Args: { sessionId } Returns: { ok: true, message }

API reference — look up snaptrude.* call signatures

API REFERENCE for the snaptrude.* call surface (design.create, design.query, design.transform, core.math.vec3, core.geom.query.curve, core.units, core.io.import, program.spreadsheet, presentation.views, analysis.shadows, etc.). Look up call signatures, parameter types, and return shapes for the plugin-client modules. Use this lightly during planning to check feasibility, and use it deeply during implementation when you're writing src/worker.ts and need exact call signatures. Do NOT use it for o

Snaptrude plugin examples — list or fetch a starter

Snaptrude plugin starter examples: list the curated examples, or fetch one example's full file contents. Two modes, one tool — pick by whether exampleId is provided. Omit exampleId to LIST every starter example with a description and resourceUri. Use this to decide which one to fetch. Provide exampleId to FETCH that example's complete files (path + contents pairs, ready to pass to the publish tool after customizing manifest.name). Args: { exampleId?: string, response_format? } Returns (list m

Upgrade notes — migrate a plugin between plugin-client versions

Get migration notes for upgrading @snaptrude/plugin-client between versions, e.g. from 0.5.0 to 0.6.0. Two modes, one tool — pick by whether BOTH from and to are provided. - Omit from/to to LIST the available upgrade spans ({from, to, breaking} per released minor step). - Provide from AND to to FETCH the concatenated markdown notes for every span in that range, in upgrade order (multi-hop ranges chain automatically, e.g. 0.4.0 -> 0.6.0 returns the 0.5.0 and 0.6.0 notes). Args: { from?: string,

Validate Snaptrude plugin source (no build)

Run cheap static checks on the plugin's source files. Does NOT invoke esbuild — sub-second feedback so the LLM can self-correct before burning a build slot. Checks (in order): 1. Path allowlist (src/worker.ts, src/App.tsx, src/App.css, src/index.css, src/modules/<name>.ts, src/assets/<file>.{json,svg}) 2. Required files: src/worker.ts and src/App.tsx 3. Size caps: 256 KB per file, 2 MB total 4. Manifest sanity: name is lowercase-hyphen; version is semver-like 5. Import allowlist: reac

Publish a Snaptrude plugin

Build the supplied source files with esbuild and register the plugin to the user's Snaptrude account. Creates a new plugin record. Use the update tool for subsequent revisions. Send UNMINIFIED authored source — this server bundles and minifies with esbuild. Never pre-bundle or minify before uploading: it is redundant work and minified code costs far more of your output budget per byte. Split logic into src/modules/<name>.ts rather than one giant file. Args: - sessionId (string) - manifest:

Update an existing Snaptrude plugin

Build and re-upload source files for an existing plugin. Requires an explicit pluginId — there is no implicit 'last published' tracking, to prevent silently updating the wrong plugin. Args: same as publish (send the COMPLETE unminified source as 'files', OR a staged 'uploadId'), plus required pluginId. The 'version' field in manifest is IGNORED on update — the server reads the currently-deployed version and bumps its patch component automatically (Snaptrude's CDN does not invalidate cached asse

Stage plugin source files for a chunked upload

Accumulate a plugin's source files across several calls so a plugin too large to emit in one message can still be published. Send one chunk of files per call; the server buffers them under an uploadId. When every file has been staged, call snaptrude_publish_plugin or snaptrude_update_plugin with that uploadId (and no inline 'files') to build and register the assembled set. Use this ONLY when the complete source won't fit in a single message. For a normal-sized plugin, pass 'files' inline to pub

List the user's Snaptrude plugins

Return the plugins registered to the signed-in user. Archived plugins are hidden by default; pass includeArchived: true to see them. Args: - sessionId (string) - limit (1..100, default 20) - offset (default 0) - includeArchived (boolean, default false) - response_format ('markdown' | 'json'): default 'markdown' Returns: { total, count, offset, has_more, next_offset?, plugins: [{ id, name, version, visibility, archived?, ... }] }

Archive a Snaptrude plugin (soft delete, recoverable)

Archive (hide) a Snaptrude plugin. Archive is a soft delete — the plugin disappears from the user's list and load surface, but the database record and every uploaded build artifact are preserved so it can be restored later with snaptrude_unarchive_plugin. Use for "I don't need this anymore", "hide this", "remove this plugin", "delete this plugin". Every chat-driven removal intent maps to archive. There is no hard-delete tool in this MCP surface (by design); if a user insists on permanent destru

Restore a previously archived Snaptrude plugin

Restore (unarchive) a previously archived Snaptrude plugin. The plugin returns to the user's list and load surface in its preserved state. Use for "restore this plugin", "bring it back", "unarchive it", or "show this plugin again". To find an archived pluginId, call snaptrude_list_my_plugins with includeArchived: true. Idempotent: a no-op if the plugin is already active. Args: { sessionId, pluginId } Returns: { pluginId, archived: false } Errors: NOT_FOUND, AUTH_REQUIRED, AUTH_EXPIRED, AUTH_

Rename a Snaptrude plugin

Change a plugin's name (and optionally description) without rebuilding or re-uploading. The plugin's pluginId, version, and bundle URL are unaffected — anyone with the plugin loaded keeps it loaded. Metadata-only; do NOT use the update tool for renames (that one rebuilds source and bumps the version). Use when the user says "rename it to X", "change the name", or "update the description". Args: { sessionId, pluginId, name (lowercase letters/digits/hyphens, ≤64 chars), description? (≤500 chars)

Log feedback, bug report, missing-API request, or feature request

Capture user feedback as tracked action items for the Snaptrude team. Use whenever the user expresses friction, reports something not working, or asks for something the API doesn't yet support. After the tool returns, tell the user in ONE plain sentence "I've logged this with the Snaptrude team" — never show ticket ids, error codes, or technical details. Delivery failures are invisible by design; the LLM should always reassure the user it was logged. Args: - category: 'bug' | 'missing_api' |