MCP server for X, Bluesky, Mastodon and LinkedIn

statuz init

• 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.

claude mcp add statuz -- statuz mcp

• In Claude Code, run /mcp and check statuz is connected.
• Ask: "Schedule a post to Bluesky for tomorrow 9am."

statuz init

• 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.

{
  "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.

statuz init

• 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.

codex mcp add statuz -- statuz mcp

• 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.

statuz agents add --agent claude-desktop

• 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.

statuz init

• 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.

{
  "servers": {
    "statuz": { "type": "stdio", "command": "statuz", "args": ["mcp"] }
  }
}

• Run "MCP: List Servers" and start statuz.
• Use it from Copilot Chat in agent mode.

statuz init

• Tick Windsurf in the list it shows; the Statuz skill goes in ~/.codeium/windsurf/skills.
• Cascade runs statuz in its terminal.

{
  "mcpServers": {
    "statuz": { "command": "statuz", "args": ["mcp"] }
  }
}

• Refresh the MCP list in Cascade.
• Ask Cascade to schedule a post.

statuz init

• Tick Gemini CLI in the list it shows; the Statuz skill goes in ~/.gemini/skills.
• Gemini CLI asks before it runs each statuz command.

{
  "mcpServers": {
    "statuz": { "command": "statuz", "args": ["mcp"] }
  }
}

• In Gemini CLI, run /mcp and check statuz is listed.
• Ask: "Draft a thread for Friday at 10."

statuz init

• Tick Copilot CLI in the list it shows; the Statuz skill goes in ~/.copilot/skills.
• Copilot CLI asks before it runs each statuz command.

{
  "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?"

statuz init

• Tick OpenCode in the list it shows; the Statuz skill goes in ~/.config/opencode/skills.
• OpenCode runs statuz in its shell.

{
  "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.

statuz agents add --agent lm-studio

• 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.

statuz help --json

• 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.

statuz mcp

• 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.