NovelAI Image MCP


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 the official MCP Python SDK v2 (MCPServer), 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: https://xinvxueyuan.github.io/NovelAI-Image-MCP/
Features
- 11 MCP tools covering the full NovelAI image API surface.
- Two transports: stdio (local agents) + streamable-http (remote / multi-client).
- Dual image return: base64
Image content blocks (the agent sees the image)
and PNG saved to disk (path returned as text).
- Async + sync: async tool handlers + a
typer CLI for direct invocation.
- Monorepo: uv workspace (Python) + pnpm workspace (Node tooling) orchestrated
by Turbo; MIT-licensed, Docker-ready, GitHub Pages docs.
Repository layout
This is a uv + pnpm monorepo:
NovelAI-Image-MCP/
├── apps/
│ ├── server/ # MCP server (the installable PyPI package)
│ │ ├── src/novelai_image_mcp/ # 11 MCP tools + NovelAI HTTP client
│ │ ├── tests/
│ │ ├── docker/ # smoke-test entrypoint
│ │ ├── Dockerfile # built with repo root as context
│ │ └── pyproject.toml # ruff / pyright / pytest config
│ └── docs/ # Sphinx documentation site
│ ├── source/ # MyST Markdown + conf.py
│ ├── Makefile
│ └── pyproject.toml
├── .github/ # workflows, CODEOWNERS, issue templates
├── pyproject.toml # uv workspace root (virtual)
├── uv.lock # single shared lockfile
├── pnpm-workspace.yaml # pnpm workspace declaration
├── pnpm-lock.yaml # Node toolchain lockfile
├── turbo.json # cross-workspace task graph
├── package.json # root scripts + dev toolchain
└── docker-compose.yml # local container orchestration
See CONTRIBUTING.md for the developer guide and
apps/docs/source/ for the full documentation source.
Quick start
Install from source (development)
git clone https://github.com/xinvxueyuan/NovelAI-Image-MCP.git
cd NovelAI-Image-MCP
uv sync
cp .env.example .env
uv run python -m novelai_image_mcp serve
MCP_TRANSPORT=streamable-http uv run python -m novelai_image_mcp serve
Install from PyPI (runtime only)
pip install novelai-image-mcp
export NOVELAI_TOKEN=pst-...
novelai-image-mcp serve
If you plan to contribute, install the cross-cutting Node toolchain (turbo,
husky, markdownlint) via pnpm:
corepack enable pnpm
pnpm install --frozen-lockfile
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.
Connect an agent
The MCP server supports two transports (stdio + http), all configured under
mcpServers:
stdio (local agent — Claude Desktop / Cline)
claude_desktop_config.json:
{
"mcpServers": {
"novelai-image": {
"type": "stdio",
"command": "uv",
"args": [
"run",
"--directory",
"/path/to/NovelAI-Image-MCP",
"python",
"-m",
"novelai_image_mcp",
"serve"
],
"env": {
"NOVELAI_TOKEN": "${input:novelai_token}"
}
}
}
}
Alternative: uvx (published package)
{
"mcpServers": {
"novelai-image": {
"command": "uvx",
"args": ["--prerelease=allow", "novelai-image-mcp", "serve"],
"env": { "NOVELAI_TOKEN": "pst-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" }
}
}
}
Set NOVELAI_TOKEN (or NOVELAI_USERNAME + NOVELAI_PASSWORD) in the host
environment before launching — uvx inherits the parent shell env.
http (remote / Docker deployment)
After docker compose up --build (server listens on http://HOST:8000/mcp):
{
"mcpServers": {
"novelai-image-http": {
"type": "http",
"url": "http://127.0.0.1:8000/mcp",
"headers": {
"Authorization": "Bearer pst-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
}
}
}
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).
CLI (sync, for scripting)
uv run python -m novelai_image_mcp generate --prompt "a cat, masterpiece" --width 832 --height 1216
uv run python -m novelai_image_mcp upscale --image ./in.png --factor 4
uv run python -m novelai_image_mcp info
uv run python -m novelai_image_mcp --help
| Tool | Description |
|---|
generate_image | Text-to-image (V3 / V4 / V4.5 models, character prompts, vibes) |
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.
Configuration
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: https://image.novelai.net/docs/index.html
Development
The project is a uv + pnpm monorepo orchestrated by Turbo. See
CONTRIBUTING.md for the full setup; the short version:
uv sync
pnpm install --frozen-lockfile
pnpm check
pnpm docs:build
pnpm server:serve
pnpm docs:serve
Per-member commands (via uv):
uv run --directory apps/server ruff check src tests
uv run --directory apps/server -m pyright
uv run --directory apps/server -m pytest
Docker
docker compose up --build
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.
Documentation
The Sphinx documentation site is built with Furo + MyST Markdown and
auto-deploys to GitHub Pages on every push to main:
License
MIT — 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).