Schedule social media posts from Kimi.

Kimi Code is Moonshot AI’s terminal agent running Kimi K3. Add SociaHive to its MCP config, sign in once, and it can schedule and report on your posts.

Connect Kimi How to connect

Server addresshttps://www.sociahive.com/api/mcp

How it connects: MCP server in ~/.kimi-code/mcp.json or through /mcp-config
Sign-in: OAuth with /mcp-config login, or an API key header
What you need: Kimi Code with model access from Moonshot, plus a SociaHive trial or paid plan
Best for: Turning docs, release notes and project files into scheduled posts
Not for: The kimi.com chat app, where custom MCP support is not confirmed

Set it up in Kimi.

Needs a SociaHive trial or paid plan.

Connect SociaHive to Kimi

Your server address

https://www.sociahive.com/api/mcp

Kimi

Kimi Code CLI, in your terminal

1
Install Kimi Code CLI from Moonshot’s Kimi Code docs, start it with kimi and sign in with /login.
2
Add SociaHive to ~/.kimi-code/mcp.json with the entry below, or run /mcp-config and add a server with the SociaHive address.
3
Run /mcp-config login sociahive. A browser opens: sign in to SociaHive and approve. Tick Read-only access if you only want reports.
4
Start a new session and run /mcp to check the server is connected. Servers added by editing the file only show up in new sessions.
5
Ask Kimi to list your SociaHive connected accounts.

Then: Point Kimi at a folder in your project and ask it to turn what changed into posts.

Install in Kimi

mcp.json with sign-in

~/.kimi-code/mcp.json for every project, or .kimi-code/mcp.json in one project. Then run /mcp-config login sociahive.

{
  "mcpServers": {
    "sociahive": {
      "url": "https://www.sociahive.com/api/mcp"
    }
  }
}

mcp.json with an API key

Use this instead of signing in, for example on a server. Create the key in SociaHive under Settings → API keys.

{
  "mcpServers": {
    "sociahive": {
      "url": "https://www.sociahive.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk_your-key"
      }
    }
  }
}

Things to ask first.

Copy one into a chat once you are connected.

One post per updated page, queued across the week.
Per-post numbers with a short read on the pattern.
Date, time, platform and caption for every queued post.

What is Kimi Code?

Kimi Code CLI is Moonshot AI’s open-source coding agent for the terminal. It runs Moonshot’s Kimi K3 model, reads and edits your project, and calls outside tools through MCP servers set up in a JSON file or with the /mcp-config command.

It is separate from the Kimi chat app at kimi.com. We have not confirmed that the chat app can add a custom MCP server, so this page covers Kimi Code.

With SociaHive connected, Kimi can schedule posts to 22 platforms, read your numbers and build comment-to-DM automations as drafts without leaving the terminal.

Can Kimi post on a schedule?

We have not seen Kimi Code document a way to run tasks on its own timer. It works while you have a session open.

Your posts do not depend on that. Kimi hands each post to SociaHive with a time, and SociaHive publishes it from its queue whether or not the terminal is still open.

Everything Kimi can do in SociaHive.

Schedule posts

Write a post and queue it at your best time, on any account you connected.

Post right now

Publishes straight away, after you confirm in the chat.

See your calendar

Everything that is scheduled, across all your accounts.

Read your numbers

Reach, saves and engagement per post, and what to post more of.

Build DM automations

Describe it in one sentence. It builds the flow as a draft for you to turn on.

Check your automations

Which flows are live and how often each one fires.

Reuse what works

Save your best posts to an evergreen queue and reshare them later.

Move posts in bulk

Shift a whole day of posts in one go, keeping their times.

What Kimi gets: the SociaHive MCP server.

One address, https://www.sociahive.com/api/mcp. The same server works in every AI tool on this site.

MCP (Model Context Protocol) is the open standard AI tools use to reach outside apps. SociaHive runs a hosted MCP server, so there is nothing to install or keep running: Kimi calls it over the internet and acts in your SociaHive account. These are the tools it uses most. See every tool and the API.

Tool	What it does
list_accounts	Lists the social accounts you connected to SociaHive.
create_scheduled_post	Writes a post, with text, images or video, for one or more accounts.
schedule_post	Queues a post at a time you pick or at your best time.
find_next_slot	Finds the next free slot in your posting schedule.
publish_post_now	Publishes straight away, after you confirm.
upload_media_from_url	Copies an image or video from a public link into your media.
get_scheduler_calendar	Shows what is scheduled, across all accounts.
get_post_analytics	Reads reach, likes, comments and saves per post.
get_content_insights	Finds which formats and topics beat your usual numbers.
generate_flow	Builds a DM automation from one sentence, as a draft.
list_flows_with_stats	Lists your automations, which are live and how often they run.
bulk_reschedule_posts	Moves many scheduled posts in one go.

One connection, every channel.

Connect each account once in SociaHive and Kimi can post to it. Scheduling covers 22 platforms; X needs a paid plan.

Instagram
Facebook
LinkedIn
Twitter/X
TikTok
YouTube
Threads
Bluesky
Pinterest
Telegram
Discord
Mastodon
Lemmy
Dev.to
Hashnode
WordPress
Listmonk
Slack
Tumblr
Dribbble
Twitch
Kick

DM automations run on Instagram, Facebook, Messenger and WhatsApp on every paid plan, and on Telegram on Pro and Agency.

Is it safe to let Kimi post for you?

You approve the connection
Sign in to SociaHive and approve, or use an API key you can delete at any time. The agent never sees your social passwords.
Read-only if you want
Tick “Read-only access” when you connect and the agent can look at everything and change nothing.
Nothing goes live by surprise
Publishing right now asks for your yes in the chat. Automations it builds start as drafts until you turn them on.
Revoke in one click
Settings → Connected apps in SociaHive cuts the agent off on its next request. API keys are deleted under Settings → API keys.

Kimi or another AI tool?

Every one of them connects to the same SociaHive account.

Agent	Kind	How it connects	Best for
Kimi	Coding agent	MCP server in ~/.kimi-code/mcp.json or through /mcp-config	Turning docs, release notes and project files into scheduled posts
Claude Code	Coding agent	The SociaHive plugin, or claude mcp add with the server address	Bulk work from files: CSVs, changelogs, release notes
Cursor	Coding agent	The Add to Cursor link, or mcp.json with the server address	Announcing what you ship without leaving the editor
Codex	Coding agent	codex mcp add, or an [mcp_servers] entry in config.toml	Turning releases and diffs into posts
ChatGPT	Chat assistant	A custom MCP plugin on chatgpt.com, with the SociaHive server address	Writing captions and scheduling them in the same chat
OpenAI dots	Autonomous agent	Custom MCP server added in ChatGPT, then allowed for the dot	Watching your calendar and automations between check-ins

What does it cost?

Kimi Code CLI is open source. Model usage is paid through the Moonshot API or a Kimi Code plan; check Moonshot’s pricing page for current rates.

On SociaHive, MCP access is part of the 7-day trial and every paid plan, from Creator up. There is no extra charge per tool call. See plans.

Included in the trial.

And on every paid plan. 7-day free trial for the paid features. No credit card required.

Connect Kimi

Troubleshooting Kimi.

SociaHive is in mcp.json but Kimi does not list it.: Start a new session. Kimi reads servers added by editing the file only when a session starts. Then run /mcp.
A project-level server is ignored.: Kimi asks you to trust a folder before it loads its .kimi-code/mcp.json. Trust the workspace, or put SociaHive in ~/.kimi-code/mcp.json instead.
Calls fail as unauthorized after it worked before.: Run /mcp-config login sociahive again to sign in, or check that the API key in your headers has not been revoked.
It asks me to upgrade: MCP access is part of the SociaHive trial and every paid plan. On the free plan the agent can connect, but each request answers with an upgrade link.
An account is missing: The agent only sees accounts connected in SociaHive. Connect it under Connected accounts, then ask the agent to list your accounts again.
A post did not go out: Ask the agent for the post’s status, or open it in SociaHive. A failed post shows the platform’s reason, for example an expired login that needs reconnecting.
It says it is not allowed to change anything: You connected with read-only access. Remove SociaHive under Settings → Connected apps and connect again without ticking it.

FAQ

Is Kimi the same as Kimi Code?

Kimi is Moonshot AI’s family of models and apps. Kimi Code is its terminal agent, and it is the part that can connect to SociaHive through MCP.

Can I connect SociaHive to the Kimi app at kimi.com?

We have not confirmed that the chat app accepts custom MCP servers. Use Kimi Code CLI, which does.

Do I need an API key for Kimi?

No. Run /mcp-config login sociahive and approve SociaHive in the browser. A key in a header is there if you prefer it.

What about the older Kimi CLI?

Some older builds read ~/.kimi/mcp.json instead. If you still run one, the same entry works there, but Kimi Code CLI is the current tool.

Which platforms can Kimi post to?

Any of the 22 platforms SociaHive schedules to, such as Instagram, LinkedIn, Threads, Bluesky and Dev.to. X needs a paid SociaHive plan.

Is it free to start?

SociaHive’s 7-day trial includes MCP access. Kimi Code is free to install; model usage is billed by Moonshot.

Can it post or change things without asking me?

Automations it builds start as drafts, with every step written out, until they are turned on. Publishing a post right away needs your yes in the chat. If you only want it to look, tick “Read-only access” when you connect: it can read everything and change nothing.

Which plans include it?

The 7-day trial and every paid plan. On the free plan your assistant can still connect, but each request answers with a link to upgrade instead of running.

How do I disconnect it?

Open Settings → Connected apps in SociaHive and revoke it. It is cut off on its very next request. You can also remove the connector in your assistant.