Kie MCP Server

Kie MCP server exists for a simple reason — assistants are far more useful when they can act on Kie directly instead of describing what you should do. MCP for kie.ai: 45+ image, 70+ video, 20+ audio models with model intelligence.

What you get

A comprehensive Model Context Protocol server for the kie.ai generation API. Gives Claude (and any MCP client) access to 47+ image models, 86+ video models, and 20+ audio tools with deep model intelligence built in.

• Deep research embedded — — Every major model has a research field with verdicts, prompt techniques, weaknesses, cost-efficiency analysis, and competitor comparisons. Researched by Averiguare, our model intelligence agent
• Cost-aware — — Every model has pricing in credits and USD. The MCP tells you the cheapest option for your use case
• Smart filtering — — list_models filter="lip sync" or filter="architecture" or filter="cheapest video" — searches across capability tags, descriptions, AND research fields
• Dual-mode transport — — stdio for local Claude Code, HTTP Streamable for remote Cowork/cloud usage

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

Once Kie is connected, these are the calls the assistant has available:

• Utility — The Utility tool exposed by this server
• Prerequisites — The Prerequisites tool exposed by this server
• Setup — The Setup tool exposed by this server

Configuration and credentials

You will need 3 environment variables: KIE_API_KEY, KIE_PROJECT_ROOT, KIE_CALLBACK_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 18+ - A kie.ai API key from kie.ai/api-key

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the kie mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Kie's toolset — Utility, Prerequisites, Setup — is a fair guide to whether it matches your workflow. It is maintained by elibarnett; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Kie's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.