Rushie over MCP

Connect Claude, Cursor or any MCP client with one URL and a sign-in: search, license and commission pictures on your credits.

Rushie is a remote Model Context Protocol server. Point an agent at it and the agent can search the catalogue, license a picture and commission one that does not exist yet — and the account behind the key earns a share of every sale of what it commissioned.

Connect in a minute

The address is all a client needs: https://rushie.ai/mcp. It opens a Rushie sign-in window, you sign in with Google or your phone and press Allow, and it is connected to your account. New accounts start with 10 free credits. No key to copy, and you can disconnect the app from your account page at any time.

Claude

Settings → Connectors → Add custom connector, name it Rushie, paste the address, press Connect.

Claude Code

claude mcp add --transport http rushie https://rushie.ai/mcp
# then, inside Claude Code:  /mcp  →  rushie  →  Authenticate

Cursor, VS Code, Windsurf and other clients that take a URL

{
  "mcpServers": {
    "rushie": { "url": "https://rushie.ai/mcp" }
  }
}

Scripts and clients without a browser

Create an API key under Developer access on your account and send it as a bearer token:

curl https://rushie.ai/mcp \
  -H "Authorization: Bearer rsh_..." \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Then ask for a picture in plain words. A good agent searches first, commissions only when nothing fits, and licenses what you pick.

The picture desk

Every image API an agent can use today answers here are some results, and leaves the agent to judge them, generate when nothing fits, clear the licence, cut the picture for each placement and write the alt text. Rushie does all five in one call.

get_picture({
  "subject": "a beekeeper lifting a honeycomb frame at dawn",
  "sizes": ["hero", "og", "square"],
  "max_credits": 15
})

→ {
  "source": "catalogue",            // or "made for you"
  "files": [
    {"placement": "hero",   "width": 1920, "height": 1080, "url": "https://rushie.ai/api/bank/download/…?fit=1920x1080"},
    {"placement": "og",     "width": 1200, "height": 630,  "url": "…"},
    {"placement": "square", "width": 1080, "height": 1080, "url": "…"}
  ],
  "alt_text": "A beekeeper in a veil lifting a frame of capped honeycomb …",
  "license": {"type": "standard", "perpetual": true,
              "verify_url": "https://rushie.ai/api/bank/licence/lic_…"},
  "credits_spent": 0
}

• Never a near-miss. A catalogue picture is used only when it is relevant and carries what was asked for. “A zeppelin over a harbour” does not come back as a harbour. When nothing is right, it is made.
• Never over budget. Making and licensing together stay within max_credits; if that is not enough it says exactly how much is, and spends nothing.
• Cut around the subject. Each size is cropped where the detail is, so a portrait’s face survives a 16:9 hero. One licence covers every size.
• Proof, not a PDF. The licence has a public URL anyone can check: what it grants, on which picture, since when, and that the picture is AI-generated. Never the buyer or the price.
• Nothing charged twice. A render that outlives the call returns a request_id; calling again with it collects the picture. A render that fails is refunded.

illustrate does the same for a whole draft: it reads an article or page, picks the moments that most need a picture, says what each should show, which already exist and what making the rest costs — and with fill_gaps it starts making them.

Tools

Every tool carries MCP annotations — read-only, idempotent, open-world — so a client can ask for confirmation only where something is spent.

Credits

One credit is one US dollar of list price. A commission costs a flat 2 credits for the GPU time; a licence costs its price (a standard image is 9). A spend is checked and written in one locked transaction, so two calls racing for the last credit cannot both win, and a commission that is refused or fails is refunded automatically. While a catalogue runs with free licensing, licences cost nothing in credits either.

Who can call what

Studio tools are not merely refused to anyone else — they are not listed. Keys are stored only as a SHA-256 digest, can be revoked from the account page at any time, and a revoked key is treated as no key at once.

Protocol

• Streamable HTTP, stateless: POST https://rushie.ai/mcp with JSON-RPC 2.0. Batches are accepted.
• Protocol version negotiated at initialize; the reply carries MCP-Protocol-Version.
• OAuth 2.1 with PKCE (S256 only): protected-resource metadata (RFC 9728) at /.well-known/oauth-protected-resource, authorization-server metadata (RFC 8414) at /.well-known/oauth-authorization-server, dynamic client registration (RFC 7591) and Client ID Metadata Documents, resource indicators (RFC 8707), rotating refresh tokens with replay detection, and revocation (RFC 7009).
• Tool results carry structuredContent alongside text, for clients that read either.
• Agents with a wallet can pay per call instead of holding credits: see agent payments.