Create together
Work through your idea in Claude Code, then ask for a post tailored to each channel.
Move from a working session to a publishing plan. Use a supported MCP connection to work with your Orymus drafts and calendar.
Drafts move into Orymus, where your team can check the copy, channels and timing.
Illustration only. No account is connected and nothing is published.
Work through your idea in Claude Code, then ask for a post tailored to each channel.
Keep drafts, channels and proposed publishing times in one Orymus calendar.
Review the details in Orymus before you ask to schedule or publish.
Claude Code supports an MCP setup path. Availability and sign-in steps depend on your account and workspace settings.
Create an Orymus account and connect the social channels you want to use.
Follow Claude Code’s official MCP setup guide, then add the Orymus server URL below.
If the client offers an Orymus sign-in flow, complete it and ask to list your connected channels. Start with a draft for review.
Use this endpoint in clients that support remote MCP servers.
https://mcp.orymus.com/mcpConnection support and available tools depend on the client.
Use these examples after your client has access to Orymus tools. Ask for drafts first, then review the result.
“Draft a LinkedIn post about our new collection in our brand voice. Save it as a draft in Orymus for review.”
“Prepare three posts for next week. Suggest times in Asia/Ho_Chi_Minh and show me the plan before scheduling.”
“Show the posts scheduled this week in Orymus, including channels, times and review status.”
“Turn this idea into a five-post campaign. Keep everything in draft until I review the copy and channels.”
The official Claude Code documentation describes an MCP setup path. Add the Orymus server URL and complete authorization if your account supports it.
No. The example is local and does not connect accounts, save drafts or publish posts.
Yes. Ask for drafts, then review copy, channels, media and times in Orymus before scheduling or publishing.
Claude Code is identified for compatibility guidance only. Product names belong to their respective owners.