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.How it works
MCP access on TryPost Cloud requires an active trial or subscription. New accounts get a 7-day trial automatically. 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
Authentication
TryPost’s MCP server uses OAuth 2.1 with Dynamic Client Registration (DCR), PKCE, and themcp:use scope. Modern MCP clients (Claude, Claude Code, Claude Desktop, ChatGPT, Perplexity, Cursor, Windsurf, VS Code, GitHub Copilot in IDE, Gemini CLI, OpenCode, OpenClaw, 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.
Troubleshooting
HTTP 402 — Active subscription required
HTTP 402 — Active subscription required
Your OAuth grant 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 (7-day free trial), then reconnect the MCP server. Self-hosted instances skip this check.
HTTP 401 — Unauthenticated
HTTP 401 — Unauthenticated
The OAuth session expired and refresh failed, or the access token is missing/malformed/revoked. Re-run the assistant’s connect flow to sign in again.
Server shows as “Failed to connect”
Server shows as “Failed to connect”
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; 403 → use OAuth (not an API key); anything else → open an issue on GitHub.Browser doesn't open during sign-in
Browser doesn't open during sign-in
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 a client that can finish OAuth locally, or drive TryPost through the REST API with an API key.
Next steps
Claude web
Claude on the web (claude.ai).
Claude Code
CLI assistant by Anthropic.
Claude Desktop
Desktop app by Anthropic.
ChatGPT
OpenAI ChatGPT with MCP apps.
Perplexity
Perplexity chat and Computer.
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.
OpenClaw
Personal AI assistant gateway.
Codex
CLI agent by OpenAI.
Antigravity
AI agent by Google.

