Give your agent a brand animator

How it works

The endpoint is a hand-rolled JSON-RPC 2.0 server over streamable HTTP — POST https://logoanimator.audio-1ae.workers.dev/api/mcp. It implements the baseline MCP handshake: initialize, tools/list, and tools/call. No MCP SDK, no persistent connection to manage — a single POST per call, exactly like every other tool your agent already talks to.

Available tools

• list_animations

  List every animation available in LogoAnimator, the dot-matrix logo animator, with id, display name, and category.

• recommend_settings

  Suggest an animation, density, and color settings for a logo based on its kind and mood. Pure heuristic — does not fetch, decode, or inspect any image.

• animate_logo

  Render a logo image into an animated dot-matrix SVG. Accepts base64-encoded PNG bytes only — does not fetch URLs.

Authentication

Every call needs an API key from an active Pro or Studio account, issued from the account menu in the editor. Send it as a bearer token — or, if your client can't set Authorization, the equivalent x-api-key header:

Authorization: Bearer dm_live_your_api_key

Example config

A remote/streamable-HTTP MCP client config — the shape most agent frameworks expect for a URL-based server:

{
  "mcpServers": {
    "dotmatrix": {
      "url": "https://logoanimator.audio-1ae.workers.dev/api/mcp",
      "headers": {
        "Authorization": "Bearer dm_live_your_api_key"
      }
    }
  }
}

Or call it directly:

curl https://logoanimator.audio-1ae.workers.dev/api/mcp \
  -H "Authorization: Bearer dm_live_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_animations"}}'