Glif MCP

​

What you can do with it

• Create marketing assets: hero images, landing-page graphics, blog headers, ad sets and launch materials
• Explore visual concepts: generate several logo, illustration or design directions
• Adapt existing designs: make variations, dark-mode versions and alternate formats for every placement
• Create motion: short animations and video concepts that explain products, features or user flows
• Work from your existing documents: if your agent can read your briefs, product sheets or brand docs, it can pass the details straight to Glif
• Run your brand Skills from anywhere: “Use our launch-ad-set skill on this product photo.”

​

How to get started

​

Option A: Agent-led setup

Install the Glif MCP server: https://glif.app/api/mcp — full instructions: https://glif.app/llms.txt

​

Option B: Manual setup

• Claude
• ChatGPT
• Cursor
• VS Code
• LM Studio
• Kiro
• Replit

• Claude Code
• Codex
• Hermes
• OpenClaw

1. Go to Customize → Connectors → + → Add custom connector.
2. Paste this URL:

   https://glif.app/api/mcp

3. Approve the Glif sign-in when Claude opens the OAuth flow.

​

Example prompts

• “Make a hero banner image for my landing page — hand-drawn, on brand”
• “Generate header art for my blog post about our API launch”
• “Generate 4 logo concepts for my MCP server launch”
• “Make dark-mode variants of these graphics”
• “Make a quick animation about users going through this app”
• “Use Glif to make 3 static ad concepts for this product in 4:5 and 9:16, using our brand kit”
• “Continue the Glif project from earlier and add two more headline variations”

​

Costs

​

Manage access

​

More on glif.app

• MCP setup
• API overview
• API tokens and connected apps
• Glif MCP capabilities (llms.txt)
• Security

​

Agent Reference

​

Connection

​

Tools

​

Standard run for a campaign request

1. Gather the brief: product, audience, channels and formats, quantity, copy, video length.
2. Call list_user_skills to find a brand or production skill; plan to name it in the prompt.
3. Upload product photos, logos or guidelines with upload_file if they aren’t already Glif assets.
4. For large jobs, call whoami and estimate cost from typical per-output figures.
5. Confirm the plan and estimate with the user. compose_project charges credits and has no approval step.
6. Call compose_project with the whole set in one prompt. Share projectUrl right away.
7. Poll get_job_status with job_id, passing each progressCursor back as progress_cursor. Share new assets once each as they arrive.
8. Report the final result or failure. On input_required, ask the user rather than guessing.
9. For revisions, resizes and cutdowns, call compose_project with the same project_id.

​

Rules

• Don’t call compose_project while a job is working. In the same project it errors; without project_id it starts a separate billable job.
• Never start another paid job automatically, including retries.
• Put a campaign set (concepts × formats × variations) in one prompt to keep it in one project.
• Reusing earlier media requires project_id or asset_ids.
• Prefer resizing an approved asset over regenerating it per placement.
• Don’t end with only a “started” message unless the user asked for background work. If polling can’t continue, say so and share the project link.
• Job records expire about 30 minutes after a job finishes. Saved media remains available via get_project.
• Share media URLs as plain links; some hosts show Markdown image embeds as broken.
• https://glif.app/brand.md is Glif’s own brand guide. Use it only for Glif-branded work, not for the user’s brand.

​

Example

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "compose_project",
    "arguments": {
      "prompt": "Use my `launch-ad-set` skill. Product: Cha Cha Club iced matcha. Audience: NYC commuters 25–40. Key message: 'Hand-whisked. Never powdered. Always iced.'",
      "asset_ids": ["img_PRODUCTXXXXXXXXXXXXXX", "img_LOGOXXXXXXXXXXXXXXXXX"],
      "intelligence": "smart"
    }
  }
}

​

Support