Codex
Set up Codex to manage your social accounts with dopost.
Set up Codex to manage your social accounts with dopost.
Codex is OpenAI's coding agent. It runs in a terminal CLI, in the Codex desktop app and in IDE extensions, reads and edits your repository, runs commands and connects to MCP servers that you configure once for every session.
Check the API access requirements before connecting your workspace.
Add the hosted server and sign in once
Sign in to dopost to connect your accounts. No API key is needed.
Where to configure it: Codex CLI or the Codex app MCP settings
codex mcp add dopost --url https://mcp.dopost.co/mcp
codex mcp login dopostcodex mcp add dopost --url https://mcp.dopost.co/mcp
codex mcp login dopostInstall the dopost skill and let Codex call the REST API
Agents that run shell commands and need to upload files from disk.
Where to configure it: The environment where Codex runs commands
Create the key in Settings → API keys, in the workspace you want to connect. Select the permissions for the actions you will use; analytics needs analytics:read. Store the key in the environment or the client's credential field.
npx skills add dopost-co/skills -a codex
export DOPOST_API_KEY=dpk_live_your_keynpx skills add dopost-co/skills -a codex
export DOPOST_API_KEY=dpk_live_your_keyRun the dopost MCP server locally inside Codex
Local file uploads and clients without remote MCP support.
Where to configure it: Codex's local MCP configuration
Create the key in Settings → API keys, in the workspace you want to connect. Select the permissions for the actions you will use; analytics needs analytics:read. Store the key in the environment or the client's credential field.
codex mcp add dopost --env DOPOST_API_KEY=dpk_live_your_key -- npx -y @dopost/mcp-servercodex mcp add dopost --env DOPOST_API_KEY=dpk_live_your_key -- npx -y @dopost/mcp-serverStart a new conversation and ask:
Use dopost to list my connected social accounts.
Check that the returned accounts belong to the workspace you authorized.
Read CHANGELOG.md and turn the v2.4 entry into a four-post X thread for tomorrow at 09:00.
Upload dist/demo.mp4 and post it on LinkedIn with a short summary of v2.4, Wednesday at 10:00.
Read the diff for the new bulk import feature. Write a LinkedIn post showing what users can do now, include a concrete before-and-after example and schedule it for Monday at 10:00.
Compare my accounts' performance over the last 30 days and show my best-performing posts. Include when the data was last updated.
You need analytics:read. See the MCP reference or the analytics endpoints, depending on your connection method. Available metrics depend on the platform and collected data.
Copy the URL printed in the terminal into your browser, finish the sign-in, then run codex mcp list to confirm dopost is authenticated.
It cached an older list of dopost tools. Refresh the MCP tools or remove and re-add dopost, then start a new session.
Check that the workspace has a Creator, Pro or Agency plan and the credential includes the action's permissions. For analytics, check analytics:read. Existing credentials do not receive new permissions automatically.
Reconnect dopost and approve the required workspaces and permissions. Then refresh the client's MCP connection and start a new conversation.
Check that the key is active and belongs to the correct workspace. For the Skill or local server, check that the agent process receives DOPOST_API_KEY. A remote MCP client using a token needs Authorization: Bearer <key>; REST calls use x-api-key.
Check the authorized workspace, connected accounts, and date range. Analytics may be partial or not yet available. Do not treat missing values as zero; inspect the returned freshness and coverage information.