MCP for agents

Give an AI agent the ability to transform images. TransformKit ships a Model Context Protocol server, so any MCP-capable client — Claude, Cursor, or your own agent — can call it as a tool.

Connect a client

The server speaks stateless Streamable HTTP at a single endpoint. Add the URL to your MCP client and connect — a browser opens to sign in via OAuth, so there is no API key to paste. Manage access from Credentials.

mcp endpoint

Run this once, then run claude /mcp, pick transform-kit, and authenticate via OAuth.

 
claude mcp add --transport http transform-kit ""

Prefer an API key?

Clients without OAuth can send a TransformKit key as a bearer header instead — the credential is verified identically. Under OAuth, the endpoint advertises /.well-known/oauth-protected-resource and a 401 carries a WWW-Authenticate challenge for automatic discovery.
bearer-key config
{
  "mcpServers": {
    "transform-kit": {
      "url": "",
      "headers": {
        "Authorization": "Bearer tk_your_key_here"
      }
    }
  }
}

Tools

The server exposes two tools:

  • whoami — the authenticated account and key. Unmetered. No parameters.
  • health — checks the API is reachable. No auth, unmetered.
Media transforms aren't exposed as MCP tools yet — they run through the SDK, which orchestrates upload → pipeline → signed URL. These tools cover identity and health so an agent can confirm its connection.

Verify from the terminal

The endpoint is plain HTTP, so you can smoke-test it with curl before wiring up a client.

curl -s -X POST "" \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list"
  }'