Setup
Connect your AI client to the hosted dopost MCP server.
Connect your AI client to the hosted dopost MCP server.
Connect your AI client to dopost's hosted MCP server. There is nothing to install and no local process to keep running.
https://mcp.dopost.co/mcpCopy this prompt into an AI agent that can read web pages and manage its own MCP configuration:
Set up dopost from https://dopost.co/ai-agents. Read the instructions for AI agents on that page, apply the configuration for your client, and ask for approval before opening sign-in or changing files.The Agents page contains the canonical, agent-readable setup block for Claude Code, Codex, Cursor, VS Code, ChatGPT, Claude, and other remote MCP clients. It also tells the agent how to verify the connection, check final publishing status, and avoid duplicate posts after a lost response.
Open the full instruction set at dopost.co/ai-agents.
Secure sign-in
Clients that support remote MCP open dopost in your browser. Sign in and approve the requested permissions once. Choose the workspaces to authorize. Workspaces you join later stay disabled until you enable them in Settings → MCP connections. Your password is never shared with the AI client.
Select your client below and add the hosted server URL. OAuth-capable clients complete the rest in your browser.
claude mcp add --transport http dopost https://mcp.dopost.co/mcpclaude mcp add --transport http dopost https://mcp.dopost.co/mcpYour client will open dopost so you can sign in and choose a workspace.
Ask your assistant:
List my connected social accounts.
If the assistant can see the dopost tools and returns your accounts, setup is complete.
Explore the assistant guides for client-specific setup and publishing examples.
Old tool schema
publish_post includes replyTo and thread. If your assistant only sees accountId, text, media, publishAt, and platformOptions, it has cached an older tool schema. Refresh the MCP tools or disconnect and reconnect dopost before trying again.
Some clients, such as Manus, Cue, NanoClaw or DeepSeek Harness, ask for a header instead of a sign-in. Use the same URL with Authorization: Bearer dpk_live_your_key. The key only reaches its own workspace.
For a stdio-only client, run npx -y @dopost/mcp-server and provide DOPOST_API_KEY as an environment variable. The local server includes upload_media for files on your disk, which the hosted server does not offer.
Agents that run shell commands but have no MCP client, such as Grok Bot, can use the dopost skill: npx skills add dopost-co/skills with DOPOST_API_KEY in their environment.
Manage API keys from Settings → API keys. From Settings → MCP connections you can remove or restore individual workspace access, or disconnect an OAuth client completely.
Prefer OAuth whenever your client supports it. API keys belong to one workspace and should never be saved in a repository.