The loop around the tools: read your brand context, write and render content locally, push the finished piece back here for you to publish. Agents reading this site can start from /llms.txt.
Everything below assumes the MCP is connected. That is one command and one token — Connect an agent walks it, and the MCP page mints the token. Once connected, run /mcp in Claude Code and 56 tools should be listed. The exceptions are push_creative and push_slideshow: both read a file off your local disk, so they exist only on the stdio server that ships in the repo. Over HTTP, upload via POST /v1/creatives (multipart) instead.
Content (memes, reels, edits) is produced locally in the repo's content/ Remotion workspace:
cd attribura/content && npm install
npm run studio # optional: hot-reload preview editorClaude Code picks up the create-content skill automatically inside the repo — it carries the format catalog, caption conventions, safe areas, and the copywriting reference. Just ask it for a meme, a reel, or a facecam edit.
get_context → write copy → render locally (Remotion)
→ Claude previews the frames itself → push_creative
→ it lands on the Board as a draft → you review,
edit the caption, mark ready → publishEvery video is a recipe (a props JSON + a template): ask Claude for any change — a different hook, caption position, a b-roll swap — and it edits the recipe and re-renders identically.
56 tools over the hosted server, in 8 domains. What each one does, and which of them a read-only token can call, is in the tool catalog.