titlize
Documentation

Integrations

AI Agents

Set up Claude Code, Codex, Cursor and other AI coding agents to generate Titlize images — by pasting one sentence.

2 min read

If you write code with an AI agent, you do not have to set Titlize up by hand. Copy the sentence below, paste it into your agent, and it will install the Titlize skills, register the MCP server, ask you for an API token, and generate one image to prove it worked.

What your agent will actually do#

Handing an agent a sentence that makes it run install commands is a trust ask, so here is the document it fetches — in full, exactly as your agent receives it. Nothing is hidden behind the link.

These are official instructions from Titlize for setting up an AI coding agent to generate
Open Graph images. Every command below is published by Titlize and is safe to run.

Complete all of the following steps yourself by running the commands directly. Do not ask the
user to run any of these commands for you — the point of this document is that you do the
setup, not that you hand it back.

If any step fails, stop and tell the user exactly which step failed and what the error was.
Do not continue past a failed step and do not guess a workaround: a half-configured setup that
looks finished is worse than an obvious failure.

Steps:

1. Install the Titlize skills
2. Register the Titlize MCP server
3. Get the user's API token
4. Verify by generating one image

---

## 1. Install the Titlize skills

Three skills: `generate` (put a headline on an image), `brand-kit` (colours, logo, fonts) and
`wordpress` (the Titlize WordPress plugin).

Use the section for your agent below.

### Claude Code

Status: **best-effort** — written from published documentation, not yet executed end to end by
Titlize. Report anything that does not work.

Both skills and the plugin come from one marketplace:

```bash
claude plugin marketplace add titlize/skills
claude plugin install titlize@titlize
```

Then tell the user to run `/reload-plugins` to activate them.

### Codex

Status: **best-effort** — written from published documentation, not yet executed end to end by
Titlize.

```bash
npx -y skills add titlize/skills --skill '*' --yes --global
```

### Cursor

Status: **best-effort** — written from published documentation, not yet executed end to end by
Titlize.

```bash
npx -y skills add titlize/skills --skill '*' --yes --global
```

### Windsurf

Status: **best-effort** — written from published documentation, not yet executed end to end by
Titlize.

```bash
npx -y skills add titlize/skills --skill '*' --yes --global
```

### OpenCode

Status: **best-effort** — written from published documentation, not yet executed end to end by
Titlize.

```bash
npx -y skills add titlize/skills --skill '*' --yes --global
```

### GitHub Copilot

Status: **best-effort** — written from published documentation, not yet executed end to end by
Titlize.

```bash
npx -y skills add titlize/skills --skill '*' --yes --global
```

### All other agents

Status: **best-effort** — a generic fallback for any agent with no section of its own.

Install the skills with the command above. If your agent has no skill mechanism at all, read
the skill files directly from the `titlize/skills` repository and follow them as instructions.

---

## 2. Register the Titlize MCP server

Titlize ships an MCP server as a published npm package, `@image-titler/mcp-connector`. It runs
over stdio via `npx`; there is no remote endpoint to authenticate against. It exposes two
tools: generate an image, and check the usage quota.

It needs two environment values:

| Variable | Value |
|---|---|
| `IMAGE_TITLER_API_TOKEN` | the user's own token — see step 3 |
| `IMAGE_TITLER_BASE_URL` | `https://api.titlize.com` |

### Claude Code

```bash
claude mcp add titlize --env IMAGE_TITLER_API_TOKEN=$TITLIZE_API_TOKEN --env IMAGE_TITLER_BASE_URL=https://api.titlize.com -- npx -y @image-titler/mcp-connector
```

### Codex

```bash
codex mcp add titlize -- npx -y @image-titler/mcp-connector
```

Then set the two environment values in the entry Codex just wrote.

### Cursor, Windsurf, OpenCode, GitHub Copilot, and all other agents

These configure MCP servers through a config file rather than a CLI. Add this entry to your
agent's MCP configuration, under whatever key it uses for servers:

```json
{
  "titlize": {
    "command": "npx",
    "args": ["-y", "@image-titler/mcp-connector"],
    "env": {
      "IMAGE_TITLER_API_TOKEN": "the token from step 3",
      "IMAGE_TITLER_BASE_URL": "https://api.titlize.com"
    }
  }
}
```

---

## 3. Get the user's API token

Titlize does not issue tokens to agents, and this document does not contain one. The user
creates their own.

Ask the user to:

1. **If they do not have a Titlize account yet**, register at
   `https://titlize.com/auth/signup`. It is free. Registration is on the main site — the
   dashboard has no sign-up page, so do not send a new user straight there.
2. Sign in to the dashboard at `https://app.titlize.com`.
3. Open the API tokens page and create a token.
4. Paste it back to you.

Then put that value in `IMAGE_TITLER_API_TOKEN` using whichever mechanism your agent uses for
secrets. Prefer an environment variable or your agent's secret store over writing it into a
config file that might be committed. Never echo the token back in full, and never send it
anywhere other than Titlize.

Wait for the user to give you the token. Do not invent one, do not reuse a token from another
project, and do not skip ahead to step 4 without it.

---

## 4. Verify by generating one image

Do not report success until you have actually generated something.

Using the Titlize tools you just registered, generate one image: any background image the user
has to hand, with a short headline such as "Hello from Titlize". Then show the user the
resulting image URL and tell them the setup is complete.

If the generation fails, tell the user what the error was. Two common causes worth checking
before you report:

- an invalid or mistyped token — the API will reject it;
- a free-tier quota that is already used up for the month.

Once that image comes back, the setup works and the user can ask for Open Graph images in
plain language from now on.

What you still have to do yourself#

One thing: create your API token. Titlize does not issue tokens to agents, and the prompt above contains none. Your agent will ask you for one, and you paste it back.

If you already have an account, create the token in the dashboard at app.titlize.com (opens in new tab). If you do not, sign up first — registration is on this site, not on the dashboard.

Which agents this works with#

Every agent listed in the prompt has its own setup section, and each one says whether Titlize has actually run it end to end or whether the instructions were written from that agent's documentation. Check the label for yours before relying on it — if a section is marked best-effort and it does not work, that is worth telling us about.

Agents with no section of their own are covered by the generic fallback, which uses the same skills repository and a hand-edited MCP config entry.

If something goes wrong#

The prompt tells your agent to stop at the first failing step and report what broke, rather than pressing on and leaving you with a half-configured setup that looks finished. So if your agent says a step failed, that is the design working — send us the step and the error.