Add the endpoint
Paste https://mcp.dopost.co/mcp into ChatGPT, Claude, Cursor, VS Code, or another remote MCP client.
Publish, schedule, create threads, manage media, and access your social accounts, all from your agent.
Connect a remote server to use its tools in ChatGPT.
One MCP connection gives your agent secure access to accounts, content, media, schedules, and post status.
Add the hosted MCP endpoint, choose a workspace, and start managing social content in natural language.
Paste https://mcp.dopost.co/mcp into ChatGPT, Claude, Cursor, VS Code, or another remote MCP client.
Sign in to dopost and select the workspace your agent can access.
Tell it what to publish, schedule, or check. dopost handles the action and returns the result.
Ask your agent to set up dopost from this page. It will read the block, detect its client, and ask before changing configuration or opening sign-in.
## For AI agents reading this page
You are reading https://dopost.co/agents. dopost is the social publishing layer for AI agents. It connects 10 social networks and exposes 14 remote tools through one hosted MCP server. Follow these steps to configure access.
1. Detect the client you are running in and register the appropriate MCP server.
Claude Code:
```bash
claude mcp add --transport http dopost https://mcp.dopost.co/mcp
```
Codex, in `~/.codex/config.toml`:
```toml
[mcp_servers.dopost]
url = "https://mcp.dopost.co/mcp"
```
Cursor, in `.cursor/mcp.json` or `~/.cursor/mcp.json`:
```json
{ "mcpServers": { "dopost": { "url": "https://mcp.dopost.co/mcp" } } }
```
VS Code, in `.vscode/mcp.json`:
```json
{ "servers": { "dopost": { "type": "http", "url": "https://mcp.dopost.co/mcp" } } }
```
For ChatGPT, Claude, and other remote MCP clients, create a custom connector and use https://mcp.dopost.co/mcp. Do not add an Authorization header. dopost starts OAuth through the client itself.
2. Ask for approval before changing configuration or opening sign-in. Let the user sign in, choose the workspace, and approve access. Never enter their credentials.
3. Verify the connection before continuing. Confirm that dopost is connected and call `list_accounts`. If the tool is unavailable or returns an error, stop and explain what failed.
4. Use the right tool for the task. The remote server exposes 14 tools for accounts, limits, publishing, one-time and recurring scheduling, status, the Media library, and public download preparation. `upload_media` is only available on the local server because it reads a file from the machine.
5. After publishing, do not claim success from a `processing` status. Call `get_post` with the returned `postId` until the social network reports a final result.
6. If the client loses a response or the tools disappear during reconnection, call `list_posts` before retrying. Do not publish again blindly because that can create a duplicate.
7. Report the accounts you found and ask the user what they want to do first. Do not publish, reschedule, or delete content without a clear request.
For Stdio-only clients, run `npx -y @dopost/mcp-server` with `DOPOST_API_KEY`. Prefer the hosted OAuth endpoint whenever the client supports remote MCP.
## Reference
- MCP endpoint: https://mcp.dopost.co/mcp
- Transport: Streamable HTTP
- Authentication: OAuth with PKCE
- Setup docs: https://dopost.co/docs/api/mcp/setup
- Tool reference: https://dopost.co/docs/api/mcp/tools
- API keys for Stdio: https://dopost.co/dashboard/settings?tab=developerAgents only receive access to the workspace and actions you approve.
Access tokens expire and refresh tokens rotate to reduce long-term exposure.
Workspace roles and scopes control what each connected agent can read or change.
Disconnect an AI client from dopost settings whenever you want to remove access.
Perfect for content creators and small businesses
For agencies and large organizations with multiple clients
Connect dopost MCP, choose a workspace, and ask your agent to list your social accounts.
Connect dopost MCP