MCP server
Connect Imagifly to any agent that speaks the Model Context Protocol.
Imagifly runs a remote MCP server at:
https://imagifly.net/api/mcpIt uses Streamable HTTP transport, authenticates with the same API key as the HTTP API, and exposes six tools. Any MCP client that supports remote HTTP servers can connect; this section walks through the clients we test.
Tools
| Tool | What it does |
|---|---|
list_image_models | Image model catalog with credit prices and limits. |
generate_image | Submit a text-to-image task (optional reference images, ratio, quality, resolution, steps). |
get_image_generation | Poll an image task and read its image URLs. |
list_video_models | Video model catalog with sizes, durations and supported workflows. |
generate_video | Submit a text-to-video, reference-to-video or first/last-frame task. |
get_video_generation | Poll a video task and read its video URLs. |
Tool calls are thin wrappers over the HTTP API: same models, same credits, same error codes. Generation is still asynchronous, so an agent typically calls generate_* once and get_* until the task finishes.
Authentication
Pass the key in a header on every request:
Authorization: Bearer imf_your_key_herex-api-key: imf_your_key_here is also accepted. Create the key in the API console.
Manual configuration
Most clients accept the same JSON fragment:
{
"mcpServers": {
"imagifly": {
"type": "http",
"url": "https://imagifly.net/api/mcp",
"headers": {
"Authorization": "Bearer imf_your_key_here"
}
}
}
}Prefer environment interpolation where the client supports it (${IMAGIFLY_API_KEY} or ${env:IMAGIFLY_API_KEY}) so the key is not written to disk.
Pick your client
Claude Code
Codex
OpenClaw
WorkBuddy
Cursor
Verify the connection
Ask the agent to list its tools. A healthy connection shows the six imagifly tools above. If the client reports the server as connected but lists no tools, the request is usually unauthenticated — check that the header is sent exactly as Authorization: Bearer imf_....