Skip to main content
Grok is xAI’s assistant. Add TryPost as a custom MCP connector and you can schedule, publish, and manage social posts from a normal Grok chat — on the web, iOS, or Android. This page is for Grok chat connectors. It is not the Grok Build CLI (grok mcp add) and not the xAI API Remote MCP tools. Those are separate products.
TryPost is not in Grok’s built-in or catalog connectors. You add it yourself: New Connector → Custom, then paste the TryPost MCP URL.

​
Prerequisites

​
Server URL

Use this exact URL. Do not add a trailing slash. Do not paste an OAuth authorize URL.

​
Setup

1

Open Connectors

On the web, go to grok.com/connectors.You can also start from a chat: click + → Connectors → + Add connector.On iOS and Android, open Settings → Connectors.
2

Add a custom connector

Click New Connector, then select Custom.Paste the MCP server URL:
Name it TryPost if Grok asks for a name.If Grok shows OAuth client fields (Client ID, Client Secret, authorize/token URLs), leave them empty. TryPost uses OAuth 2.1 with Dynamic Client Registration. Grok discovers the endpoints from the MCP URL and registers itself.
3

Sign in to TryPost

Grok then asks you to authenticate. Complete the browser sign-in.
  1. Sign in to your TryPost account
  2. Review the permissions
  3. Click Allow
After that, Grok discovers the TryPost tools and makes them available in conversations — the same way it uses built-in and catalog connectors. You do not need to paste an API key.
4

Ask Grok to use TryPost

Open a new chat and ask in plain language. For example:
Grok should call TryPost tools instead of guessing. If it answers without tools, say you want it to use the TryPost connector.See the Tools reference for every tool and the recommended create → attach media → publish workflow.

​
Authentication

TryPost MCP accepts OAuth only — a browser sign-in with the mcp:use scope. Personal Access Tokens from Settings → API Keys work on the REST API, not on /mcp/trypost.
If Grok offers an API key or bearer-token field, leave it blank and finish the OAuth prompt instead. A pasted API key returns 403 MCP OAuth authorization required.
Manage connected assistants later under workspace Settings → MCP in TryPost.

​
What you can do

Once the connector is authorized, Grok can: Pinterest needs a board_id, Discord needs a channel_id, and TikTok needs a privacy_level before you publish. Ask Grok to list boards or channels first. Details and tool names: Tools reference.

​
Self-hosted

Grok reaches the MCP server from xAI’s cloud, not from your phone or browser. localhost, 127.0.0.1, and private LAN addresses are rejected.
Point the custom connector at your instance:
Example: https://trypost.yourdomain.com/mcp/trypost.The URL must be reachable on the public internet over HTTPS. If the app only runs on your machine, expose it with a tunnel first — xAI’s custom MCP tunneling guide covers ngrok and Cloudflare Tunnel. After you authorize, Grok still opens the TryPost OAuth screen on your instance. Do not put a Personal Access Token in the connector.

​
Grok Business and Enterprise

On these plans, members cannot add a custom connector until a team admin provisions it.
  1. Sign in to console.x.ai, select your team, and open Grok Business → Connectors
  2. Click + Add Connector → Other
  3. Paste https://app.trypost.it/mcp/trypost (or your self-hosted {APP_URL}/mcp/trypost)
  4. Finish the TryPost sign-in if Grok asks
Adding and removing connectors requires Team Read-Write permissions. xAI’s connector management page has the full admin flow.After the admin adds it, each member still opens grok.com/connectors and signs in to their own TryPost account. The admin step only makes the connector available; it does not share one TryPost login across the team.

​
Troubleshooting

You may have pasted the wrong URL. Use https://app.trypost.it/mcp/trypost — not /oauth/authorize, not /api, and not a trailing slash. Remove the connector and add it again, then allow pop-ups so the OAuth window can open.
Finish OAuth. Grok can list a custom server before you have authorized it. Open grok.com/connectors, connect TryPost, and click Allow on the TryPost screen. Then start a new chat and ask it to use the TryPost connector.
Cloud TryPost is already public. If you self-host, Grok must reach the URL from the internet. localhost and private IPs fail. Use a public HTTPS URL or a tunnel.
The OAuth grant worked; the TryPost account is not active. Open app.trypost.it, activate the account, then reconnect the connector. Self-hosted instances skip this check. See Introduction.
The OAuth session expired or was revoked. Open the connector and complete sign-in again.
The request used an API key (Personal Access Token) or an OAuth token without mcp:use. Remove any bearer token from the connector and sign in with OAuth.
On Grok Business / Enterprise, only an admin can provision custom MCP. Ask someone with Team Read-Write to add TryPost in console.x.ai first. On personal Grok, open grok.com/connectors and choose Custom, not a catalog app.

​
Example prompts