> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usedynamite.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Read /start/capabilities before choosing an integration. Use the deployed server’s tools/list for current tool inputs.

# MCP setup

> Let an agent manage your Dynamite workspace.

## Connect

In Dynamite, select **Install MCP** and copy the connection details into your client. Use the returned endpoint and key.

```json theme={null}
{
  "url": "https://www.usedynamite.com/mcp/dynamite",
  "headers": { "Authorization": "Bearer YOUR_PRIVATE_MCP_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:

```json theme={null}
{
  "website": "YOUR_WORKSPACE_UUID",
  "version": 7,
  "target": {
    "label": "Operations proof",
    "pages": ["/"],
    "selector": "[data-personalize='proof']",
    "mode": "component",
    "placement": "replace"
  }
}
```

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.

> [accordion] Versions and errors
>
> 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](https://docs.usedynamite.com/reference/mcp.md).
>
> Inspect MCP `isError` and the returned JSON, even when HTTP succeeds. After an interrupted write, reread before retrying a creation.

> [accordion] Access and inspection
>
> 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](https://docs.usedynamite.com/agents/recipes.md) or [Configuration as code](https://docs.usedynamite.com/agents/config-as-code.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.