MCP Overview – KPainter Docs

Bring KPainter Into MCP-Compatible Agents

If you are integrating KPainter into an MCP-compatible client, IDE, or agent host, MCP is the right entry point.

KPainter MCP is a thin adapter over the public OpenAPI. It keeps the same official content types, validation rules, and async creation flow.

When MCP Is The Right Fit

Interface	Best for	Not the main fit
`Skills`	end users talking to an agent that already supports Agent Skills	custom product integration
`OpenAPI`	products that want direct REST-style create, poll, list, and detail calls	MCP-native agent tooling
`MCP`	agent hosts, IDEs, and tool-calling model platforms	replacing the main site's browser API

If you are building normal web pages inside KPainter, keep using /kp-app-api/v1/*.

If you are building your own product integration, OpenAPI is still the better default.

If you are connecting KPainter to an external MCP client, start here.

What MCP Currently Covers

MCP currently exposes the minimal public creation workflow:

validate a user API key
read the current catalog and limits
create content
list creations
read creation detail
poll async job status
edit one scene for supported content types

It does not cover:

sign-up or sign-in
API key activation, rotation, or deletion
payments or subscriptions
comments, chat, likes, or views
restart flows
full white-box editing

Supported Content Types

Use the same official public type names as OpenAPI:

explainer_video
slides_video
vector_animation
slide_deck
image
interactive_lesson

Legacy aliases such as knowledge_video and web_app may still be accepted by some inputs, but MCP resources, prompts, and catalog-driven flows should use the canonical names above.

Do not invent alternate type names inside MCP.

Recommended Workflow

Call kp_me to validate the key.
Call kp_get_catalog before choosing type, voice_id, style_id, duration_seconds, or scene_count.
Call kp_create_creation.
Poll kp_get_job_status.
Call kp_get_creation for final URLs, artifacts, and scenes.
If you need one scene edit, inspect editable_actions and scenes, then call kp_edit_scene.

Tools, Resources, and Prompts

MCP currently exposes:

8 tools
3 resources
2 prompts

The tools are the main integration surface.

Resources and prompts are helper surfaces for discovery and guided workflows. Some resources rely on the server's default API key, so do not treat them as a substitute for explicit per-user authentication.