# How to Connect PostEverywhere to Grok Bot > Grok cannot post to social media on its own. Add PostEverywhere as a custom connector at grok.com/connectors and Grok can draft, schedule and publish across all top platforms. One URL, nothing to install. **Source:** https://posteverywhere.ai/blog/connect-grok-to-social-media **Author:** Jamie Partridge **Published:** 2026-09-11 --- Grok is fast. That is the whole point of it: something is happening right now, you want a take on it, and you want the take out before it stops mattering. What Grok cannot do, on its own, is publish. It will write you a sharp post and then leave you to carry it into a scheduler by hand, which is exactly the step that costs you the moment you were trying to catch. A connector fixes that. Connect PostEverywhere to Grok at `grok.com/connectors` and Grok gains real publishing tools: draft, schedule, publish, check what is queued, read back what performed. > "Something is trending in our category right now. Draft a take and schedule it for the next busy hour." Grok calls PostEverywhere, the post lands in the queue, and you never leave the conversation. This guide walks through connecting PostEverywhere to Grok end to end. [PostEverywhere](/agents) runs the hosted MCP server that Grok connects to, and it holds the authorised connections to each network. It takes about a minute on a personal plan. *Written by Jamie Partridge, Founder.* ## Table of Contents 1. [What you need to connect PostEverywhere to Grok](#what-you-need-to-connect-posteverywhere-to-grok) 2. [Why Grok needs PostEverywhere to post at all](#why-grok-needs-posteverywhere-to-post-at-all) 3. [Step-by-step: connect PostEverywhere to Grok](#step-by-step-connect-posteverywhere-to-grok) 4. [Three PostEverywhere prompts to try in Grok](#three-posteverywhere-prompts-to-try-in-grok) 5. [What Grok can actually do with your PostEverywhere accounts](#what-grok-can-actually-do-with-your-posteverywhere-accounts) 6. [PostEverywhere Grok connector troubleshooting](#posteverywhere-grok-connector-troubleshooting) 7. [When to use Grok rather than another assistant](#when-to-use-grok-rather-than-another-assistant) 8. [Connect PostEverywhere to your other assistants](#connect-posteverywhere-to-your-other-assistants) 9. [FAQs](#faqs) ## What you need to connect PostEverywhere to Grok Three things, and one of them depends on your plan: **1. A Grok account.** On personal plans you can add a custom connector yourself, immediately, with no admin involved. On Grok Business or Enterprise a team admin has to provision it first in the cloud console at `console.x.ai`, under Grok Business, then Connectors, then Add Connector, then Other. If the New Connector option is greyed out for you, that is why. You are not doing it wrong; you need someone with admin rights. **2. A PostEverywhere account with at least one connected social account.** Every plan from Lite ($9/mo) includes the full API and the hosted MCP server, and there is no separate developer tier. The [7-day free trial](/pricing) covers the whole thing, though a card is required to start it and there is no free plan. Connect the accounts you want Grok to publish to first, because the connector can only ever reach accounts you have already authorised. **3. About a minute.** There is nothing to install and no config file to edit. > **Want the fastest possible start?** [Start a 7-day free trial](https://app.posteverywhere.ai/signup), connect two or three accounts, and have Grok scheduling before the news cycle moves on. Card required, $0 charged today, cancel anytime. ## Why Grok needs PostEverywhere to post at all It is worth being precise about what connects to what, because most writing on this topic is vague about it. Grok has no social media integrations of its own. It does not hold your Instagram login, it has no relationship with the LinkedIn API, and connecting it to "social media" is not a thing you can do directly. What you can do is give it a connector: an external server exposing tools it is allowed to call. That standard is the Model Context Protocol (MCP), originally proposed by Anthropic in 2024 and since adopted across the industry, including by OpenAI's agent stack and by xAI, whose developer documentation covers the wider platform. So the chain has three links, and the middle one is the part that does the work: **Grok reasons. PostEverywhere publishes. The platform receives.** The [PostEverywhere MCP server](https://www.npmjs.com/package/@posteverywhere/mcp) exposes 38 tools covering scheduling, publishing, media upload, [AI image generation](/ai-image-generator), account health, campaigns, webhooks and [analytics](/social-media-analytics). Underneath, it talks to each platform's official API. That distinction matters more than it sounds: your accounts stay compliant, nothing is scraped, and no password ever enters the conversation. Grok keeps the connector on your account rather than your device, so it follows you between the web app and the phone apps. Add it once on either and it is available on both. ## Step-by-step: connect PostEverywhere to Grok Nothing to install. The connector lives in your Grok account, not on your machine. ### Step 1: Open Connectors in Grok Go to `grok.com/connectors`. On the phone apps it lives under **Settings**, then **Connectors**, rather than at that URL, but it is the same flow and the same server. ### Step 2: Add a custom connector Click **New Connector**, then select **Custom**. ### Step 3: Paste the server URL ``` https://mcp.posteverywhere.ai ``` There is no client ID or secret to hunt down, and no API key to copy and paste on this path. The server handles sign-in itself. ### Step 4: Complete the sign-in A browser window opens on PostEverywhere's sign-in page. Log in with your normal account and approve. One known quirk: **if the popup hangs on "Connecting", close it and try once more.** This is a wrinkle in the Grok connector flow rather than a fault in the server, and the second attempt almost always completes. ### Step 5: Run a sanity check Start a new conversation and ask: > "Show me my connected social accounts on PostEverywhere." Grok calls the `list_accounts` tool and returns your linked platforms with their status. If you see your accounts, you are live. > **Prefer to see the tools before connecting?** The [MCP server page](/mcp) lists all 38 tools by group, and the [connectors page](/connectors) covers the per-assistant setup, including the prerequisite each one hides behind. ## Three PostEverywhere prompts to try in Grok Once PostEverywhere is connected, plain language is the interface. Grok suits the fast turnaround in particular, so these lean that way: **1. The reaction post.** > "Something is trending about our category right now. Draft a take and schedule it for the next busy hour." Grok drafts to the moment and queues it, rather than leaving you to paste it somewhere else while the moment passes. Pair it with our [best time to post](/best-time-to-post) data if you want the slot chosen for you. **2. The split-speed publish.** > "Post this to X now and schedule the same thing for LinkedIn and Threads this afternoon." It publishes immediately where timing matters and queues the slower platforms separately. That is [cross-posting](/cross-posting) with different urgency per platform, driven from one message. **3. The week in review.** > "What did we post this week and which one actually landed?" It reads back the week with engagement figures, so you can ask for more of whatever worked. ## What Grok can actually do with your PostEverywhere accounts The connection carries the same 38 tools every MCP client gets. In practice they group into a few jobs: **Publishing.** Create posts, schedule them for any future time, publish immediately, and cross-post to any combination of your connected accounts across all top platforms. Everything goes through each network's official API with per-platform formatting, and [bulk scheduling](/bulk-scheduling) is available when one prompt fans out into many posts. **Media.** Upload images and video from a URL in one call, or generate images with the built-in tools. Credits come with every plan. **Account management.** List accounts and check connection health before posting, so an expired token never silently eats a scheduled post. **Measurement.** Pull engagement and reach across platforms, straight into the conversation where Grok can actually reason about them. What the connector deliberately does **not** do is act unprompted. Grok drafts and schedules when asked, and everything queued is visible in your [content calendar](/social-media-calendar) before it goes. It also does not give Grok access to your X account beyond what you have authorised in PostEverywhere, and it cannot read replies or run an inbox. Publishing and reporting only. For the permissions model behind any assistant connection, [how to give an agent access safely](/blog/ai-agent-access-to-social-media) covers what to grant and what to withhold. ## PostEverywhere Grok connector troubleshooting **The popup hangs on "Connecting".** Close it and try again. Known quirk of the Grok flow; the second attempt almost always completes. **New Connector is greyed out.** You are on Business or Enterprise, where an admin has to provision the connector in the cloud console first. On personal plans the option is available immediately. **Grok answers but never schedules anything.** Name the action. Say *schedule* rather than *write*, and give it a time. Otherwise it will happily produce the text and stop there, which is the single most common thing people mistake for a broken connector. **A scheduled post failed.** Ask Grok to check account health, or to retry. The usual culprit is an expired platform token, and the fix is reconnecting that account in the dashboard. **You want to disconnect.** Remove the connector in Grok and revoke access from your PostEverywhere dashboard as well. Belt and braces. ## When to use Grok rather than another assistant Grok fits the fast turnaround. When something is happening now and the post needs to be out before it stops mattering, it is quicker than opening a dashboard, and quicker than the assistants that want to discuss the brief first. For longer work the trade-offs go the other way. If you are holding a brand voice across a week of planned content, [Claude](/blog/connect-claude-to-social-media) keeps a style guide in a Project and writes against it. If your team already lives in ChatGPT, [the Developer Mode connector](/blog/connect-chatgpt-to-social-media) puts the same tools there. If you work in a terminal, [Claude Code](/blog/how-to-use-posteverywhere-with-claude-code-mcp) speaks the same protocol with one command. There is no wrong answer, and no need to pick just one. The connector is per-assistant; the PostEverywhere account is one; the queue they publish into is shared. Our roundup of the [best social media scheduling tools for AI agents](/blog/best-social-media-scheduling-tools-for-ai-agents) maps how the wider field compares on this, and [which social tools run MCP servers](/blog/social-media-mcp-servers) covers who else has one at all. ## Connect PostEverywhere to your other assistants PostEverywhere runs one hosted MCP server, so the same account and the same key drive every client. Only the setup step differs, which is why each assistant gets its own walkthrough: | Assistant | How it connects | Guide | |---|---|---| | **ChatGPT** | Custom connector in Developer Mode, Plus and above | [Connect PostEverywhere to ChatGPT](/blog/connect-chatgpt-to-social-media) | | **Claude** | Browser sign-in, no API key, works on the Free plan | [Connect PostEverywhere to Claude](/blog/connect-claude-to-social-media) | | **Claude Code** | One `claude mcp add` command in the terminal | [PostEverywhere with Claude Code](/blog/how-to-use-posteverywhere-with-claude-code-mcp) | | **Gemini** | CLI and API today; the app cannot add connectors yet | [Connect PostEverywhere to Gemini](/blog/connect-gemini-to-social-media) | | **Grok** | Custom connector at grok.com/connectors | You are reading it | | **Cursor, Codex, Windsurf, Cline, Zed** | The same JSON config block | [All connectors](/connectors) | | **Your own agent** | REST API, Node SDK or CLI, all on one key | [Social media API](/social-media-api) | They all publish into the same queue and the same [content calendar](/social-media-calendar), so running Grok for reactions and Claude for planned content against a single PostEverywhere workspace is normal, not a workaround. The full tool surface is on the [MCP server page](/mcp), and [the agents page](/agents) covers the patterns people build on top of it. ## FAQs ### What am I actually connecting Grok to? PostEverywhere. Grok has no social integrations of its own, so it never talks to Instagram or LinkedIn directly. The custom connector points Grok at the PostEverywhere MCP server, and PostEverywhere holds the authorised account connections and publishes through each platform's official API. Grok reasons, PostEverywhere publishes, the platform receives. ### Can Grok really post to Instagram, TikTok and LinkedIn? Yes, through the connector, using each platform's official API. With PostEverywhere connected, Grok can create, schedule and publish to Instagram, LinkedIn, TikTok, YouTube, Facebook, X, Threads, Pinterest, [Bluesky](/bluesky-scheduler), [Telegram](/telegram-scheduler) and Discord. Nothing is scraped and no passwords are shared. ### Do I need to know how to code? No. The setup is: open Connectors, click New Connector, select Custom, paste one URL, sign in. There is no code, no terminal and nothing to install. The coding paths exist for people building products, not for using the connector. ### Why is New Connector greyed out on my work account? On Grok Business or Enterprise a team admin has to provision the connector first, in the cloud console at `console.x.ai`. Until they do you cannot add it yourself, whichever menu you use. On personal plans the option is available straight away. ### Can I add the connector from the Grok phone app? Yes. On the phone apps it lives under Settings, then Connectors, rather than at `grok.com/connectors`, but it is the same flow and the same server. Grok keeps the connector on your account rather than your device, so adding it in one place makes it available in both. ### Does this cost extra on the PostEverywhere side? No. API and MCP access are included on every plan from $9/mo. Grok connectors are free to add on personal plans. There is a 7-day free trial that covers everything, though a card is required to start it and there is no free plan. ### Is it safe to connect Grok to my social accounts? The connector never sees your social passwords. It authenticates through sign-in, every action flows through official platform APIs with the permissions you granted PostEverywhere, and you can revoke access at any time from your dashboard. It also cannot publish unprompted, so nothing goes out that you did not ask for. ### Can I connect Grok and another assistant at the same time? Yes. The hosted server accepts any number of MCP clients. Running Grok for fast reactions and [Claude](/blog/connect-claude-to-social-media) or [ChatGPT](/blog/connect-chatgpt-to-social-media) for planned content against the same PostEverywhere workspace is a common setup, and they share one queue and one calendar. --- The gap between "Grok writes a sharp take" and "the take is live on every account" turned out to be one URL. Add it once, and the slowest part of reacting to anything stops being your job. [Start your 7-day free trial](https://app.posteverywhere.ai/signup) and have Grok scheduling before the moment passes. For the architecture choice between assistant-driven MCP and code-driven REST, see [API vs MCP](/blog/social-media-api-vs-mcp). If you would rather drive the whole thing from your own code, the [REST API](/social-media-api) and the [developer docs](/developers) cover the same surface the connector sits on.