> ## Documentation Index
> Fetch the complete documentation index at: https://docs.postonce.to/llms.txt
> Use this file to discover all available pages before exploring further.

# PostOnce MCP

> Connect PostOnce to Claude, Codex, and other MCP clients to create posts, upload media, and manage workflows with your PostOnce API key.

The PostOnce MCP lets MCP-compatible clients create posts, upload media, and manage workflows through the PostOnce Public API.

* Endpoint: `https://postonce.to/mcp`
* Auth: `Authorization: Bearer <PostOnce API key>`
* Transport: Streamable HTTP

The hosted MCP does not store your API key. It forwards the bearer token you send to the PostOnce Public API for each request.

## Prerequisites

Before you connect the PostOnce MCP, make sure you have:

* a PostOnce API key from the [dashboard preferences page](https://postonce.to/dashboard/preferences)
* at least one active connected social account in [the dashboard](https://postonce.to/dashboard/accounts)
* a plan that includes Public API access. See [plans](https://postonce.to/#pricing)
* a real local file path if you want to use the media helper tools

## Setup for Claude Desktop

Add a custom MCP server in Claude Desktop and use this config:

```json theme={null}
{
  "mcpServers": {
    "postonce": {
      "type": "http",
      "url": "https://postonce.to/mcp",
      "headers": {
        "Authorization": "Bearer po_live_your_api_key"
      }
    }
  }
}
```

After saving the config, restart Claude Desktop and start using the `postonce` tools.

## Setup for Claude Code

Add the PostOnce MCP to your Claude Code MCP settings:

```json theme={null}
{
  "mcpServers": {
    "postonce": {
      "type": "http",
      "url": "https://postonce.to/mcp",
      "headers": {
        "Authorization": "Bearer po_live_your_api_key"
      }
    }
  }
}
```

Use your PostOnce API key as the bearer token exactly as shown above.

Create and manage API keys in the [dashboard preferences page](https://postonce.to/dashboard/preferences).

## Setup for Codex

Add the PostOnce MCP to your Codex MCP configuration:

```json theme={null}
{
  "mcpServers": {
    "postonce": {
      "type": "http",
      "url": "https://postonce.to/mcp",
      "headers": {
        "Authorization": "Bearer po_live_your_api_key"
      }
    }
  }
}
```

Once added, Codex can call the PostOnce MCP directly from your workspace.

## Setup for other MCP clients

Any MCP client that supports HTTP transport can connect directly with:

* Endpoint: `https://postonce.to/mcp`
* Auth header: `Authorization: Bearer po_live_your_api_key`
* Transport: HTTP (Streamable HTTP)

## Quick start

Use this sequence to verify the connection:

1. `list_active_accounts`
2. `create_post`
3. `get_post`
4. `create_workflow`
5. `delete_workflow`

For media posting:

1. `upload_media_from_path`
2. `create_media_post_from_path`

## Common tools

| Tool                          | What it does                                                                          |
| ----------------------------- | ------------------------------------------------------------------------------------- |
| `list_active_accounts`        | Returns active connected social accounts you can post to right now.                   |
| `create_post`                 | Creates a text or media-backed post for one or more target accounts.                  |
| `get_post`                    | Returns the aggregate post status and per-target delivery details.                    |
| `upload_media_from_path`      | Uploads a local image or video file and returns a reusable media object.              |
| `create_media_post_from_path` | Uploads a local file and creates a post in one flow.                                  |
| `create_workflow`             | Creates a workflow that republishes content from a source account to target accounts. |
| `delete_workflow`             | Deletes a workflow you no longer need.                                                |

## Good to know

* Media helper tools require a real local file path.
* Generic chat attachments only work if your MCP client exposes them as local files or URLs.
* `create_media_post_from_path` supports a single image or video file per call.
* The MCP uses your PostOnce account permissions, so available tools and actions depend on your API key scopes and connected accounts.

## Ready to connect?

<CardGroup cols={2}>
  <Card title="Get API keys" icon="key" href="https://postonce.to/dashboard/preferences">
    Open your dashboard preferences to create or manage a PostOnce API key for MCP access.
  </Card>

  <Card title="View plans" icon="badge-dollar-sign" href="https://postonce.to/#pricing">
    Check which PostOnce plans include Public API access before you connect the MCP.
  </Card>
</CardGroup>