Originally published at smartpoststudio.com. Republished with a canonical link.
Not every AI assistant that "supports MCP" can actually schedule a post. ChatGPT is the big surprise: OpenAI's own help center says full MCP, the kind that can create or change things, is limited to Business, Enterprise and Edu workspaces, and on Pro a custom MCP connection gets read and fetch permissions only. That means it can tell you what's in your queue, but it can't draft or schedule. Below is the client-by-client picture for October 2026: what each assistant can do with a scheduler, how you connect it, and which ones we've documented ourselves.
A note on how to read this. Everything about third-party clients comes from each vendor's own documentation, checked on October 12, 2026, and these features change monthly. Where we say a client "should work" with Smart Post Studio, that means its documented connection method matches ours, not that we've published a tested walkthrough for it. We'll say which is which.
Before the list, here's what actually matters. MCP itself is an open standard, but clients implement different slices of it.
1. Can it reach a remote server? A scheduler's MCP server lives on the internet (ours is at https://app.smartpoststudio.com/v1/mcp). Some clients only run local servers on your own machine. All five below can reach remote ones.
2. How does it sign in? Either OAuth (a browser window opens, you log in, you pick permissions) or a token pasted into a config file as a header. OAuth is friendlier; tokens work in more places.
3. Will it call write tools? Reading your queue is a read. Creating a draft, scheduling, moving or cancelling a post are writes. This is the column that catches people out.
Can schedule: yes. Anthropic lists custom connectors using remote MCP on the Free, Pro, Max, Team and Enterprise plans, with Free accounts limited to one custom connector. On Team and Enterprise, an owner adds the connector for the organization first and members then connect individually.
How: Settings → Connectors → Add custom connector, paste the server URL, leave the OAuth client ID and secret empty, sign in, then choose permissions. This is the setup we've documented step by step on our MCP page and in the Claude setup guide.
One thing to be clear about: a free Claude account can hold the connector, but our MCP access itself is a paid Smart Post Studio feature (from the $8/month Scheduler plan). The free side of the equation is Claude's, not ours.
Can schedule: yes. It's the same OAuth sign-in, started from the terminal:
claude mcp add sps --transport http https://app.smartpoststudio.com/v1/mcp
Then run /mcp and finish the sign-in in your browser. Useful if you already live in a terminal, or want to script a weekly routine around the prompts in our seven-prompt guide.
Can schedule: yes. Cursor's docs list stdio, SSE and Streamable HTTP transports, with OAuth for the remote ones, and you add servers in mcp.json (per project or globally). Cursor also supports static headers for servers that use tokens. Cursor is one of the clients we name on our MCP page: OAuth clients sign in by adding the URL, and header-based setups use a token created under web app → AI access.
Can schedule: only on Business, Enterprise or Edu, according to OpenAI's help center. Here's the detail, because the two OpenAI pages don't read the same.
OpenAI's developer documentation describes developer mode as full MCP client support for read and write tools, available to Pro, Plus, Business, Enterprise and Education accounts on the web. You switch it on under Settings → Apps → Advanced settings → Developer mode, then use "Create app" to point at a remote server. It supports SSE and streaming HTTP, and OAuth or no authentication. There's no header-token option in that list.
The help center article, updated in October 2026, is narrower. It says full MCP support, including modify and write actions, is rolling out in beta to Business, Enterprise and Edu, and that Pro users can connect MCP servers with read and fetch permissions in developer mode. It doesn't spell out Plus separately. Until you've tested it on your own account, we'd assume an individual plan can read your queue but not change it.
Other things worth knowing from the same pages:
Where that leaves Smart Post Studio: ChatGPT's OAuth flow should be able to reach our server, since it's the same remote URL Claude uses, but we haven't published a verified ChatGPT walkthrough, and on most individual plans you'd be limited to questions like "what's scheduled this week?" anyway. If you're on a Business workspace and get it working, we'd like to hear how it went.
Can schedule: should work (we haven't documented it). VS Code stores MCP servers in mcp.json, either in your workspace (.vscode/mcp.json) or your user profile. A remote server needs a type of http and a url, and the reference documents a headers field plus an inputs array so you're prompted for a token rather than storing it in the file. Using a token from web app → AI access, that looks like:
{ "servers": { "sps": { "type": "http", "url": "https://app.smartpoststudio.com/v1/mcp", "headers": { "Authorization": "Bearer ${input:sps-token}" } } }, "inputs": [ { "id": "sps-token", "type": "promptString", "description": "Smart Post Studio token", "password": true } ] }
If you're on Copilot Business or Enterprise, your organization's "MCP servers in Copilot" policy has to be enabled first. That's the most common reason a remote server silently doesn't appear.
Can schedule: should work (we haven't documented it). Gemini CLI reads MCP servers from ~/.gemini/settings.json (or a project's .gemini/settings.json). Remote servers go in with an httpUrl, and its docs describe OAuth discovery: if the server answers with a 401, the CLI discovers the sign-in details, opens a browser, and stores the token locally. You can trigger it with /mcp auth <server-name>. For servers that use tokens instead, a headers entry works the same way as in the other clients.
| Client | Transport | Sign-in | Read + write? | Status |
|---|---|---|---|---|
| Claude (Free/Pro/Max/Team/Enterprise) | remote MCP | OAuth | yes | Documented by us |
| Claude Code | remote MCP | OAuth | yes | Documented by us |
| Cursor | remote MCP | OAuth or token headers | yes | Named on our MCP page |
| ChatGPT Business / Enterprise / Edu | remote MCP, web only | OAuth | yes, with confirmation | Not yet documented by us |
| ChatGPT Pro (and likely Plus) | remote MCP | OAuth | read and fetch only | Can check your queue, can't schedule |
| VS Code + Copilot / Gemini CLI | remote MCP | OAuth or token headers | should work | Not documented by us |
This is the part that doesn't change between clients. A confirmation dialog in ChatGPT, or permission checkboxes in Claude, are the client's safety features. What the assistant is able to do is decided by the scheduler's server. In Smart Post Studio's case: there's no "post now" tool for any client, anything an assistant schedules must be at least ten minutes out, it shows in your Queue with an AI badge, and it's written to your account history. There's a cap of 100 AI-created posts a day and 30 requests a minute. Each connection appears under AI access, lasts 90 days, and stops working the moment you delete it.
That ten-minute window is a chance to intervene, not an approval step. A scheduled post goes out at its time whether you looked at it or not. If you want the background on why we built it that way, MCP for people who don't code covers it without the jargon.
And if you're still choosing a scheduler rather than a client, our comparison of schedulers that speak MCP is honest about who's cheaper. Buffer, for one, lists Claude, ChatGPT and Cursor integrations on its free plan. The 2026 scheduler pricing study has the rest of the numbers.
TL;DR: Claude (including a free account), Claude Code and Cursor can all read and schedule over MCP today, and they're the clients we've documented. ChatGPT can too, but OpenAI's help center limits write access to Business, Enterprise and Edu. On Pro it's read and fetch only, so it can check your queue but not fill it. VS Code with Copilot and Gemini CLI both support remote servers with OAuth or token headers and should work, though we haven't published a walkthrough. Whatever the client, the scheduler's server sets the real limits.
Config files, copy-paste ready: every client setup in this post (Claude, Claude Code, Cursor, VS Code, Gemini CLI) lives as a file in our public GitHub repo, alongside a week of example prompts.