# MCP server for X, Bluesky, Mastodon and LinkedIn

[

Install Statuzbrew, npm or the shell script. Then statuz init.](/download)[

Add it to your agentOne command or one config block, below.](#setup)[

AskIt writes, schedules and checks. You approve.](#prompts)
## Choose your agent
CLIMCP
Claude Code
Cursor

Codex
Claude Desktop
VS Code
Windsurf

Gemini CLI
Copilot CLI

OpenCode

LM Studio

Other
Your agent runs statuz in a terminal, like you do. statuz init lets you pick which apps learn how.
Run this in your terminal
```
statuz init
```
Copy

- 

Tick Claude Code in the list it shows; the Statuz skill goes in ~/.claude/skills.
- 

Ask: "Schedule a post to Bluesky for tomorrow 9am." Claude Code runs statuz for you.
Run this in your terminal
```
claude mcp add statuz -- statuz mcp
```
Copy

- 

In Claude Code, run /mcp and check statuz is connected.
- 

Ask: "Schedule a post to Bluesky for tomorrow 9am."
Run this in your terminal
```
statuz init
```
Copy

- 

Tick Cursor in the list it shows; the Statuz skill goes in ~/.cursor/skills.
- 

The agent runs statuz in its terminal and asks before each command.
Add to ~/.cursor/mcp.json
```
{
 "mcpServers": {
 "statuz": { "command": "statuz", "args": ["mcp"] }
 }
}
```

- 

Open Cursor Settings → MCP and turn statuz on.
- 

Ask the agent to draft a thread with posts_create and draft: true.
Run this in your terminal
```
statuz init
```
Copy

- 

Tick Codex in the list it shows; the Statuz skill goes in ~/.agents/skills.
- 

Ask: "What is scheduled this week?" Codex runs statuz and shows each result.
Run this in your terminal
```
codex mcp add statuz -- statuz mcp
```
Copy

- 

Start codex; the statuz tools load with it.
- 

Ask: "What is scheduled this week on Statuz?"

Claude Desktop can't run terminal commands. Use MCP: Statuz shows up as tools in a new chat.
Run this in your terminal
```
statuz agents add --agent claude-desktop
```
Copy

- 

It adds Statuz to claude_desktop_config.json; your other servers stay.
- 

Restart Claude Desktop. Statuz shows up under the tools icon in a new chat.
Run this in your terminal
```
statuz init
```
Copy

- 

Tick VS Code in the list it shows; the Statuz skill goes in ~/.copilot/skills.
- 

Copilot in agent mode runs statuz in the terminal after you approve.
Add to .vscode/mcp.json
```
{
 "servers": {
 "statuz": { "type": "stdio", "command": "statuz", "args": ["mcp"] }
 }
}
```

- 

Run "MCP: List Servers" and start statuz.
- 

Use it from Copilot Chat in agent mode.
Run this in your terminal
```
statuz init
```
Copy

- 

Tick Windsurf in the list it shows; the Statuz skill goes in ~/.codeium/windsurf/skills.
- 

Cascade runs statuz in its terminal.
Add to ~/.codeium/windsurf/mcp_config.json
```
{
 "mcpServers": {
 "statuz": { "command": "statuz", "args": ["mcp"] }
 }
}
```

- 

Refresh the MCP list in Cascade.
- 

Ask Cascade to schedule a post.
Run this in your terminal
```
statuz init
```
Copy

- 

Tick Gemini CLI in the list it shows; the Statuz skill goes in ~/.gemini/skills.
- 

Gemini CLI asks before it runs each statuz command.
Add to ~/.gemini/settings.json
```
{
 "mcpServers": {
 "statuz": { "command": "statuz", "args": ["mcp"] }
 }
}
```

- 

In Gemini CLI, run /mcp and check statuz is listed.
- 

Ask: "Draft a thread for Friday at 10."
Run this in your terminal
```
statuz init
```
Copy

- 

Tick Copilot CLI in the list it shows; the Statuz skill goes in ~/.copilot/skills.
- 

Copilot CLI asks before it runs each statuz command.
Add to ~/.copilot/mcp-config.json
```
{
 "mcpServers": {
 "statuz": { "type": "local", "command": "statuz", "args": ["mcp"], "tools": ["*"] }
 }
}
```

- 

In copilot, run /mcp and check statuz is listed.
- 

Ask: "What is scheduled this week on Statuz?"
Run this in your terminal
```
statuz init
```
Copy

- 

Tick OpenCode in the list it shows; the Statuz skill goes in ~/.config/opencode/skills.
- 

OpenCode runs statuz in its shell.
Add to ~/.config/opencode/opencode.json
```
{
 "mcp": {
 "statuz": { "type": "local", "command": ["statuz", "mcp"] }
 }
}
```

- 

Start opencode; the statuz tools load with it.
- 

Ask it to schedule a post to Mastodon.

LM Studio can't run terminal commands. Use MCP: Statuz shows up as tools in a new chat.
Run this in your terminal
```
statuz agents add --agent lm-studio
```
Copy

- 

It adds Statuz to ~/.lmstudio/mcp.json; your other servers stay.
- 

LM Studio loads it on save. Chat with a model that can call tools.
Any agent with a terminal
```
statuz help --json
```
Copy

- 

Every command and flag with its JSON Schema, for the agent to read.
- 

Add --json to any command; errors come back with a code and a plain message.
Any MCP client: start this over stdio
```
statuz mcp
```
Copy

- 

Or use HTTP: http://127.0.0.1:3850/mcp while statuz start runs.
- 

Send the token in ~/.statuz/run/relay.token as a Bearer header.

## What your agent can do

Write and schedulePosts and threads, now or at "fri 17:30", checked against every limit.

Plan a weekLists what is scheduled, moves posts, fills the gaps.

Attach mediaAdds images and video from your disk with alt text.

Check accountsFinds an expired sign-in before a post is due.
## Try asking

```
Schedule a week of launch posts: one a day at 9am, Monday to Friday, to X and Bluesky. Show me the list first.
```
Copy
```
What's scheduled for next week?
```
Copy
```
Anything failed? Retry it.
```
Copy
Two ways in, same commands. Agents with a shell (Claude Code, Cursor, Codex) call `statuz` directly; apps without one, like Claude Desktop, use `statuz mcp`, which serves every command as a tool over stdio. The [CLI reference
](/docs/cli) lists them all.

## Teach your agent

```
statuz init
```
Copy
Writes `AGENTS.md` and the Statuz skill into `~/.statuz`, then lists the agent apps it finds. Tick the ones that should use Statuz. Apps with a terminal get the skill in their own folder; apps without one get an MCP server in their config:

AppWhereClaude Code`~/.claude/skills`Codex, Zed, OpenHands`~/.agents/skills`Cursor`~/.cursor/skills`VS Code, Copilot CLI`~/.copilot/skills`Windsurf`~/.codeium/windsurf/skills`Gemini CLI`~/.gemini/skills`OpenCode`~/.config/opencode/skills`Amp`~/.config/amp/skills`Goose`~/.config/goose/skills`Cline`~/.cline/skills`Kilo Code`~/.kilo/skills`Factory Droid`~/.factory/skills`Qwen Code`~/.qwen/skills`Crush`~/.config/crush/skills`Warp`~/.warp/skills`Junie`~/.junie/skills`Mistral Vibe`~/.vibe/skills`Kimi Code`~/.kimi-code/skills`Qoder`~/.qoder/skills`Pi`~/.pi/agent/skills`Letta Code`~/.letta/skills`Trae`~/.trae/skills`Claude DesktopMCP server in `claude_desktop_config.json`LM StudioMCP server in `~/.lmstudio/mcp.json`JanMCP server in `mcp_config.json`AnythingLLMMCP server in `anythingllm_mcp_servers.json`BoltAIMCP server in `~/.boltai/mcp.json`Show 20 more
Some apps also read other apps' folders (Cursor reads `~/.claude/skills`), so ticking several can show the skill twice. Nothing already there is overwritten. Untick an app to disconnect it, or use `statuz agents list | add | remove`.

## Tool names

Command id with dots turned into underscores. Inputs match the flags, in camelCase.

CLIMCP tool`statuz posts create``posts_create``statuz posts list``posts_list``statuz accounts list``accounts_list``statuz status``status`
## Try it

Connect an account ([Accounts
](/docs/accounts)), run `statuz start`, then ask:

Schedule a week of launch posts: one a day at 9am, Monday to Friday, to X and Bluesky. Under 280 characters each. Show me the list first.

More prompts:

- "What's scheduled for next week?"

- "Move Thursday's post to Friday at 10."

- "Anything failed? Retry it."

- "Open my post for Monday."

Posts too long for a destination are rejected before saving, and the agent sees why.

## Open in the app

`statuz open --post <id>` (or `--page queue`) shows it in the Mac app when it's installed, else on statuz.cloud for Cloud's posts. An agent on Statuz Cloud gets the link to hand you instead.

## Read and write

Every command is read or write; the [CLI reference
](/docs/cli) marks each. On [Statuz Cloud
](/docs/cloud), an API key has its own role: viewer (reads), member (also writes posts and connects accounts) or admin (also runs the team and settings). There are no owner keys, so no key reaches billing, and a key never does more than its creator can today. Make one with `statuz cloud keys create --label CI --role member`; revoke it from the API keys page or `statuz cloud keys revoke`.

## Local or Cloud

Agents follow the target: `statuz use local` or `statuz use cloud`.
[

](/)
Schedule posts from your terminal or your agent.
LightDarkAuto© 2026 [Intenseloop, Inc.](https://intenseloop.com)[
](https://x.com/intent/follow?screen_name=stewones)