TryPost

View saved version →

---
name: trypost
description: Schedules and publishes social media posts through TryPost's hosted MCP server. Use when the user wants to draft, schedule, queue, publish, approve, preview, or analyze posts on Instagram, Facebook Pages, LinkedIn (profiles and pages), X, TikTok, YouTube Shorts, Threads, Pinterest, Bluesky, Mastodon, Telegram, Discord, or Google Business Profile, or when they mention TryPost, the posting queue, approvals, ideas, labels, signatures, analytics, repurpose, or webhooks.
homepage: https://trypost.it
metadata: {"openclaw":{"emoji":"📅","requires":{"bins":[],"env":[]}}}
---

# TryPost

TryPost schedules and publishes social posts from one workspace. This plugin registers the hosted MCP server `https://app.trypost.it/mcp/trypost` (self-hosted: `{APP_URL}/mcp/trypost`).

Docs: https://docs.trypost.it/ai/tools-reference
App: https://app.trypost.it

## Connecting

- Every tool here comes from the `trypost` MCP server and is written `trypost:<tool>`. Clients may load MCP tools on demand and show them in another form, for example `trypost.list-social-accounts-tool` or `mcp__trypost__list_social_accounts_tool`. Before saying a TryPost tool is unavailable, search the client's tools for `trypost`.
- Only when that search finds no TryPost tool, or a call asks the user to sign in, is TryPost not connected: the user connects it from the client's plugin or connector settings, which opens TryPost's sign-in, where they pick the workspace to use. Never send them to the TryPost website to sign in: that does not connect the plugin. No account yet: https://app.trypost.it/register.
- The TryPost web app in a browser is not a substitute for these tools.

## Authentication

- OAuth 2.1 with Dynamic Client Registration and PKCE, scope `mcp:use`. On the first call the client opens a browser: the user signs in, picks the **workspace** this connection may use, and authorizes. Every tool acts on that one workspace; to work in another, connect again and pick it.
- API keys (Personal Access Tokens) are for the REST API only. Sent to the MCP endpoint they are refused with `403` `MCP OAuth authorization required.`
- Other HTTP errors: `401` (token missing, expired or revoked, or the bound workspace was deleted: reconnect), `403` `Workspace access denied.` (the user no longer belongs to the workspace), `402` `Active subscription required.` (TryPost Cloud account without app access; self-hosted skips this check).
- Times in arguments are ISO 8601; without an offset they are read as UTC. Post times in responses are UTC (`Y-m-d H:i:s`). No tool returns the user's own time zone; each channel's zone is `timezone` in `trypost:list-social-accounts-tool`.

## Permissions

`trypost:get-workspace-tool` returns `me.is_admin`, `me.requires_approval` and `me.publishes_directly`.

| Who | Can call |
|---|---|
| Any member | Posts (create, update, publish, preview, delete, media, notes, metrics), ideas and stages, analytics, labels, signatures, accounts and posting-schedule reads, free slots, Pinterest boards, Discord channels, TikTok creator info, Instagram audio, content types, workspace |
| Members who publish directly (owner, admins, members without approval) | Also `trypost:approve-post-tool`, `trypost:reject-post-tool`, `trypost:set-post-recurrence-tool`, `trypost:reorder-queue-tool`, `trypost:move-post-to-slot-tool`, every repurpose tool |
| Admins (and the account owner) | Also `trypost:update-posting-schedule-tool`, `trypost:generate-posting-schedule-tool`, `trypost:copy-posting-schedule-tool`, every webhook tool, every API key tool |

A refused call returns a tool error (`This action is unauthorized.`). Ids from another workspace answer as not found.

## The post model

- A post has exactly **one channel**: `social_account_id`, `content_type` and `meta` sit at the top level of the post. The channel of an existing post cannot change.
- `trypost:create-post-tool` creates one post on one channel. `trypost:create-posts-tool` creates **one indep

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: trypost-setup
description: Checks that TryPost is connected after the plugin is installed and helps the user sign in, pick a workspace and see their connected channels. Use right after installing TryPost, or when the TryPost tools are not available.
---

# TryPost setup

1. Find the TryPost tools first. Clients may load MCP tools on demand and name them differently, for example `trypost.get-workspace-tool` or `mcp__trypost__get_workspace_tool`. Search the client's tools for `trypost` before anything else. Only when the search finds none, go to step 4.
2. Call `trypost:get-workspace-tool`. When it answers, tell the user which workspace is connected and whether their posts need approval (`me.requires_approval`). If it asks the user to sign in, go to step 4.
3. Call `trypost:list-social-accounts-tool` and list the connected channels. A channel with `status` `token_expired` or `disconnected` must be reconnected in the TryPost app (Accounts). With no channel, the user connects one in the TryPost app at https://app.trypost.it: channels cannot be connected through the plugin.
4. Only when step 1 found no TryPost tool, or a call asked the user to sign in: TryPost is not connected yet. Ask the user to connect TryPost from the plugin settings: Connect opens TryPost's sign-in, where they pick the workspace this connection may use. Never send them to the TryPost website to sign in: that does not connect the plugin. No account yet: https://app.trypost.it/register.
5. To use another workspace, disconnect TryPost in the plugin settings and connect again, picking that workspace.