Turn a detailed brief into a campaign
Share the problem, audience, positioning and product facts. Have Claude propose a sequence that introduces the idea, answers objections and invites a next step. Move the approved direction into Orymus drafts.
Give your longer briefs and brand guidelines a practical next step. Connect Claude to Orymus through a custom remote MCP connector, then prepare social content without losing the context of your conversation.
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.
Claude supports custom remote MCP connectors. Add the Orymus MCP endpoint in Claude’s connector settings, authenticate your Orymus workspace and enable the connector in your conversation. Organization owners may need to configure access before team members can connect.
Official client documentationClaude 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 | ||
|---|---|---|
| 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.
Go to Customize → Connectors. On an eligible individual plan, choose Add custom connector; organization owners configure team access first.
Use Orymus as the name and paste the remote MCP endpoint. Continue to the authentication settings Claude detects.
Complete the displayed authorization flow for your workspace and finish adding the connector.
Use the conversation’s + menu to enable the connector. Ask Claude to show the available Orymus tools before your first content 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.
Share the problem, audience, positioning and product facts. Have Claude propose a sequence that introduces the idea, answers objections and invites a next step. Move the approved direction into Orymus drafts.
Provide examples of posts you like, along with phrases to avoid. Ask Claude to explain the intended angle for each draft so a reviewer can assess the message alongside the wording.
Extract distinct lessons from a transcript or newsletter you provide. Give each post its own point, adapt the length for each channel and keep links to source material in the review brief.
Copy an example, add your context and ask your connected assistant. Confirm the available tools before saving drafts or changing a schedule.
Read this brand brief. Prepare a five-post campaign in Orymus covering the problem, our approach, a customer question, a product example and a next step. Save drafts only.
Turn this newsletter into a LinkedIn post and an X thread. Preserve the original claims, use our voice and save supported formats in Orymus for review.
Review the Orymus posts planned for this week. Identify repeated topics and suggest a more balanced mix before editing 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 Claude’s custom remote MCP connector flow with the Orymus endpoint. Availability depends on your Claude plan, organization settings and successful Orymus authorization.
The Claude chat connector uses the app’s connector settings. Claude Code has a terminal MCP configuration. Both connect to the Orymus endpoint; follow the guide for the client you use.
An organization owner can configure a connector for the team. Each member must connect as required, and actions remain subject to the workspace and account permissions in effect.
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.