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. 52 tools, no token to copy.
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
The URL
https://mcp.schedchie.com/mcp
That is the whole configuration. There is no per-user URL and no API key to generate — signing in is an OAuth round trip to Schedchie, and your assistant never sees your password.
Setting it up, per client
Three steps everywhere: copy the URL, add it, sign in.
ChatGPT
- Go to Settings → Connectors, press Create, name it Schedchie and paste the URL. Set authentication to OAuth. If there is no Create button, turn on developer mode under Advanced first.
- A Schedchie sign-in opens. Approve it, then pick Schedchie in a chat.
- ChatGPT receives a 13-tool core profile rather than the full set — its connector budget is small. Scheduling, editing, the queue and the analytics summary are all in it.
Claude (claude.ai and Desktop)
- Go to Settings → Connectors, press Add custom connector and paste the URL.
- Approve the Schedchie sign-in that opens, and the full tool set appears in the chat.
Claude Code
claude mcp add --transport http schedchie https://mcp.schedchie.com/mcp claude mcp login schedchie
Your browser opens the Schedchie sign-in. Approve it and Claude Code has the full set. Add -s user to the first command to register it globally rather than per project.
Cursor
Add it to .cursor/mcp.json:
{
"mcpServers": {
"schedchie": { "url": "https://mcp.schedchie.com/mcp" }
}
}Cursor registers itself with Schedchie and opens the sign-in. Nothing to paste.
VS Code (Copilot)
Run MCP: Add Server from the Command Palette, pick HTTP and paste the URL — or write .vscode/mcp.json directly:
{
"servers": {
"schedchie": { "type": "http", "url": "https://mcp.schedchie.com/mcp" }
}
}Any other MCP client
Point it at the URL. The one requirement is the Streamable HTTP transport. The server advertises its authorization server and registers clients dynamically, so anything that speaks OAuth sends you through the sign-in without being told to.
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.
| Permission | What it covers |
|---|---|
| Schedule and edit posts | Draft, schedule, change, retry and delete posts in your queue. |
| Upload media | Add images and video to posts, including custom video covers. |
| Read analytics | Followers, publish activity and per-platform numbers. Read only. |
| Team and approvals | Members, invitations, approving or rejecting held posts, client review links. |
| Notes, presets and groups | Content notes, publishing presets, account groups and connections. |
- 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 actually do
52 tools across posts, media, analytics, accounts, teams, notes and presets. In practice that means asking for things like:
- "What is scheduled for next week, and did anything fail on Friday?"
- "Schedule this to Instagram and LinkedIn on Tuesday at 9, with different copy for each."
- "Retry the accounts that missed on that post."
- "How did last month's LinkedIn posts do?"
- "Approve everything waiting from the team."
Seven of the tools delete or disconnect things, and they are marked as destructive so a well-behaved client asks you first.
Worth knowing
- Media sent inline through an assistant caps at 5 MB. Larger video goes through the app.
- Buying the X add-on stays in the app — an assistant can read your remaining balance but not spend money.
- Team tools need the Team plan, the same as they do in the app.
- Everything the assistant does lands in the same calendar and the same activity view as work done by hand.
The longer version, with the full tool list and a walkthrough of a real session, is on the AI connection page.
Related help
Teams
Team members and approvals
Invite members to specific client Groups, hold their posts for approval, read the 30-day activity view, and let clients approve without an account.
Start here
Getting started
The first four steps in Schedchie: connect an account through the platform, write one post for all of them, put it on the calendar, and check what went out.
Billing
X (Twitter) add-on
€4.99 buys 30 X posts, valid 30 days. How posts are counted, how batches stack, where to buy, and what happens when a batch runs out.
Not covered here?
Write to support@schedchie.com with the account name and the scheduled time of the post, and you get a person, not a form.
Unlimited accounts, unlimited posts, €7.99
Nine platforms on one calendar. The trial runs 14 days with everything switched on.
14-day free trial · Cancel anytime, no questions asked
