If you already spend your day in Claude Code, you can schedule and manage social posts without switching to a browser. Connect OneUp's MCP server once, and Claude Code can list your accounts, schedule posts, and check or fix what's queued, all from plain-language requests.
Connect OneUp to Claude Code
- Get an API key. Generate one on OneUp's API Access page.
- Add OneUp to Claude Code:
claude mcp add --transport http --scope user oneup "https://feed.oneupapp.io/mcp/oneup"
The --scope user flag makes OneUp available across all your projects.
- Authenticate. Open Claude Code, run
/mcp, select oneup, and complete the browser flow. You enter your API key on a OneUp page and approve access. OneUp stores the key encrypted, and Claude Code receives an OAuth token instead of the key itself. - Check the connection from your terminal:
claude mcp list
Then ask: "Use OneUp to list my connected social accounts." If it returns your accounts, you're set.
Prompts to try
- "List all my connected Instagram accounts."
- "Schedule a post to my 'Marketing' category for tomorrow at 2 PM with the text 'Hello from Claude Code.'"
- "Show me my scheduled posts for next week."
- "Show me any failed posts, and reschedule them for tomorrow at 9 AM."
- "Edit my scheduled post about the webinar to fix the date."
OneUp's tools cover creating text, image, and video posts, listing scheduled, published, draft, and failed posts, editing or deleting scheduled posts, and rescheduling failed ones.
Workflows that suit developers
Because Claude Code can read files in your project, it can turn what you've already written into posts:
- Announce a release."Read CHANGELOG.md, write a short announcement for the latest version for LinkedIn and X, and show me the draft before scheduling anything."
- Promote a docs or blog update. Point it at a markdown file and ask for a post that links to it.
- Batch a launch week. Ask for a handful of posts at staggered times, then review them as a group.
Habits that keep it safe
- Ask for a preview first. Have Claude Code show the text, accounts, and times, and only schedule after you approve.
- Name the category. Categories scope which accounts a post can reach, which avoids posting to the wrong place.
- Verify afterward. Ask it to list your scheduled posts and confirm the new one is there.
- Prefer the OAuth flow. Leave the API key out of the server URL. If a client forces a key in the URL, keep that URL private, because it can end up in config files and shell history.
- Know where to revoke. You can review and disconnect connections from OneUp's MCP Connections page.
Not using Claude Code?
The same server works with Codex, Cursor, and other MCP clients that support remote HTTP servers and OAuth. See OneUp's coding agent setup guide.
Ready to schedule from your terminal? Get started with OneUp.