Your workflow. One API.

Bring Postede into your terminal, your agent, or your own application. Each interface works with the same projects, drafts, context and posting plans.

CLISign in from your terminal. Use focused commands or call all 29 tools with JSON.MCPConnect an agent host through OAuth and discover the tools it can use.REST APIInspect endpoints, required scopes, request schemas and response examples.

Two clients. A shared foundation.

The CLI and MCP translate commands and tool calls into the same REST contract. Postede’s API owns authorization, validation, version checks and delivery state, so your work stays consistent across clients and the dashboard.

>_ CLI

Your terminal or coding agent

◇ MCP

Your connected agent host

POSTEDE API

Consent & scopes
Project roles & review rules
Versions & exact retries

Projects & context

Drafts & posting plans

Canonical delivery queue

Controlled testing starts with a read.

The CLI is not published on npm or ready for general users. No API keys are offered; test access uses approved OAuth registrations. An existing MCP endpoint may be deployed, but that does not verify this new CLI, agent setup experience, or full project parity rollout.

Only use the setup flow when a maintainer has approved the test and supplied a preview build and matching test environment. This prompt checks those prerequisites before any installation or sign-in.

Agent setup prompt

Read https://postede.com/llms.txt. Postede integrations are a developer preview. Only proceed if I have maintainer-approved test access, an approved CLI tarball, and a registered test environment. Otherwise stop and report coming-soon status; do not install from npm. If those prerequisites are met, install that approved build, guide browser sign-in, and verify by listing my projects.