setuplisted

Onboard a new Upload-Post user. Authenticate the hosted MCP server over OAuth, verify the connection, and confirm that at least one social account is connected. Use when the user first installs the plugin, asks how to get started, says the plugin is not working, or runs /upload-post:setup.
Upload-Post/upload-post-plugin · ★ 1 · AI & Automation · score 63

Install: claude install-skill Upload-Post/upload-post-plugin

# Upload-Post setup Walk the user through three checks. Stop as soon as one fails and help them fix it before moving on. ## 1. Authentication The plugin points at the hosted MCP server (`https://mcp.upload-post.com/mcp`). There is **no API key to copy and no env var to export** — the server speaks OAuth 2.1 with dynamic client registration, so Claude Code handles it. Check the connection state with `/mcp`. Expected states: - **connected** — nothing to do, move to step 2. - **needs authentication** — tell the user to run `/mcp`, select `upload-post`, and choose *Authenticate*. A browser tab opens on `app.upload-post.com/oauth/authorize`; they log in (or sign up — the free plan needs no card) and approve. The tab closes itself and the tools become available. - **failed / not listed** — the plugin may not be enabled. Have them check `/plugin` and restart Claude Code. The user can revoke access at any time from **Connected Apps** in the Upload-Post dashboard. > **API-key alternative.** Users who prefer a long-lived key (CI, headless, shared machines) can skip OAuth by adding their own MCP entry with an `Authorization: ApiKey <key>` header, or by running the stdio server `npx -y @upload-post/mcp` with `UPLOAD_POST_API_KEY`. Only bring this up if the user asks for it or OAuth is blocked in their environment. ## 2. MCP connection Call `get_account_info`. It is the cheapest call — it validates the session and returns the account state. If it succeeds, the connection is live.