Skip to main content
TryPost provides a built-in MCP (Model Context Protocol) server that lets AI coding assistants manage your social media scheduling directly. Your AI assistant can create and publish posts, manage signatures and labels, fetch metrics, and more — all through natural language.

What is MCP?

MCP is an open protocol that connects AI assistants to external tools and data sources. Instead of copying and pasting API calls, your AI assistant can interact with TryPost directly.

Available tools

TryPost exposes a full set of MCP tools for end-to-end content workflows. See the Tools reference for parameters and examples.
CategoryToolsDescription
PostsList, Get, Create, Update, Publish, Delete, Attach Media from URL, Request Media Upload, Attach Media from Upload, Preview, Get MetricsCreate, schedule, publish, and analyze posts across all connected platforms — including local-file uploads via signed URLs
PlatformsList Content TypesDiscover valid content_type values and per-platform limits
SignaturesList, Create, Update, DeleteManage reusable text blocks (hashtag sets, CTAs, link callouts)
LabelsList, Create, Update, DeleteManage color-coded labels for organizing posts
Social AccountsList, ToggleView connected accounts and toggle active/inactive
WorkspaceGetGet current workspace details
API KeysList, Create, DeleteManage API keys

How it works

MCP access on TryPost Cloud requires an active trial or subscription. New accounts get a 7-day trial automatically — no credit card required to start. See Plans & billing for details. Self-hosted instances skip this check.
1

Add the TryPost MCP server in your assistant

Use your assistant’s MCP configuration to add a remote HTTP server pointing to https://app.trypost.it/mcp/trypost. Each client guide below has the exact command or settings file.
2

Sign in through your browser

The first time the assistant calls a tool, TryPost opens a browser window asking you to sign in and authorize the connection. Click Allow and you’re done — the assistant holds the OAuth token from then on, with automatic refresh.
3

Start using natural language

Ask your assistant to manage your TryPost account. For example: “Create a new post for LinkedIn next Tuesday at 9am” or “List all my scheduled posts.”

Server URL

https://app.trypost.it/mcp/trypost

Authentication

TryPost’s MCP server uses OAuth 2.1 with Dynamic Client Registration (DCR), PKCE, and the mcp:use scope. Modern MCP clients (Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, GitHub Copilot in IDE, Gemini CLI, OpenCode, Codex) detect this automatically from the .well-known discovery endpoints — you only point them at the URL and the browser sign-in handles the rest.
If your environment can’t open a browser — for example a CI pipeline, the GitHub Copilot cloud coding agent, or a client that doesn’t speak OAuth yet — you can authenticate with a Personal Access Token instead. Create one in Settings > API Keys on the TryPost dashboard and send it as Authorization: Bearer YOUR_API_KEY. The same token works for both the REST API and the MCP endpoint.Keep the token in a secret store, not committed to source. Rotate from Settings > API Keys if a key leaks.

Troubleshooting

Your token is valid and the config is correct — the account behind it just doesn’t have an active trial or subscription. Open app.trypost.it, start a trial or pick a plan (no card required to start the trial), then reconnect the MCP server. Self-hosted instances skip this check.
The OAuth session expired and refresh failed, or (in the Bearer fallback) the token is missing/malformed/revoked. Re-run the assistant’s connect flow to re-authenticate, or issue a new PAT from Settings > API Keys.
Run the connection probe your assistant exposes (for example claude mcp list). The HTTP status from the probe tells you which case you’re in: 402 → see above; 401 → re-authenticate; anything else → open an issue on GitHub.
Some clients print the authorize URL to the terminal instead of launching the browser when running over SSH or inside a container. Copy the URL into a local browser, complete the flow, and the assistant will pick up the callback automatically. If the callback port is blocked, use the Bearer fallback.

Next steps

Claude Code

CLI assistant by Anthropic.

Claude Desktop

Desktop app by Anthropic.

Cursor

AI-powered code editor.

Windsurf

Editor with Cascade AI.

VS Code

Native MCP support in Copilot Chat.

GitHub Copilot

Copilot agent mode.

Gemini CLI

CLI assistant by Google.

OpenCode

Open-source CLI assistant.

Codex

CLI agent by OpenAI.

Antigravity

AI agent by Google.