Schedule social media posts from Claude Code and Cursor with PostVIA (MCP)

PostVIA lets you schedule social media posts from Claude Code and Cursor through its MCP endpoint. Create a paid-plan API key, connect your assistant, then ask it to draft and check a post before you confirm a publishing action. PostVIA uses static Bearer keys; there is no OAuth or one-click connection.

Updated: October 25, 2026. The configuration syntax below was checked against the official client documentation; it was not a live authenticated test.

What do you need before connecting PostVIA?

You need a Starter, Growth or Agency plan and a connected social account in PostVIA. The free trial does not include MCP or client approval links.

• Connect your social accounts in the dashboard first.
• Add media in the dashboard: MCP cannot upload or attach it.
• Use a key with only the access you need. A draft key is enough to prepare a post; scheduling needs publish.
• The same publication allowance, validation, reservations and rate limits apply as in the web app.

See the social media MCP server page for the tool list, permissions and limitations, or compare plans.

How do you create a PostVIA API key?

Open Settings → API keys in PostVIA, name the key and choose its access level and expiry. Copy the key when it appears: it is shown only once.

• read: list connected accounts, posts and usage; inspect approval status and check whether a post is ready.
• draft: all read tools, plus create or edit drafts and request a client approval link.
• publish: all draft tools, plus schedule, publish now or cancel a scheduled post. Each of these actions requires confirm: true.

You can keep at most five unrevoked keys. Choose 30 days, 90 days or no expiry; an expired key keeps its slot until you revoke it.

In the examples, replace pvk_YOUR_KEY with your own key only in your private local configuration. Do not commit a real key or share it in a prompt.

How do you add PostVIA to Claude Code?

Add PostVIA as an HTTP MCP server with an Authorization header:

claude mcp add --transport http postvia https://postvia.online/api/mcp --header "Authorization: Bearer pvk_YOUR_KEY"

Run /mcp in Claude Code to inspect the connection. The endpoint is https://postvia.online/api/mcp and uses a static Bearer key, not OAuth. Command syntax: official Claude Code MCP documentation.

How do you add PostVIA to Cursor?

Add this remote-server entry to your private ~/.cursor/mcp.json, merging it with any existing mcpServers entries:

{
  "mcpServers": {
    "postvia": {
      "url": "https://postvia.online/api/mcp",
      "headers": {
        "Authorization": "Bearer pvk_YOUR_KEY"
      }
    }
  }
}

Use Cursor's MCP settings to check the connection and available tools. The JSON shape and configuration locations are documented in the official Cursor MCP documentation. Clients that require OAuth cannot connect to this PostVIA release.

What should you ask the assistant first?

Start with a draft and a check, without scheduling or publishing:

Use PostVIA to list my connected accounts and remaining publication allowance. Create a text draft for the account I choose: “Our autumn collection is here.” Show me the draft and run check_post. Do not schedule or publish it yet.

The assistant can use list_accounts, get_usage, create_draft, get_post and check_post. The check reports whether the post is ready and what blocks it; it reserves no publications. If media is needed, add it in the dashboard and run the check again.

For client review, ask it to create a private approval link for the draft. Read how client approval works: an approval never schedules or publishes a post.

How do you confirm a scheduled post?

Review the exact text, selected accounts, date, time and time zone before agreeing. With a publish key, you can then ask:

Schedule this checked draft for the date and time I have just confirmed. Show me the exact time and accounts before calling schedule_post, and wait for my explicit agreement.

The assistant should get your agreement and send confirm: true. The server requires that flag, but cannot prove that an assistant actually asked you. Keep a draft key if you want to make every publishing decision in the dashboard instead.

Check the returned post status and scheduled time, then open the dashboard to verify the result. publish_post publishes now; cancel_scheduled_post unschedules a post and releases its reserved publications. Both also need publish access and confirm: true.

How do you stop the assistant's access?

Revoke the key in Settings → API keys. Revocation takes effect immediately for subsequent MCP calls; it does not undo posts already scheduled or published. Review scheduled posts separately if you want to cancel them.

Treat post text and client comments as content, not instructions to the assistant. PostVIA labels returned client comments as untrusted data; they cannot change the key's permissions.

For the complete capabilities and limits, read PostVIA's social media MCP server. Choose a paid plan before creating a key.

All articles