MCP

The eight MCP tools, and the conventions they share.

Eight tools. Five answer anonymous callers, three need authorization because they spend money or credits.

The usual path is short: describe the idea → `suggest_memes` → `caption_meme`. Everything else exists for when the user already knows the template, or when a person should do the wording.

• search_templates — Find templates by text, kind or tag.
• get_template — Text box ids, example captions, and how the format works.
• list_tags — Every tag with at least one published template.
• get_editor_url — A prefilled editor link for a human to finish.
• suggest_memes — Describe an idea, get templates back already captioned. Needs a key.
• caption_meme — Render a PNG or GIF and return a permanent URL. Needs a key.
• face_swap_meme — Put a photographed face into a still template. Needs a key.
• open_meme_editor — Open the picker and live preview inline, in clients that support MCP Apps.

Conventions

These hold across every tool:

• Template references. Anywhere a template is named, an id (42), a slug (drake-hotline-bling) or the <slug>-<id> form from an editor URL all work.
• Captions. Either an array applied to the text boxes in order, or an object keyed by box id from get_template. Up to 16 captions, 300 characters each. An id the template doesn't have is rejected rather than quietly dropped.
• Casing and fit. Captions are drawn in the meme font and uppercased. Short lines stay large; a sentence shrinks until it fits. Write short.
• GIF presets. high, discord (the default), compact and emoji, in descending order of size. Ignored when rendering a still.
• Cost. Only face_swap_meme spends credits. Everything else is limited by rate limits alone.
• Errors. A tool that fails returns isError with a sentence explaining what to do, not a stack trace.