Set up Codex CLI
- 01
Make a key
In 1Post, make a key with write scope under Settings, then API keys, and export it as ONEPOST_API_KEY in your shell.
- 02
Open the file
Edit ~/.codex/config.toml, or .codex/config.toml in a trusted project.
- 03
Add the server
Add the table below. bearer_token_env_var names the variable that holds the key.
- 04
Check the connection
Start Codex and ask it to list your 1Post accounts.
The Codex CLI settings
[mcp_servers.onepost]
url = "https://api.get1post.com/v1/mcp"
bearer_token_env_var = "ONEPOST_API_KEY"codex mcp add onepost --url https://api.get1post.com/v1/mcp/oauth
codex mcp login onepostThe key stays in the environment, not in the file.
A request and its reply
Once connected, Codex CLI sends tool calls like this one when you ask it to schedule a post. Account ids come from list_accounts.
{
"name": "create_post",
"arguments": {
"accounts": [
"ACCOUNT_ID"
],
"text": "Doors open at nine.",
"schedule_at": "2026-11-02T15:00:00Z"
}
}{
"id": "POST_ID",
"status": "scheduled",
"scheduled_at": "2026-11-02T15:00:00.000Z",
"accounts": [
{
"account_id": "ACCOUNT_ID",
"status": "queued"
}
]
}What the connection can do
| Tool | What it does | Needs |
|---|---|---|
| list_accounts | Lists connected accounts and their state | Read |
| create_post | Saves, schedules or publishes a post | Write |
| get_post | Reads one post and the result for each account | Read |
| cancel_post | Cancels a post that has not started | Write and confirm: true |
The connection acts with the role of the member who made the key or signed in, so a contributor's posts still go to review. The full tool list is on the MCP page.