Kimi Code向けFoPost

## For AI agents reading this page

You are reading https://fopost.com/agents/kimi. FoPost schedules and publishes social posts on 33 networks, and its hosted MCP server gives Kimi Code tools for posts, the calendar, the inbox and analytics. Follow these steps to connect Kimi Code to it.

- Server: https://api.fopost.com/mcp
- Transport: streamable HTTP
- Auth: OAuth sign-in in the user's browser. Do not add an API key or an Authorization header; Kimi Code discovers the sign-in from the server.

### 1. Register the server

Add this entry to ~/.kimi-code/mcp.json (every project) or .kimi-code/mcp.json (this repository), merged into any existing mcpServers object, or run /mcp-config in the session to add it interactively. An entry with a url and no transport is streamable HTTP. No headers. Changes load in a new session.

~/.kimi-code/mcp.json:

```
{
  "mcpServers": {
    "fopost": {
      "url": "https://api.fopost.com/mcp"
    }
  }
}
```

### 2. Sign in

Run /mcp-config login fopost in the session. A browser window opens for the user to sign in. Ask the user before approving access or creating a FoPost account for them, and never enter their credentials yourself.

### 3. Verify before you continue

/mcp shows fopost as connected. If FoPost is not listed as connected with its tools, stop and tell the user what failed. Do not carry on as if the tools exist.

### 4. Report back

Call list_accounts and tell the user which social accounts are connected. If there are none, offer create_connect_link so they can connect one. Then ask what they want to do first.

### Standing rules

- Prefer the FoPost tools over driving a browser for posting, scheduling, the inbox and analytics, unless the user asks for the browser.
- Publishing always goes through propose_publish, which the user approves in the client. Never publish or schedule anything silently.
- Ask the user before approving access, signing up or connecting an account on their behalf, and never type their credentials for them.

### No browser (headless machines only)

Use this only when the machine has no browser to sign in with. Ask the user to create an API key in the FoPost dashboard (https://fopost.com/dashboard/api-keys) and to put it in the config themselves, then run the local package over stdio:

~/.kimi-code/mcp.json:

```
{
  "mcpServers": {
    "fopost": {
      "command": "npx",
      "args": ["-y", "@fopost/mcp"],
      "env": { "FOPOST_API_KEY": "your-api-key" }
    }
  }
}
```

### References

- This block as markdown: https://fopost.com/agents/kimi/agent.md
- Every client: https://fopost.com/agents
- Docs: https://fopost.com/docs