Inside ChatGPT, Claude and Grok

Inside Kimi

Kimi Code and the Kimi Work desktop app: a remote HTTP server, with the key in a header.

Kimi, from Moonshot AI, connects to MCP servers in Kimi Code, its agent for the terminal and the editor, and in the Kimi Work desktop app. Add AutomateSocials as a remote HTTP server with your key in the x-api-key header, and brief it where you already work.

Kimi Code

  1. In AutomateSocials: Project setup → API keys & MCP → Create a key. Copy the sk_live_… key.
  2. In a terminal, add the server with the command below, your key in place of sk_live_….
  3. Check that it connected: kimi mcp test automate-socials lists the AutomateSocials tools. Inside Kimi Code, /mcp shows the server's status.
  4. Ask Kimi what you want. A safe first request is “List my connected social accounts”.
kimi mcp add --transport http \
  --header "x-api-key:sk_live_..." \
  automate-socials https://automatesocials.net/mcp

Or add it to Kimi Code's mcp.json: ~/.kimi-code/mcp.json for every project, or .kimi-code/mcp.json in one repository only.

{
  "mcpServers": {
    "automate-socials": {
      "url": "https://automatesocials.net/mcp",
      "headers": { "x-api-key": "sk_live_..." }
    }
  }
}

kimi mcp list shows the servers Kimi Code knows; kimi mcp remove automate-socials takes this one off again.

One key is one project. For several brands or clients, add one server per project, each with its own name and key. If a key ever ends up in a chat or a shared repository, revoke it under Project setup → API keys & MCP and make a new one.

Kimi Work (desktop app)

Kimi Work reads its MCP servers from its own mcp.json. Edit the file by hand rather than asking Kimi to: a wrong value in it stops Kimi from starting the server, and then the agent cannot fix it either.

  1. Close Kimi Work.
  2. On Windows, press Windows + R (or click into File Explorer's address bar), paste %APPDATA%\kimi-desktop\daimon-share\daimon\runtime\kimi-code\home and press Enter. Open mcp.json with Notepad.
  3. Add the automate-socials entry below, your key in place of sk_live_…. Keep "transport": "http" exactly as written: Kimi Work refuses "streamable-http" with “Invalid MCP server config … No matching discriminator”.
  4. Save, start Kimi Work again, and ask it to list your connected social accounts.
{
  "mcpServers": {
    "automate-socials": {
      "transport": "http",
      "url": "https://automatesocials.net/mcp",
      "headers": { "x-api-key": "sk_live_..." }
    }
  }
}

If the file already lists other servers, add only the automate-socials block next to them, with a comma between entries.

kimi.com

In the kimi.com chat in the browser, tools are added as plugins. We have not confirmed a way to add your own MCP server by URL there, so use Kimi Code or Kimi Work.

Still stuck? Ask a person.

Real people on support: the team that builds AutomateSocials reads and answers every message.

info@automatesocials.net