Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Krita Codex MCP
Overview
Description from the maker (original English)
Control Krita through a secure local MCP server and authenticated Windows bridge.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- PyPIPython’s uv installed (for the uvx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"krita-codex": {
"command": "uvx",
"args": [
"krita-codex-mcp"
]
}
}
}Run this in your terminal
claude mcp add krita-codex -- uvx krita-codex-mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"krita-codex": {
"command": "uvx",
"args": [
"krita-codex-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"krita-codex": {
"type": "stdio",
"command": "uvx",
"args": [
"krita-codex-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account cyyprezz, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32709 servers in this category
- Published to the registry more recently than 18% of the other 32709 servers in this category
- Basic checks equal to or better than 100% of the other 32709 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Krita Codex MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 4 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, SwarmMemo
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated 2 days ago
Install
SwarmMemo
by Hugo0
Talk with agent swarms: rooms, private messages and paid tasks for AI agents
Runs in the cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Krita Codex MCP Server
Control Krita from OpenAI Codex through a secure local Model Context Protocol (MCP) server for Windows and Linux.
PyPI package · GitHub releases · Windows installation guide · Linux installation guide · Codex and MCP compatibility
A local MCP server that lets Codex inspect and control Krita through a small, authenticated bridge. The MCP process uses STDIO. The Krita Python plugin listens only on 127.0.0.1, validates a shared bearer token, and dispatches every Krita API call to Qt's main thread.
Windows is the original supported platform; Linux support is experimental. Both platforms use a capability-based runtime compatibility check. Krita 5.3.2.1 on Windows is a tested build, not a hard version requirement. The server deliberately exposes a small set of cohesive tools instead of a large collection of micro-tools:
| Tool | Purpose |
|---|---|
krita_state | Active document, canvas/color space, recursive layer tree with UUIDs, active layer and current painting state |
krita_preview | Whole-canvas or pixel-precise cropped PNG returned directly as MCP image content |
krita_canvas | Sample colors; resize, scale, crop, rotate or flip; import editable raster layers |
krita_edit | Create/refine/move selections; native copy, cut, paste, selection-to-layer, fill and clear |
krita_document | Inspect runtime compatibility; list, create, open, activate, save and close documents |
krita_layers | Read/edit the layer tree, safely reparent, and transform layers by stable UUID |
krita_history | Read undo/redo state and execute bounded undo or redo steps |
krita_brush | Read/set native brush state and search installed Krita presets |
krita_paint_path | Pressure-aware line segments through Krita's native Node.paintLine API and active brush preset |
krita_draw | Native preset-backed lines, open/closed paths, polygons, rectangles and ellipses |
krita_color | KRA-backed project palettes, Krita palette swatches, color replacement and safe correction filters |
krita_asset | Export layer PNGs plus Unity-oriented animation, tileset and named-region packages with direct previews |
krita_save_export | Save KRA and export PNG beneath configured roots only |
Codex -> local STDIO MCP process -> authenticated 127.0.0.1 HTTP bridge-> queued, timeout-aware Qt main-thread dispatch -> Krita Python API
The bridge has no arbitrary Python execution tool and no direct pixel painting fallback. Actual painting, shapes, replacement fills and correction filters go through native Krita actions or stroke APIs. If the running Krita build lacks a feature, krita_state and krita_document(action="compatibility") report the affected tools. Calling that feature returns a structured error; the bridge never silently switches to a different rendering backend.
Quick start
Choose the installation source for your platform:
| Platform | Installation source | Validation |
|---|---|---|
| Windows | PyPI 0.2.2 or a checkout | Windows CI; original live testing with Krita 5.3.2.1 |
| Linux | PyPI 0.2.2 or a checkout | Linux CI; contributor live test on Debian 13 / Krita 5.2.9 in limited mode |
Version 0.2.2 includes the Linux/XDG path and private-configuration fixes. Keep the installer, Krita plugin and Codex server on that same exact version; the marketplace launcher also pins it. Other Linux distributions and Krita builds require their own live preflight.
A first-time setup has two separate parts: the local bridge must be installed and enabled in Krita, then Codex must be connected through either the marketplace plugin or a direct MCP configuration. The codex plugin commands do not install or enable anything in Krita.
Krita must include Python scripting, pass the live compatibility check, and have uv/uvx on PATH. Run the MCP process on the same computer as Krita. Local Codex CLI, IDE and supported desktop clients use local MCP configuration; a hosted ChatGPT web chat cannot connect through this computer's 127.0.0.1 bridge by adding this GitHub repository.
Windows: published package
- Close Krita, make sure the allowed directory already exists, and install the current release from PyPI:
uvx --from "krita-codex-mcp==0.2.2" `krita-codex-install install ` --allowed-root "C:\Krita Work"
- In Krita, open Settings > Configure Krita > Python Plugin Manager and enable Krita Codex Bridge.
- Close and reopen Krita so the installed plugin and shared protocol package are loaded together.
- Run the same version's live check:
uvx --from "krita-codex-mcp==0.2.2" krita-codex-install check- Require either
Ready for productive use.or the explicit limited-mode success message. - Choose exactly one Codex connection method below: the marketplace plugin or the direct MCP configuration.
Linux: PyPI package
Close Krita, create a narrow allowed directory and install from PyPI:
mkdir -p "$HOME/krita-codex-work"uvx --from "krita-codex-mcp==0.2.2" krita-codex-install install --allowed-root "$HOME/krita-codex-work"
Enable Krita Codex Bridge in Krita's Python Plugin Manager, close and reopen Krita, then run:
uvx --from "krita-codex-mcp==0.2.2" krita-codex-install checkAccept compatible or explicitly reported limited mode. Follow the Linux guide's Codex setup for either connection method. The installer uses XDG directories and keeps its token configuration private. No sudo is needed.
Install the Codex plugin from GitHub
The repository includes a public, local-first Codex plugin. It bundles the guided krita-control skill and starts the version-pinned PyPI MCP server through uvx; Krita and the authenticated bridge continue to run only on the user's machine. Run these commands only after the Krita bridge has been installed, enabled, restarted, and checked as described above. They register the GitHub marketplace and install the Codex bundle; they do not modify the Krita installation or enable its Python plugin.
codex plugin marketplace add cyyprezz/krita-codex-mcpcodex plugin add krita-codex-mcp@krita-codex
Start a new Codex task after installation, then verify krita_state and krita_preview. Plugin users should not also add a separate [mcp_servers.krita] block because the plugin already provides that server. For later repository releases, run codex plugin marketplace upgrade krita-codex, rerun codex plugin add krita-codex-mcp@krita-codex, and start another new Codex task.
Configure the MCP server directly
For either platform, use this alternative only after the Krita bridge has passed the live check. Preview the checkout-free, exactly version-pinned uvx Codex block with krita-codex-install codex-config. Apply it only after explicit confirmation, restart Codex, verify krita_state and krita_preview, and only then start normal work.
Install and update never close Krita. If the authenticated bridge is running, replacement is rejected before any installed files are changed and Krita must be closed manually. A busy local bridge port also stops the installer before replacement begins.
For a personal installation, use the user-level ~/.codex/config.toml on Linux or C:\Users\ \.codex\config.toml on Windows. This is the recommended option because the server is then available to all local Codex tasks and Git worktrees. The generated block uses uvx, has no checkout cwd, and pins the same exact distribution version as the installed plugin. The installer only changes that file after showing the full preview and receiving explicit confirmation. Unmarked or conflicting Krita entries are never overwritten. Never commit personal configuration. See the Windows installation guide for details.
The generated launcher and marketplace configuration explicitly forward custom XDG directories. Codex and Krita must inherit the same values. For unreleased source changes, use the checkout-specific alternative in the Linux guide.
Current Codex and MCP compatibility
The compatibility check uses Codex CLI 0.163.0 (released 2026-10-15) against the built wheel and checks discovery of all 13 tools without an API key, model request or running Krita. See the compatibility notes for its exact scope.
This server intentionally stays on the MCP Python SDK 1.x maintenance line (mcp<2). Current Codex retains the legacy STDIO handshake used by this SDK. The newer MCP 2026-07-28 protocol and portable plugin format do not by themselves require replacing this working local integration. The existing Codex plugin manifest remains a supported compatibility format; full support for newer MCP protocol features would be a separate, tested SDK migration.
The preflight checks local configuration, the complete installed hash manifest, wheel/plugin/ protocol versions, loopback port, authentication and the running Krita capability profile. The running plugin reports the distribution, protocol and Krita versions without adding an MCP tool. The check creates a disposable document, verifies a new paint layer, native drawing, Undo/Redo, transactional reparenting, direct PNG preview bytes and temporary KRA/PNG output beneath an allowed root. It restores the previously active document and removes every temporary file.
An unknown Krita version is accepted when all critical capabilities pass. Missing optional features produce limited warnings naming the affected MCP tools; missing projection, persistence, stable layer-tree or document-lifecycle APIs remain critical. The same structured report is available to Codex through krita_state, so it can avoid unavailable operations.
Capabilities and Krita limits
The current release supports native preset-backed painting and shapes, persistent document and layer editing, selections, color operations, KRA/PNG output, and Unity-oriented animation, tileset and named-region packages. Preview and asset operations return PNG images directly to the MCP caller. Re-export preserves Unity .meta sidecars for stable generated filenames.
The tested Krita 5.3.2.1 build imposes several safety limits. Other builds are evaluated at runtime and may report different available features:
- Free layer scale, rotate, shear and crop operations are not native Undo commands. The bridge creates a hidden backup layer and blocks a second direct transform until the KRA is saved, closed and reopened.
checkpoint_reopen=truecan perform that round trip automatically. - Transform masks are limited to three per open document. Same-session mask mutation/removal and mixing mask and direct transform backends are blocked until Krita restarts.
Node.paintLinerequires integerQPointvalues, so incoming canvas coordinates are rounded at the native API boundary.- PNG export temporarily enables Krita batch mode so no format dialog can block the local bridge.
Timeouts and production guardrails
Timeouts are operation-specific across Codex, the MCP BridgeClient, the local HTTP bridge and Qt's main-thread dispatcher:
Only the beginning is shown; read the rest in the repo