---
name: dreams-mcp
description: Connect an AI agent to the Dreams to Life MCP server to generate media and run app-store operations.
---

# Connect to the Dreams to Life MCP server

One MCP server backs Dreams to Life, Muzie, AI Invites and Appomation. It exposes the
same account surface an agent needs: media generation, marketing automations, and app
store operations.

- Endpoint: `https://api.dreamstolife.ai/appomation/mcp`
- Transport: Streamable HTTP, stateless. One request, one response.
- Auth: `Authorization: Bearer apm_live_...`. Unauthenticated requests return 401.
- Server card: <https://api.dreamstolife.ai/.well-known/mcp/server-card.json>

## Get a key

API keys are minted by the account owner inside the app, they are not self-serve for an
agent. In the app sidebar, open **Connect Agent**, select **Generate key**, and copy the
setup config. The raw key is shown once. Keys are scoped to that one user, and every tool
call runs as that user. Keys can be revoked from the same screen.

## Client config

Clients that speak HTTP MCP directly:

```json
{
  "mcpServers": {
    "dreams": {
      "type": "http",
      "url": "https://api.dreamstolife.ai/appomation/mcp",
      "headers": { "Authorization": "Bearer apm_live_..." }
    }
  }
}
```

Clients that only speak stdio need a bridge:

```bash
npx mcp-remote https://api.dreamstolife.ai/appomation/mcp \
  --header "Authorization: Bearer apm_live_..."
```

## What the tools cover

- **Media generation**: list image and video models, generate images, generate music,
  and the movie flow, create a movie, add scenes, generate scene images, generate scene
  videos, render. Generation is asynchronous, poll the matching get tool.
- **Marketing**: automation CRUD, topics, triggering a run, and the chat agent that
  builds an automation from an idea.
- **App store operations**: projects, store connectors, listing metadata and screenshots
  per locale, versions and releases, experiments, and monetization, products, prices and
  RevenueCat entitlements, offerings and packages.

The server sends its own domain primer as MCP `instructions` on connect. Read that
before calling anything, it explains the project model and which calls have side effects.

## Safety

- Generation tools spend tokens from the account balance. They cost real money.
- Store push tools change a live app listing. Some enqueue a job and return a job id.
- Sync tools overwrite locally authored content with whatever the store currently holds.
  Do not run them unless the user asked for it.