Give your assistant the context
Share the audience, objective, source material and brand voice. Ask for the angle before asking for a full campaign.
Use Z.AI / GLM in a compatible MCP client to develop social content, then bring supported drafts and plans into Orymus for review.
Start with a draft. Review the details. Choose what goes live.
Turn this idea into three social posts for next week. Save drafts in Orymus for my review.
Illustrative example. Available actions depend on connected tools and permissions.
Z.AI / GLM provides models; the application hosting the model handles MCP connections. Choose a client that supports both this provider and Orymus’s remote MCP authorization. A model API or chat alone does not establish the connection.
Official client documentationFirst, sign in to Orymus and connect the social accounts you want to manage. Then follow the client steps below.
Choose an agent or application that supports this model provider and remote MCP with the authorization required by Orymus.
Follow the client’s instructions to configure Z.AI and select an available model.
Add the Orymus MCP URL in the client’s MCP settings and complete its authorization flow.
Ask the client to list available Orymus tools. Request a draft only after the connection is active and check the result in Orymus.
Authorize with your Orymus account. Available tools follow your workspace permissions.
First request: “Show the Orymus tools and connected social channels available to my account.”
Provider access and Orymus plans are separate. Check current client requirements before connecting.
Keep the creative work in your assistant. Give the content a clear path into Orymus.
Share the audience, objective, source material and brand voice. Ask for the angle before asking for a full campaign.
MCP lets the client discover available tools and request supported actions in your authorized workspace.
Check the saved copy, platform format, media and links. Keep each version relevant to its channel.
Confirm the channel, date and timezone before a supported scheduling or publishing action. Check the returned result.
Give Z.AI / GLM your audience, source facts and brand voice. Ask for distinct versions for each channel and review supported drafts in Orymus.
Turn a release note or product brief into a sequence that explains the problem, the change and a practical example. Check every claim before saving.
Check the available calendar tools and ask for planned posts, channels and times. Resolve overlaps before requesting any schedule changes.
Copy an example, add your context and ask your connected assistant. Confirm the available tools before saving drafts or changing a schedule.
Use the available Orymus tools to prepare a LinkedIn draft from this brief. Keep the product facts accurate and save it for my review.
Propose three posts from these release notes for next week. Show the audience, channel and suggested time in Asia/Ho_Chi_Minh before creating anything.
Show my Orymus content for the next seven days and identify repeated topics. Do not change or publish anything.
The most useful prompts describe the outcome and the boundaries. A few details make content easier to review and scheduling easier to check.
Connect your accounts in Orymus first. Channel formats and MCP actions depend on the tools available to your workspace.
Use a client that supports both the model provider and the Orymus remote MCP authorization flow. Confirm compatibility in that client before connecting.
No. A draft is saved only after an available Orymus tool completes that action. Check the result in your workspace.
Model Context Protocol is a standard for connecting AI applications to external tools. Orymus provides a remote MCP endpoint so compatible clients can work with the content tools available to your authorized Orymus account.
Use the available tools to work on social drafts, campaign planning and your content calendar. The discovered tool list and account permissions determine the exact actions. Ask the assistant to show its Orymus tools before requesting an action.
Ask for drafts first and review copy, media, channels and timezone in Orymus. A request to schedule or publish should specify the exact content and time. Available publishing and team approval actions depend on your tools, permissions and plan.
Start with the channels connected to your Orymus workspace. Check the integrations catalog for channel requirements, then ask your assistant which channels and formats its current tools can use. A listed platform does not imply every format is exposed through MCP.
You need an Orymus account and access to a client that supports the required remote MCP connection. Orymus plans and AI provider plans are separate. Check the pricing page and your provider’s current connection requirements.
Confirm the full endpoint URL, finish authorization and enable the connection in your conversation. Check workspace policies and server status, then refresh the connection or start a new session. Use the official client guide for client-specific errors.
Client instructions follow the official documentation. Tools and availability can change; check the linked provider guide for current requirements.
Product names identify the clients covered by these guides and belong to their respective owners.Connect your workspace. Prepare the draft. Make the final call.