OpenPMM for agents

Social publishing for coding agents.

Let OpenClaw, Hermes, Claude Code, Codex, Cursor, or another coding agent prepare, queue, schedule, and publish to your own personal or company accounts through hosted MCP or one predictable command line.

OAuth and every public send stay behind an explicit human checkpoint.

MCP · Connect your agent

One connection. Pick your agent.

Add the hosted OpenPMM MCP server, approve access in your browser, and start with a read-only request. No API key to copy.

Any agent

Send your agent one instruction and let it configure the connection.

Paste into your agent

Read https://www.openpmm.com/docs/mcp/overview and connect this agent to OpenPMM.
Use the remote MCP server at https://api.openpmm.com/mcp.
Ask me to approve access in the browser.

Claude Code

Add OpenPMM once and use it from every Claude Code project.

Run in your terminal

claude mcp add --transport http --scope user openpmm https://api.openpmm.com/mcp

Codex

Add OpenPMM to the Codex CLI and Codex app.

Run in your terminal

codex mcp add openpmm --url https://api.openpmm.com/mcp
codex mcp login openpmm

MCP can use every public OpenPMM capability across your Account. Publishing and other confirmed actions keep their explicit human checkpoint.

Read MCP docs

CLI · Any terminal agent

No account, skill, or API key is needed to start. Paste this prompt into Claude Code, Codex, Cursor, OpenClaw, Hermes, or another terminal agent. It creates your signup link, then finishes CLI access after you approve one browser flow.

CLI setup prompt

Help me get started with OpenPMM from this terminal.

1. Ask me for my email address and pick a Workspace name.
2. Run this one-off command with my answers:
   npx -y @openpmm/cli signup create --email "<email>" --workspace-name "<workspace name>" --authorize-cli --json
3. Give me the signup URL shown by the CLI and wait while I finish in the browser with the same email address.
4. After I approve the CLI in the browser, run:
   npx -y @openpmm/cli auth login --resume --json
5. When the CLI confirms that it is connected, run:
   npx -y @openpmm/cli destinations list --json
6. Summarize my connected destinations and help me connect any that are missing.

Agent rules

The CLI is the boundary.

The credential file is an internal CLI detail. A direct API integration is a separate workflow with its own least-privilege key.

01Use only the openpmm command for a CLI-managed OpenPMM workflow.
02Never read, export, or reuse the CLI credential store.
03Do not call /v1 with the CLI credential.
04Use request files and JSON output for deterministic automation.
05After an accepted publish, stop or use the next CLI command. Never publish again.

Social media CLI for developers

Use one terminal contract for the work your agent already does.

The CLI is useful when a product update starts in a repository, a script, or an agent task. It keeps discovery, media, drafting, scheduling, and confirmation in the same workflow.

Product teams

Turn shipped work into a reviewed post.

Keep the source context in the agent and use the CLI for the final publishing path.

Automation

Use JSON in scripts and cron jobs.

Stable output, exit codes, request IDs, and idempotency make retries easier to reason about.

Coding agents

Give the agent a small public surface.

The agent can inspect state and prepare the request without learning nine provider APIs.

Get started in minutes

A command surface your agent can inspect.

Install one dependency-free client, authenticate, and let the CLI discover your workspace and connected accounts before the agent prepares anything public.

TerminalOpenPMM CLI

# Inspect the pinned first-party CLI
npx -y @openpmm/cli@0.4.0 --help

# Start browser authorization without blocking the agent.
npx -y @openpmm/cli@0.4.0 auth login --no-wait --json

# Resume after browser approval.
npx -y @openpmm/cli@0.4.0 auth login --resume --json

# Check compatibility without exposing the key
npx -y @openpmm/cli@0.4.0 doctor --json

# Discover connected accounts
npx -y @openpmm/cli@0.4.0 destinations list --json

# Give your agent a draft to work with
npx -y @openpmm/cli@0.4.0 posts create \
  --when draft \
  --channel threads \
  --body 'Draft copy' \
  --json

Why agents choose OpenPMM

Built for agents that finish the whole task.

Signup starts inside the agent

Your agent starts with only your email and Workspace name. You only finish identity and approval in the browser.

Structured output

Use stable JSON, JSONL for lists, or quiet ID-only output. Diagnostics stay on stderr.

Visible side effects

OAuth stays in the browser. Publishing, disconnecting, and destructive work require explicit confirmation.

One public contract

The CLI calls the authenticated OpenPMM /v1 API and owns its credential. Direct API clients use a separate scoped credential.

Media that just works

Upload an image or video once. OpenPMM automatically converts it to meet each destination’s requirements.

Queues without calendar math

Add a post to the next configured queue slot, choose an exact time, publish now, or keep it as a draft.

How it works

From agent intent to a reviewed public send.

01 / Discover

Check compatibility and connected accounts.

The CLI reports API compatibility, authentication, the selected Workspace, scopes, and ready Destinations without printing the key.

DiscoverOpenPMM CLI

openpmm doctor --json
openpmm destinations list --json

02 / Prepare

Upload media and create a draft.

Keep the public side effect out of the first pass. Upload the asset, create a draft for the right channel, and inspect the result as JSON.

PrepareOpenPMM CLI

openpmm assets upload ./launch.mp4 \
  --kind reel \
  --json

openpmm posts create \
  --when draft \
  --channel threads \
  --body 'We shipped it.' \
  --media-item 0:ast_... \
  --json

03 / Confirm

Review the exact send, then publish and wait.

The agent assembles the final file. A person reviews the Destination, Post version, media, and timing. The CLI accepts the send and owns bounded status checks.

ConfirmOpenPMM CLI

openpmm posts publish \
  --file approved-publication.json \
  --yes \
  --wait \
  --json

Command reference

Guessable commands. Stable output.

These are a starting point, not the whole surface. Run openpmm --help for the full command tree, and <command> --help for every flag, required scopes, side effects, output modes, and a copyable example.

openpmm posts publish --help

openpmm auth login

openpmm doctor

Check compatibility, authentication, scopes, and Destinations.

openpmm workspaces list

List the workspaces available to the current API key.

openpmm destinations list

List connected social accounts for a workspace.

openpmm destinations connect

Start a provider connection session and complete OAuth yourself.

openpmm assets upload <path>

Upload an image or video through public API operations.

openpmm posts create

Create a draft, immediate post, scheduled post, or queued post.

openpmm posts list

List drafts, scheduled posts, or published posts.

openpmm posts publish

Publish a reviewed draft with an explicit --yes confirmation.

openpmm posts wait <id>

Wait for accepted immediate publication through the CLI.

Your agent writes. OpenPMM publishes.

Give your coding agent a publish command.

The beta price starts at $1.99 per workspace for the first paid month, then $9.95. It gives your agent CLI access, unlimited immediate or scheduled posts, and your supported personal or company accounts.