Use tinyposter from Codex (and other coding agents)

Pick your path

Path A, MCP via Codex CLI (recommended)

Codex can set up MCP from a chat request. Copy one message into Codex, let it update the local config, then restart if Codex says the current session cannot see newly-added MCP servers.

1. 01

   Get a token

   Open your tokens page. Click Create token, name it “Codex,” copy the tp_… string. It only shows once.

2. 02

   Paste this into Codex

   Paste the whole message below into Codex chat. Replace the placeholder first, or use the install wizard and it will bake your token into the prompt.

   text

   Copy

   Install this Tinyposter MCP server for me in this AI tool.
   
   Server name: tinyposter
   Server URL: https://tinyposter.app/api/mcp
   Authorization header: Bearer tp_PASTE_YOUR_TOKEN_HERE
   
   Use the local/user MCP configuration for whichever tool this chat is running in:
   - Claude Code: add a remote HTTP MCP server named "tinyposter" with the URL and Authorization header above. Use local/project scope if available, so the token is not written to a shared repo file.
   - Codex CLI: add the equivalent server to my local Codex MCP config:
     [mcp_servers.tinyposter]
     url = "https://tinyposter.app/api/mcp"
     http_headers = { Authorization = "Bearer tp_PASTE_YOUR_TOKEN_HERE" }
   - Cursor, Continue, Cline, Zed, or another MCP client: add the same remote HTTP MCP server URL and Authorization header to that client's MCP settings.
   - Stdio-only clients: wrap the HTTP endpoint with "npx -y mcp-remote https://tinyposter.app/api/mcp" and pass the same Authorization header.
   
   Rules:
   - Do not commit this token or write it into any git-tracked file.
   - Do not print the token back to me. Mask it in status messages and logs.
   - After setup, verify the server is listed or connected.
   - If this current session cannot see newly-added MCP servers until restart, tell me exactly what to reopen.
   
   When it is connected, test it by asking Tinyposter to list my connected social accounts.

   Manual fallback

   If Codex cannot edit its own MCP config from chat, add this to ~/.codex/config.toml on macOS/Linux or %USERPROFILE%\.codex\config.toml on Windows:

   ~/.codex/config.tomltoml

   Copy

   [mcp_servers.tinyposter]
   url = "https://tinyposter.app/api/mcp"
   http_headers = { Authorization = "Bearer tp_PASTE_YOUR_TOKEN_HERE" }

3. 03

   Restart Codex and verify

   Quit and re-open Codex if the setup agent tells you to. In any session, run /mcp or codex mcp list. You should see tinyposter listed, along with its tools.

   Try asking:

   text

   Copy

   Use tinyposter to list my connected social accounts.

Path B, Use the CLI

If your agent doesn't do MCP (older Codex builds, generic shell agents) but it can run terminal commands, install the tinyposter CLI.

1. 01

   Install the CLI

   From a terminal, run:

   bash

   Copy

   npm install -g tinyposter

   Or skip install and use it on demand:

   bash

   Copy

   npx tinyposter <command>

   Needs Node.js 18 or newer. If you don't have Node, get it at nodejs.org.

2. 02

   Set the token

   Get a token from your tokens page. Then either:

   Option 1, interactive:

   bash

   Copy

   tinyposter login

   Option 2, environment variable (best for agents/CI):

   bash

   Copy

   export TINYPOSTER_TOKEN=tp_paste_your_token_here

3. 03

   Tell your agent to use it

   Most agents already know how to run terminal commands. Drop these instructions into your project notes or system prompt:

   text

   Copy

   When the user asks you to post to social media, use the tinyposter CLI:
   - tinyposter accounts          # list connected platforms
   - tinyposter post "<text>" --to PLATFORMS
   - tinyposter schedule "<text>" --to PLATFORMS --at <ISO datetime>
   - tinyposter list              # see recent posts
   - tinyposter cancel <id>       # cancel a scheduled post
   Pass --json to get machine-readable output.

Path C, Raw HTTP with curl

If you can't install anything, every agent that runs shell can use curl. Set your token in an env var, then:

export TINYPOSTER_TOKEN=tp_paste_your_token

# List connected accounts
curl -s https://tinyposter.app/api/v1/accounts \
  -H "Authorization: Bearer $TINYPOSTER_TOKEN"

# Post to multiple platforms
curl -s https://tinyposter.app/api/v1/posts \
  -H "Authorization: Bearer $TINYPOSTER_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"text":"hello from my agent","platforms":["TWITTER","LINKEDIN"]}'

# Schedule for later
curl -s https://tinyposter.app/api/v1/posts \
  -H "Authorization: Bearer $TINYPOSTER_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"text":"sunday note","platforms":["THREADS"],"scheduled_at":"2026-05-03T13:00:00Z"}'

Cursor specific

Cursor supports MCP natively (no CLI needed). Full walkthrough on the MCP page under “Cursor.” If you want the CLI path instead, drop the same instructions from Path B into your .cursorrules or .cursor/rules.md.

Claude Code specific

For Claude Code, MCP is the cleanest path, see the Claude guide. If you want the CLI for some reason, install it as in Path B and add a note to your CLAUDE.md:

# Social posting

Use the `tinyposter` CLI for any social media tasks.
Token is in `$TINYPOSTER_TOKEN`. Run `tinyposter help` to see commands.

Troubleshooting

Next

• MCP reference, every tool, every input
• CLI guide, every command and flag
• HTTP API, what the CLI is calling under the hood