apexapi-mcp

MCP server for ApexApi — call 120+ AI models (OpenAI, Anthropic, Google, DeepSeek, Qwen…) and read the live web (scrape / crawl / structured extract) from any MCP client, with one ak- API key and one prepaid balance.

Tools

chat, list_models, get_balance, scrape_page, crawl_site, extract_structured, check_job, generate_image, generate_speech, generate_video, list_generations, list_uploads, create_upload_url

• generate_image ends its output with a cost_usd: X line: the exact amount charged.
• check_job polls crawl, extract, video, studio and image (async POST /v1/images/jobs) jobs.
• create_upload_url returns a presigned URL: PUT the file bytes to it (for example with curl), then use the returned public_url as a reference. It works on the remote server too. The stdio server additionally has upload_reference, which takes a local file path.

Marketing Studio (turn a product into a video ad): browse the curated preset, hook and setting catalog, reuse or register a product and avatar, see the exact prompt and price for free, then render. The server fills the prompt and routes to the right video model with transparent predicted and actual USD.

1. studio_catalog: presets, hooks, settings (free)
2. studio_list_assets: your products plus stock and own avatars (free), or studio_register_product / studio_register_avatar
3. studio_preview: composed prompt, model, duration and predicted_usd (free, nothing rendered)
4. optional studio_expand_prompt: a shot-by-shot director script (one small billed chat call), to edit and pass as final_prompt
5. studio_generate: render (accepts reference_images, final_prompt, project_id), then poll check_job { kind: "studio", id }

Local (stdio)

Get a key at https://apexapi.dev/keys, then add to your MCP client config:

{
  "mcpServers": {
    "apexapi": {
      "command": "npx",
      "args": ["-y", "apexapi-mcp"],
      "env": { "APEXAPI_API_KEY": "ak-..." }
    }
  }
}

Claude Code: claude mcp add --scope user apexapi -e APEXAPI_API_KEY=ak-... -- npx -y apexapi-mcp

(--scope user registers the server for your whole machine. Without it Claude Code uses local scope, which only applies to the current directory.)

Remote (Streamable HTTP)

Endpoint: https://api.apexapi.dev/mcp with header Authorization: Bearer ak-...

Responses use MCP Streamable HTTP framing (SSE) — clients like Claude Code handle this natively; it is not a plain-JSON REST endpoint.

Claude Code: claude mcp add --transport http --scope user apexapi https://api.apexapi.dev/mcp --header "Authorization: Bearer ak-..."

Docs

https://apexapi.dev/docs/mcp