# Quickstart

In five minutes you will have Claude Code drafting a post in your Pickpost account, then asking you to approve it before it goes out.

You need a pickpost account with at least one connected social account (X, Threads or a Facebook Page), and [Claude Code](https://docs.claude.com/en/docs/claude-code) installed. Any other MCP client works too, see [Connect an MCP client](/guides/mcp-clients/).

## 1. Connect Claude Code

In Pickpost, open **API & MCP** in the sidebar. The **MCP server** card shows this command with your host filled in. Run it in a terminal:

```bash
claude mcp add --transport http pickpost https://your-pickpost-host/mcp
```

## 2. Sign in and choose what Claude may do

Start Claude Code and type `/mcp`, then pick `pickpost`. A browser window opens on Pickpost's sign-in page.

1. Sign in with the same account you use in the app.
2. The next page says **Authorize Claude Code** and lists what it asks for: reading your posts, editing drafts, asking to publish, asking to disconnect accounts.
3. Click **Authorize**. Claude Code now shows `pickpost` as connected.

The warning that the app is "self-declared by claude.ai" is expected: Claude Code describes itself with a document on claude.ai, and the page shows you that domain so you can check it.

:::note[No sign-in page?]
If the server runs without the sign-in service, or your client cannot sign in, use a personal API token instead: under **API tokens**, create one (it starts with `pp_` and is shown once) and add `--header "Authorization: Bearer pp_…"` to the command above.
:::

## 3. Draft a post

Ask Claude:

```text
Look at my Pickpost accounts and draft a short post announcing our new blog, for all of them.
Check it against each network's limits.
```

Claude calls `accounts_list`, `providers_limits`, `posts_create` and `posts_validate`. Drafting runs directly, so the draft shows up in Pickpost's **Posts** page while Claude is still answering. If a tab is open, it updates live.

## 4. Schedule it

Ask Claude to schedule the post for tomorrow at 9:00. This time nothing is published. `posts_schedule` needs approval, so Claude gets back `pending_approval` with a link, and Pickpost shows a toast with a **Review** button.

Click **Review**. The assistant panel opens on a conversation named after the client, for example "Requests from claude-code", with a card for the request. Click **Approve** and the post is scheduled, as if you had done it yourself. Click **Reject** and nothing happens.

If you missed the toast, the conversation is also in the assistant's history, and the link Claude got back opens it directly.

## What you did

- Claude Code signed in as you and got only the permissions you approved.
- Reads and draft edits run straight away. Scheduling, posting now and deleting always wait for you.
- The same 15 actions are available over plain HTTP. Try the [REST API guide](/guides/rest-api/) next, or browse the [tool reference](/reference/tools/).