Repository navigation
v1.2.0
A comparison with Ideogram's own MCP server and the current API (docs/COMPETITION-2026-10-01.md).
Added
- Style controls on
ideogram_generate(3.0),ideogram_editandideogram_remix:style_reference_images(1-3 files),
character_reference_imagewith an optionalcharacter_reference_mask,style_codes(1-8),style_presetand
color_palette(a preset name or 1-10 explicit colours with weights, never both) on all three; an exactresolution
(one of the 69 sizes, not withaspect_ratio) on generate and remix;custom_model_uriand
enable_copyright_detectionon generate — each endpoint gets exactly the parameters its documentation lists, sent
under the API's field names (a list as repeated fields, the palette as oneapplication/jsonpart as the OpenAPI
spec declares — a live probe on 2026-10-01 accepted it; the tests stubfetch). The three tools' input schemas
are strict: a parameter an endpoint does not take (an exactresolutionon edit) is refused by name, never
silently dropped. Every file
counts against the 50 MB request limit, checked withstatbefore any file is read. Tests pin the encoding, the
per-endpoint fields and the refusals on all three endpoints. ideogram_generatewithmodel: "4.0"posts to/v1/ideogram-v4/generate(text_prompt,resolution,
rendering_speedexceptFLASH,enable_copyright_detection); a 3.0-only parameter given with 4.0 is refused by
name, never dropped. A live probe on 2026-10-01 returned the documented shape (response_type,created,
data[].url/prompt/resolution/is_image_safe/seed), which the response schema accepts.
Changed
- README and
docs/API-REFERENCE.mdsaid "Ideogram 4.x uses the v2 API": the v1 API has theideogram-v4endpoints too.
The v2 API (Ideogram 4.5, Precise Edit, async jobs, usage) is still not called.