LLM Integration Guide
Make AI assistants aware of Inliner.ai, then give them live generation, editing, and project tools.
Machine-Readable Files
Following the llms.txt standard, we provide these files for AI systems:
llms.txt
Concise summary of Inliner.ai for quick LLM reference. Contains URL format, quick start, and essential links.
View /llms.txtllms-full.txt
Comprehensive documentation including all integration methods, MCP tools, pricing, and complete code examples.
View /llms-full.txtAgent-Aware Installation
Inliner uses two complementary layers. The inliner-ai skill/plugin teaches the model when to activate Inliner and which workflow is safe. @inliner/mcp-server provides the 12 live tools and publishes the same tool-selection guidance during initialization.
@inliner/agent-skill v1.3.0 and @inliner/mcp-server v1.1.1.
OpenAI Codex — skill and MCP together
Terminal
codex plugin marketplace add inliner-ai/agent-skill --ref v1.3.0
codex plugin add inliner-ai@inliner-ai
Gemini CLI extension
Terminal
gemini extensions install https://github.com/inliner-ai/agent-skill
Claude Code and other skill-compatible agents can install skills/inliner-ai from the canonical agent-skill repository. Cursor users can install the dedicated Inliner Cursor plugin.
URL Format
The core concept: use stable project image URLs in your code, with authenticated tools creating first renders for account-owned namespaces.
URL Structure
https://img.inliner.ai/{project}/{description}_{width}x{height}.{format}
Example:
https://img.inliner.ai/demo/happy-dog-playing-fetch_800x600.png
Integration Methods
- Direct URL — Use generated CDN URLs directly in HTML/CSS
- Agent Skill / Plugin — Teach Codex, Claude, Gemini, Cursor, and compatible agents when and how to use Inliner
- MCP Server — For Codex, Claude Code, Cursor, Copilot, Gemini CLI, and Windsurf
- CLI —
npx @inliner/cli "sunset-beach-palm-trees_1200x600.png" - REST API — Programmatic access via api.inliner.ai
Edit vs Generate Modality
For image changes, route to edit workflows with source context. Requests like "make it 600x600" can be interpreted as new generation if no source URL/path is provided.
- Edit existing image: Use
edit_image(MCP) orinliner-ai edit ...(CLI) with explicit source - Generate new image: Use
generate_image(MCP) orinliner-ai generate ...(CLI), and wait for the completed asset before insertion - Recommend URL only: Use
recommend_image_url; it does not generate an asset - If ambiguous: Ask whether to edit the previous image or create a new one
Cursor MCP Config (Recommended)
.cursor/mcp.json
{
"mcpServers": {
"inliner": {
"command": "npx",
"args": ["-y", "@inliner/mcp-server"],
"env": {
"INLINER_API_KEY": "${INLINER_API_KEY}",
"INLINER_DEFAULT_PROJECT": "your-project-namespace"
}
}
}
}
Project-Specific Instructions
Users can get customized LLM instructions for their specific projects:
- Log into the Inliner dashboard
- Go to Projects
- Click LLM Instructions on any project
- Copy instructions optimized for Claude, Cursor, ChatGPT, etc.
These instructions include the user's namespace, custom prompts, and reference images.