Skip to main content

​
Connect

In Dynamite, select Install MCP and copy the connection details into your client. Use the returned endpoint and key.
Store the key in your client’s secret store. The connection uses Streamable HTTP. Call tools/list to see the tools available to your role and deployment.

​
Create a draft

  1. Read get_organization, then get_website and get_context.
  2. Inspect the page and choose a target.
  3. Use save_target and save_variant to author the change.
  4. Read it back and preview it on the site.
Example save_target request:
Use the website UUID and version from the latest read. Save the returned target ID and new version for your next call.

​
Publish

Set a primary goal, confirm installation, and run check_test. Publish when the user has approved going live. A checkout URL means activation is still pending; verify the final release state.
A CONFLICT means the workspace changed. Read it again and reconcile your edit; do not increment the version yourself. Settings and memory tools have different inputs—check the tool reference.Inspect MCP isError and the returned JSON, even when HTTP succeeds. After an interrupted write, reread before retrying a creation.
Keys are scoped to their creator’s current permissions, organization, audience, expiry, and optional workspace. Admin and setup connections use separate endpoints.inspect_page reads script-free server HTML, so JavaScript-rendered content can be absent. Verify the browser DOM in preview. Use memory tools for prior research and decisions when available.
Next: Agent recipes or Configuration as code.