The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the NovelAI Image MCP listing page.
An MCP (Model Context Protocol) server that exposes NovelAI image generation as tools for AI agents (Claude Desktop, Cline, custom agents, remote clients).
Built on FastMCP 4 (the fastmcp framework over the MCP SDK v2 mcp>=2.0.0), it lets an agent generate
images (txt2img / img2img / inpaint), upscale, run Director tools (line art,
emotion, background removal, …), annotate with ControlNet, suggest tags, encode
vibes, and query account subscription — all through the standard MCP tool
interface.
📖 Documentation: xinvxueyuan.github.io/NovelAI-Image-MCP
Image content blocks (the agent sees the image)
and PNG saved to disk (path returned as text).typer CLI for direct invocation.This is a uv + pnpm monorepo:
See CONTRIBUTING.md for the developer guide and
apps/docs/source/ for the full documentation source.
If you plan to contribute, install the cross-cutting Node toolchain (turbo, husky, markdownlint) via pnpm:
This wires the husky pre-commit + commit-msg hooks and gives you turbo /
markdownlint-cli2 for local development. The MCP server has zero Node
runtime dependencies — this step is only for contributors.
The MCP server supports two transports (stdio + http), all configured under
mcpServers:
claude_desktop_config.json:
Set NOVELAI_TOKEN (or NOVELAI_USERNAME + NOVELAI_PASSWORD) in the host
environment before launching — uvx inherits the parent shell env.
After docker compose up --build (server listens on http://HOST:8000/mcp):
Replace http://127.0.0.1:8000/mcp with your self-deployed endpoint (e.g.
https://mcp.example.com/mcp behind a TLS-terminating reverse proxy). Swap
the literal token placeholder for a host-managed secret reference if your
MCP host supports one (Claude Desktop, Cline, etc. expose this via their
own secrets UI).
The project ships three skills.sh packages that teach AI agents (Claude Code, Codex, GitHub Copilot, Cursor, …) how to drive the CLI and MCP tools without you pasting docs:
| Skill | What it teaches |
|---|---|
novelai-cli | Typer CLI commands (serve, generate, upscale, director, annotate, info) for shell scripting |
novelai-mcp-tools | The 11 MCP tools — model selection, parameters, return shape, Anlas cost |
novelai-workflows | Multi-step creative pipelines (txt2img→upscale, annotate→img2img, Director edits) |
Skills and the CLI/MCP tools are complementary — install all three and your agent picks the right mode based on context. See the Agent skills docs for details.
| Tool | Description |
|---|---|
generate_image | Text-to-image (V3 / V4 / V4.5 / V5 models, character prompts; vibes V4/V4.5 only) |
image_to_image | Image-to-image with strength/noise |
inpaint | Inpainting (requires an inpaint model + mask) |
upscale_image | 2× / 4× upscale |
director_tool | Line art / sketch / bg-removal / declutter / colorize / emotion |
annotate_image | ControlNet annotation (hed, midas, scribble, mlsd, uniformer) |
suggest_tags | Prompt tag suggestions |
encode_vibe | Encode a reference image into a vibe token |
get_subscription | Account subscription + Anlas balance |
get_user_data | Account user data |
estimate_anlas_cost | Estimate Anlas cost for a generation (no API call) |
See the tools reference on the docs site for parameters and examples.
All settings are environment variables (see .env.example). Key ones:
| Variable | Default | Notes |
|---|---|---|
NOVELAI_TOKEN | — | Persistent API token (preferred auth) |
NOVELAI_USERNAME / NOVELAI_PASSWORD | — | Access-key login (argon2id) |
NOVELAI_OUTPUT_DIR | outputs | Where generated PNGs are saved |
MCP_TRANSPORT | stdio | stdio or streamable-http |
MCP_HOST / MCP_PORT | 127.0.0.1 / 8000 | For streamable-http |
NovelAI API reference: image.novelai.net/docs
The project is a uv + pnpm monorepo orchestrated by Turbo. See
CONTRIBUTING.md for the full setup; the short version:
Per-member commands (via uv):
The Dockerfile lives at apps/server/Dockerfile but
the build context is the repository root (so uv can resolve the workspace
graph). See docker-compose.yml.
The Sphinx documentation site is built with Furo + MyST Markdown and
auto-deploys to GitHub Pages on every push to main:
apps/docs/source/pnpm docs:serveMIT — see LICENSE. Per-file SPDX annotations live in
REUSE.toml. Contributions are subject to the
Developer Certificate of Origin (the commit-msg hook signs off
commits automatically).