Which clients work with the MCP server?

Anything that speaks MCP — Claude Desktop, Cursor, Cline, and orchestration tools like n8n. It's JSON-RPC 2.0 over HTTP, so a custom client is a few lines too.

Does the MCP server use the same key as REST?

Yes. One pk_live_ key works for the MCP server and for direct REST calls, and it meters against the same plan. Get one free in the dashboard.

How are MCP calls billed?

Like REST: generate_image costs one credit per image, billed on delivery, and the exact cost comes back to the client. Discovery (initialize, tools/list) and list_templates are free.

AI agents & MCP · propzapi

AI agents & MCP

Give your agent image generation

Two ways to give an agent access: install the skill, or connect the hosted MCP server. Either way you get the same tools and the same key, and it works with Claude, Cursor, Cline or anything else that speaks MCP. generate_image hands the agent the actual picture, not just a link.

Get your API key REST docs

Option A · the agent skill

Install the skill

Installs the tools straight into your agent from the public propzapi-skills repo. Pure Python standard library — no dependencies. Set your key first:

export PROPZAPI_KEY=pk_live_…

# Claude Code, Cursor, Cline — the `skills` CLI, straight from GitHub
npx skills add paperandbeyond23-gif/propzapi-skills --all

# OpenClaw / ClawHub
openclaw skills install @paperandbeyond23-gif/propzapi-full

The skill wraps the same image tools as the MCP server. Browse it on ClawHub.

Option B · hosted MCP server

Connect in one config

A remote MCP server speaking JSON-RPC 2.0 over HTTP. Drop this into your client's MCP config (Claude Desktop, Cursor, Cline) and swap in your key:

{
  "mcpServers": {
    "propzapi": {
      "url": "https://api.propzapi.com/mcp",
      "headers": { "X-API-Key": "pk_live_…" }
    }
  }
}

Endpoint — https://api.propzapi.com/mcp

Transport — streamable HTTP (JSON-RPC 2.0)

Auth — X-API-Key: pk_live_…

Discovery (initialize, tools/list) is open and free. Your key is required on tools/call and meters against your plan exactly like the REST API.

The toolbox

Two tools

Tool	Returns
`generate_image`	Renders a template with your data and returns the image itself, plus its URL. One credit.
`list_templates`	Built-in templates and your own, with each one's variables. Free.

In practice

Example prompts

"Make an OG image for this blog post and give me the URL."

generate_image

"Which of my templates can I use, and what fields do they take?"

list_templates

"Render a square quote card with this line and the author, in our brand green."

generate_image

Discovery

Everything an agent needs to self-describe

MCP server card — https://api.propzapi.com/.well-known/mcp/server-card.json

OpenAPI spec — https://api.propzapi.com/openapi.json

Plain-text brief for models — /llms.txt

One pk_live_ key works for the MCP server and direct REST calls alike. Get one free in the dashboard.

Get your API key See pricing

FAQ

Common questions

Which clients work with the MCP server?: Anything that speaks MCP — Claude Desktop, Cursor, Cline, and orchestration tools like n8n. It's JSON-RPC 2.0 over HTTP, so a custom client is a few lines too.
Does the MCP server use the same key as REST?: Yes. One pk_live_ key works for the MCP server and for direct REST calls, and it meters against the same plan. Get one free in the dashboard.
How are MCP calls billed?: Like REST: generate_image costs one credit per image, billed on delivery, and the exact cost comes back to the client. Discovery (initialize, tools/list) and list_templates are free.