Post, schedule and run ads from Kimi Code

What is Kimi Code?

Kimi Code is Moonshot AI’s terminal agent, installed as a single binary with no Node.js needed. It is an MCP client for local and remote servers, configured in an mcp.json file, and it signs in to a remote server with OAuth from inside its own interface.

Kimi Code or the Kimi app? This page is Kimi Code, Moonshot’s terminal agent. We have found no documented way to add a custom MCP server to the Kimi chat app, so we do not claim one.

Hermoso is marketing on autopilot: 876+ tools over one MCP endpoint covering competitor ad research, finished image and video ads across 90+ models, publishing and scheduling to ten social channels, and campaign management on Meta, Google Ads, Microsoft Advertising, Reddit Ads, LinkedIn, Pinterest, X Ads, TikTok Ads, Snapchat Ads, ChatGPT Ads and Apple Search Ads. One connection, and Kimi Code has all of it.

Connect Hermoso to Kimi Code

1. Add Hermoso to ~/.kimi-code/mcp.json (or .kimi-code/mcp.json in one project). An entry with a url and no transport is a streamable HTTP server:

   { "mcpServers": { "hermoso": { "url": "https://app.hermoso.ai/mcp" } } }

   Or run /mcp-config inside Kimi Code to add it without editing the file.
2. Sign in. Inside Kimi Code run /mcp-config login hermoso and approve on the Hermoso page with your Hermoso account. /mcp shows the connection status.
3. Or run it locally. With Node.js installed, sign in once with npx -y hermoso auth login and use the local server instead, with no key in the file:

   { "mcpServers": { "hermoso": { "command": "npx", "args": ["-y", "hermoso", "mcp"] } } }

4. Ask Kimi Code for something. “Pull my three closest competitors’ longest-running ads and remix the best hook into a 9:16 video,” or “post this render to the channel.” The agent picks the tools; you approve the spend.

Two Kimi Code details matter with a server this size. Hermoso has 876+ tools, and Kimi Code puts every tool of a server in the model’s list by default; its experimental deferred: true setting loads them on demand instead, once the tool-select flag is on. And a project-level .kimi-code/mcp.json only runs in a folder you trust, which is the right place for a repo that should always use one brand. The file shapes and commands are quoted from Kimi Code’s MCP documentation, read on 2026-10-03, and documented rather than run here. Hermoso is not affiliated with or endorsed by Moonshot AI.

Every channel Kimi Code can publish to

Each channel links to its Hermoso page, with that channel’s real caption cap, visibility options and what it refuses. Kimi Code reaches all of them through the same tools as every other agent.

Every one of them queues through one schedule_post calendar with per-channel captions, and list_scheduled reports per-channel outcomes rather than a single green tick, because “the job succeeded” and “the post went out” are different questions. A scheduled post lives in Hermoso, so it goes out on time whether or not Kimi Code is still running.

Two channels that are built but not offered

Being straight about this is worth more than a longer list. Two publishing surfaces exist in the codebase and are held back, each waiting on the platform rather than on us:

• Reddit: organic posting and post stats are built, but Reddit’s Responsible Builder Policy requires explicit written approval before an app may use the Data API, and that ticket has not been granted. The connector is held back rather than offered as an OAuth screen leading to a dead API. Reddit Ads is a different connection and it is live: the full campaign tree, forecasting, targeting search, pixels and lead forms.
• Google Business Profile: post_to_google_business is built, with events, offers and a real call-to-action choice, and so are the listing insights. Google allowlists the Business Profile API per project and the default quota is zero, so every call would 403 for every user. It stays gated until Google grants the project access.

A connector that would hand you a successful OAuth and a dead API is worse than one that is not offered yet, so neither is listed as available.

Three things to type once it is connected

1. Research. “Who are my three closest competitors, and what are their longest-running Meta ads? Tell me which hook keeps repeating.” It runs find_competitors → pull_competitor_ads → mine_angles.
2. Create. “Make me a 9:16 UGC video ad using that hook, with my real product photo and captions burned in.” It runs get_brand → plan_ad → render_ad, and hands back a finished mp4 URL.
3. Ship. “Schedule it to Instagram and TikTok for Tuesday 9am, and build a paused Meta campaign around it targeting the US at $30 a day.” It runs schedule_post → create_meta_campaign → create_meta_ad.

What Kimi Code cannot do on its own

An agent with a budget is only useful if the blast radius is bounded, so the fence is in the server rather than in a prompt. Every ad campaign, ad set, ad group and ad is created paused, and the status switches that arm real money refuse to run without an explicit confirmation flag. Every render is quoted first (hermoso_capabilities publishes each model’s exact credit cost before anything spends). Credits are reserved before the first provider call and settled at the exact cost afterwards, so a failed dispatch refunds rather than leaving you billed for nothing. Deletes are confirm-gated too, and every campaign tree is read back from the ad platform before your agent tells you what it built.

One step is deliberately yours: linking each account, once. Most channels link through the platform’s own OAuth consent screen in a browser; Bluesky takes an app password and Telegram a bot token, pasted in Hermoso. Everything after that is a tool call.

Kimi Code asks before an MCP call that matches no permission rule, and “Approve for this session” covers the rest of that session. Keep the publishing and spending tools on manual approval: Kimi’s own advice is to avoid an mcp__* wildcard that allows every tool at once, and its Ask When Needed mode approves MCP calls automatically.

What it costs

Adding Hermoso to Kimi Code costs nothing extra: there is one credit meter, and it does not care which client called. A free account starts with 30 credits at signup and 250+ more to earn. Credits are spent only on AI models and Ad Spy research; posting, scheduling, ads management and analytics are free on every channel except X, which bills per call because X charges per API request. Paid plans are $19, $49 and $149 a month for 1,000, 3,000 and 10,000 credits, and every feature is on every plan. hermoso_capabilities gives the exact credit price of any render before it runs.

Troubleshooting

• A local server prints help and exits. The arguments are missing the trailing mcp. npx -y hermoso on its own prints help; npx -y hermoso mcp starts the server.
• There is no browser on that machine. Create a key under MCP & CLI → Terminal & API keys and run npx -y hermoso auth login --token hmk_… instead.
• A channel is missing. Connect it in Hermoso under Settings → Connectors, then ask Kimi Code to run list_connectors again.
• Kimi Code answers without using Hermoso. Name it in the request: “use Hermoso to …”. That leaves no doubt about which tools should do the job.
• Hermoso’s tools do not appear in the current session. A server added mid-session only joins sessions started afterwards. Start a new session, then run /mcp to check the connection.

Beyond publishing

Publishing is the last step, and it is the smallest one. The same connection gives Kimi Code the Meta, Google and LinkedIn ad libraries plus organic TikTok, Instagram, YouTube, Reddit and Threads for research; 100+ image, video, voice and writing models on a single credit meter, with UGC avatars, dubbing, upscaling and native HTML ad formats; and the full campaign tree on eleven paid platforms. There are no per-vendor API keys to hold and no separate app to learn.

See the full tool list, every agent Hermoso works in, or what a marketing MCP is.

Hermoso in other agents

The same Hermoso account works in every agent below, so your brand, library, schedule and credits follow you between them.

Frequently asked questions

Can Kimi Code post to social media?

Yes, once you connect Hermoso's MCP server. Kimi Code can then publish to Facebook, Instagram, Threads, TikTok, YouTube, X, LinkedIn, Pinterest, Bluesky and Telegram, and schedule to all ten from one queue with per-channel captions.

How do I add Hermoso to Kimi Code?

Add a hermoso entry to ~/.kimi-code/mcp.json with the url https://app.hermoso.ai/mcp, then run /mcp-config login hermoso inside Kimi Code to approve it with your Hermoso account in the browser. With Node.js installed you can run it locally instead: sign in once with npx -y hermoso auth login and point the entry at npx -y hermoso mcp. Two Kimi Code details matter with a server this size. Hermoso has 876+ tools, and Kimi Code puts every tool of a server in the model’s list by default; its experimental deferred: true setting loads them on demand instead, once the tool-select flag is on. And a project-level .kimi-code/mcp.json only runs in a folder you trust, which is the right place for a repo that should always use one brand. The file shapes and commands are quoted from Kimi Code’s MCP documentation, read on 2026-10-03, and documented rather than run here. Hermoso is not affiliated with or endorsed by Moonshot AI.

Can Kimi Code generate the video and images too?

Yes, natively rather than by brokering it out. 100+ image, video, voice and writing models sit on one credit meter, and Kimi Code can price a render before it runs it because hermoso_capabilities publishes each model's exact cost. Output is a finished ad, with your real product in the scene and captions and a CTA composited over the render.

Is there a free tier for Kimi Code?

Yes. A free account starts with 30 credits and 250+ more you can earn as you set up and create, and the MCP server itself is free to add to Kimi Code. Paid plans are $19, $49 and $149 a month for 1,000, 3,000 and 10,000 credits. Every feature is on every plan including Free, and the only exception is enterprise SSO.

Is it safe to let Kimi Code post and run ads for me?

Hermoso keeps the steps that cost money or cannot be undone behind gates on its own server, whatever Kimi Code is set to do: every campaign is created paused, spend switches and deletes need an explicit confirmation, and a post only reaches an account you connected and ticked in Hermoso. Kimi Code asks before an MCP call that matches no permission rule, and “Approve for this session” covers the rest of that session. Keep the publishing and spending tools on manual approval: Kimi’s own advice is to avoid an mcp__* wildcard that allows every tool at once, and its Ask When Needed mode approves MCP calls automatically.

Do I need Node.js to use Hermoso in Kimi Code?

No. Kimi Code installs as a single binary, and the hosted route is a URL in mcp.json plus /mcp-config login hermoso. Node.js is only needed for the optional local route through npx -y hermoso mcp.