Turn a working brief into social drafts
Provide a campaign brief from your project and ask Gemini CLI to summarize the key message. Prepare one version per connected channel, with a clear audience and next step for each draft.
Use Gemini CLI’s remote MCP support to bring social content into your existing workflow. Connect the Orymus server, authorize your workspace and start with a draft you can check in Orymus.
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.
The MCP setup in this guide uses Gemini CLI. Register Orymus as an HTTP MCP server with the CLI command or the mcpServers configuration, then complete authentication. The Gemini consumer chat app has a different integration surface; this is a Gemini CLI connection guide.
Official client documentationGemini CLI is where the thinking happens. Orymus gives the result a place to go: a saved draft, a calendar slot and a review before anything is published.
| Task | Gemini CLI alone | |
|---|---|---|
| Brainstorm and draft posts in conversation | Yes | Yes |
| Save drafts to your social workspace | Yes | No |
| See every post on a content calendar | Yes | No |
| Schedule to connected social accounts | Yes | No |
| Review and approve before anything goes live | Yes | Copy and paste by hand |
| Adapt one idea for LinkedIn, Instagram, X and more | Yes | Copy and paste by hand |
First, sign in to Orymus and connect the social accounts you want to manage. Then follow the client steps below.
Install and sign in to Gemini CLI using Google’s setup documentation. Use an environment that can open a browser for authorization.
Run the command shown here, or merge the JSON example into your Gemini settings. Keep your existing MCP entries.
Open Gemini CLI and follow the authorization flow. Use /mcp auth orymus if authentication is required.
Use /mcp to inspect server status. Ask for available Orymus tools and begin with a small draft request.
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.
Provide a campaign brief from your project and ask Gemini CLI to summarize the key message. Prepare one version per connected channel, with a clear audience and next step for each draft.
Keep the social plan close to the notes you are already working with. Ask for a simple weekly outline, then save supported drafts to Orymus after checking dates and timezone.
Ask for scheduled posts and drafts before proposing a new campaign. Use the returned calendar to spot overlapping messages and avoid repeating the same announcement on the same day.
Copy an example, add your context and ask your connected assistant. Confirm the available tools before saving drafts or changing a schedule.
Read this campaign brief and use Orymus to prepare a LinkedIn draft and a shorter X draft. Keep the product details accurate and save both for review.
Show this week’s Orymus calendar before suggesting three new posts. Use Asia/Ho_Chi_Minh, avoid duplicate topics and present the plan before saving changes.
Create a review brief from these product notes: audience, key message, source facts and two caption options. Save the chosen option as an Orymus draft after I select it.
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.
These instructions use Gemini CLI, Google’s terminal client with remote MCP support. Use the CLI command or JSON configuration on this page; settings in the Gemini chat app may differ.
Use the HTTP transport for the Orymus HTTPS MCP endpoint. In Gemini CLI settings, the HTTP endpoint is configured with httpUrl under mcpServers.
The server needs authorization to access your Orymus workspace. Complete the browser flow and inspect /mcp status. If authorization fails, check the account, client version and server requirements.
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.
Connect your workspace. Prepare the draft. Make the final call.