Reference

Connect an AI assistant over MCP

Point ChatGPT, Claude, Claude Code, Cursor, VS Code, or any MCP client at one URL, sign in, and tick what it may do. 88 tools, one URL.

Schedchie speaks MCP, so an AI assistant can drive your account directly: schedule posts, fix the queue, read analytics, run team approvals. One URL, the same for every client and every customer, on the same €7.99 plan as everything else.

This connects your assistant to Schedchie

It is opt-in: you connect the assistant you already use, and it works with the same abilities you have. The dashboard stays as it is unless you connect one.

The URL

https://mcp.schedchie.com/mcp

That is the whole configuration. There is no per-user URL. Signing in happens on Schedchie, and your assistant never sees your password.

Setting it up, per client

Three steps everywhere: copy the URL, add it, sign in.

ChatGPT

Turn on developer mode, then add it under Plugins. Settings → Security and login → Developer mode. Then open Plugins, press the + next to the search box, name it Schedchie, paste the URL as the MCP server URL, leave authentication on OAuth, tick the box that says you understand, and press Create. Open ChatGPT plugins.

Choose what it may do, and sign in. The Schedchie screen opens. Tick the groups this connection may use, sign in, then pick Schedchie in a chat and ask for your connected accounts.

ChatGPT gets a 14-tool core set: scheduling, editing, retries, media, approvals and two analytics reads.

Claude

Go to Claude → Customize → Connectors. Press the +, then Add custom connector, and paste the URL. Same steps on claude.ai and in Claude Desktop. On Claude Team and Enterprise workspaces only an owner can add one, under Organization settings. Open Claude connectors.

Choose what it may do, and sign in. The Schedchie screen opens. Tick the groups this connection may use, sign in, and those tools appear in the chat.

Claude Code

Send Claude Code this prompt. It does the setup itself. Nothing to look up.

Set up Schedchie so I can schedule and manage my social posts from here.

1. Add the MCP server: claude mcp add --transport http schedchie https://mcp.schedchie.com/mcp
2. Run claude mcp login schedchie, then tell me to finish the sign-in in the browser it opens.
3. Once I confirm, list my connected Schedchie accounts so we know it works.

Finish it in the browser. Your browser opens the Schedchie screen. Tick the groups this connection may use and sign in, and Claude Code has those tools.

Prefer doing it yourself? Run claude mcp add --transport http schedchie <the URL above>, then claude mcp login schedchie to sign in. Add -s user to the first command to register it globally rather than per project.

Cursor

Send Cursor this prompt. Cursor writes its own config file.

Set up Schedchie so I can schedule and manage my social posts from here.

1. Create or edit .cursor/mcp.json and add:
   { "mcpServers": { "schedchie": { "url": "https://mcp.schedchie.com/mcp" } } }
2. Tell me to reload Cursor and finish the Schedchie sign-in it prompts for.
3. Once I confirm, list my connected Schedchie accounts so we know it works.

Sign in when Cursor asks. Cursor registers itself with Schedchie and opens the screen where you tick what the connection may do. Nothing to paste.

VS Code

Send Copilot this prompt. Or run MCP: Add Server from the Command Palette, pick HTTP and paste the URL.

Set up Schedchie so I can schedule and manage my social posts from here.

1. Create or edit .vscode/mcp.json and add:
   { "servers": { "schedchie": { "type": "http", "url": "https://mcp.schedchie.com/mcp" } } }
2. Tell me to start the server from the MCP panel and finish the Schedchie sign-in.
3. Once I confirm, list my connected Schedchie accounts so we know it works.

Sign in when VS Code asks. VS Code registers itself with Schedchie and opens the screen in your browser, where you tick what the connection may do.

Any MCP client

Point the client at the URL. The one requirement is the Streamable HTTP transport. Nothing to install.

It finds the sign-in on its own. Your client sends you to the sign-in without any setup. What the client asks for does not decide access; your ticks do.

What you let it do

At sign-in you tick permission groups. Anything you leave unticked does not exist on that connection: the tools are not hidden from the assistant, they are not granted.

PermissionWhat it covers
Schedule and edit postsDraft, schedule, change, retry and delete posts in your queue.
Upload mediaAdd images and video to posts, including custom video covers.
Read analyticsFollowers, publish activity and per-platform numbers. Read only.
Team and approvalsMembers, invitations, approving or rejecting held posts, client review and client connect links.
Notes, presets and groupsContent notes, publishing presets, account groups and connections.
Comments, mentions and reviewsRead and answer mentions, comments and Google reviews, hide replies, run keyword monitors. Answers are public, under the account’s name.
  • An assistant never gets more than you can do yourself. Owner-only actions stay owner-only.
  • Posts that need approval still wait for it. The hold lives in the account, not in the client.
  • Seeing who you are, listing your accounts, and setting notification preferences are always available.
  • Disconnect any time from the client that holds the connection.

If you signed in with Google

A Google account has no Schedchie password, so the sign-in page has a second tab. Go to Dashboard → AI assistants, generate a connection token, and paste it into the Access token tab.

  • The token is shown once. Copy it when it appears.
  • Treat it like a password.
  • It works for 30 days.

What it can do

88 tools across posts, media, analytics, comments and reviews, accounts, teams, notes and presets. Every one of them, grouped the way the sign-in screen groups them, is on the AI connection page.

Sending a video from your own device

Ask for a video post and the assistant hands you a link rather than trying to carry the file. Open it, pick the video, and it uploads from that device straight to Schedchie. It never passes through the conversation. Clients that render in-chat apps show a file picker in the message instead; the link works either way.

  • Open it on whichever device holds the video. The phone that filmed it is usually the right one.
  • The limits are the app's own: 200 MB and 15 minutes per video.
  • If the upload is interrupted, open the link again and pick the file once more.
  • When it finishes, go back to the chat. The assistant checks the file has landed before it schedules anything.
The link is good for 24 hours and covers that one file. Ask again and you get a new one.

Worth knowing

  • Media sent inline through an assistant caps at 5 MB. Anything larger goes by link: a public link Schedchie fetches itself, or an upload link (see sending a video).
  • Buying the X add-on stays in the app. An assistant can read your remaining balance but not spend money.
  • Member and approval tools need the Ultra plan, the same as in the app. Client review links work on every plan.
  • Everything the assistant does lands in the same calendar and the same activity view as work done by hand.

Write to support

Write with the account name and the post’s scheduled time, and a person writes back about that post.

support@schedchie.com

Unlimited accounts, unlimited posts, €7.99

Start free trial

14-day free trialCancel anytime, no questions asked