Overview - MCP Examples
OpenQuok MCP agent workflows — prompts or examples for scheduling, posts management, analytics, plugs, directory launch, and per-platform recipes.
Connect your agent today
Draft from chat, review in your calendar, and publish only what you approve.
What is in this section
Copy-pasteable recipes for AI agents using OpenQuok MCP, grouped by social channel or directory launch platform. Each social page shows what you can ask your agent in plain language and the tool payloads the agent builds behind the scenes — schedulePostTool, postsList, analyticsPost, plugsUpsert, and more. Directory pages use directoryProfilesList, directoryVariantsEnsure, directoryProfilesUpdate, directoryListingSummary, and directorySeoOverview for profiles, variants, filling copy, readiness, and cached SEO. Tool intent tables: Tools reference — Directory launch.
Note
OpenQuok ships first-party social providers for Meta Threads, Facebook Page, Instagram (Business and Standalone), YouTube, TikTok, X, and LinkedIn. Additional social pages appear when new providers land in backend/integrations/providers/.
Social channels
Directory launch is not social posting
Directory launch prepares your product on My Products for sites like PeerPush and Uneed. Agents use directoryProfilesList, directoryVariantsEnsure, and related tools — not schedulePostTool. You still submit on the directory site with the browser extension.
Main profile and site copy
Your main product profile is the default record for your product. A directory variant is an optional copy for one launch site so you can tailor tagline and description for PeerPush or Uneed without changing every other destination.
Before directoryVariantsEnsure, call directoryProfilesList with mainOnly: true. That lists only main profiles so the agent passes the correct main id. Without mainOnly, the response also includes site copies.
See Glossary — Directory launch for definitions.
Directory launch
List connected channels
After configuring your MCP client, ask:
List my connected social media accounts
The agent calls integrationList and returns channel names, provider identifiers, and UUIDs. Save the UUID you need for scheduling.
Multi-channel blast
Publish the same announcement to all my connected channels right now.
{
"type": "now",
"socialPost": [
{
"integration": "<integration-id-1>",
"postsAndComments": ["We just shipped a new feature!"]
},
{
"integration": "<integration-id-2>",
"postsAndComments": ["We just shipped a new feature!"]
}
]
} Use integrationList to build one socialPost entry per channel.
Bulk schedule across days
Schedule five motivational posts to my X account — one per weekday next week at 10am UTC.
Each item in socialPost is an independent post with its own date, content, and settings:
{
"type": "schedule",
"date": "2026-06-30T10:00:00.000Z",
"socialPost": [
{
"integration": "<x-integration-id>",
"postsAndComments": ["Monday motivation"],
"settings": { "who_can_reply_post": "everyone" }
}
]
} Repeat with different date values (or ask the agent to batch multiple entries in one schedulePostTool call).
List and manage posts
Show me all scheduled posts for the next two weeks.
The agent calls postsList with start and end ISO timestamps. Use postsStatus to flip a row between draft and scheduled at the same time, postsReschedule to move the publish slot, postsDelete to remove it, or postsReviewTodo to set a kanban review note.
Move post X to tomorrow at 2pm UTC
Find a free slot on my Threads channel next week.
The agent calls postsFindSlot with the channel UUID, then passes the returned date into schedulePostTool.
Per-post analytics
How did my Threads post from last Tuesday perform over the last 30 days?
- Call postsList to find the postId.
- Call analyticsPost with days: 30.
If release_id is missing, call postsMissing then postsConnect before analytics will return data.
Global plugs
Create a global plug on my X channel that auto-replies when a post hits 50 likes.
See MCP examples — Threads, X, and LinkedIn for plugsCatalog → plugsUpsert walkthroughs. Global plugs are supported on Threads, X, and LinkedIn Page only. Cross-account comments on create use schedulePostTool.settings instead — see Threads cross-account example.
Directory launch and SEO
List my directory product profiles, ensure a PeerPush variant for my main profile, and show which directories are ready to launch.
The agent calls directoryProfilesList with mainOnly, directoryVariantsEnsure with directorySiteKey peerpush, then directoryListingSummary for readiness per destination. See MCP examples — PeerPush and Uneed for per-site prompts.
What are my directory SEO ratings and when were they last checked?
Call directorySeoOverview with your main productProfileId. Use checkedAt on each metric and manualRefreshAvailableAt before directorySeoRefresh.
Conventions used in these pages
- Replace <integration-id> (and suffixed variants like <threads-integration-id>) with UUIDs from integrationList.
- Agent prompts use natural language — see MCP introduction for the canonical prompt shape (action to channel when: body).
- attachments must be public https:// URLs. OpenQuok downloads each URL, uploads it to your workspace media storage, then attaches it to the post.
Attach media in chat
Instead of pasting a public URL in your prompt, you can attach an image or video file directly in your MCP client chat (paste, drag-and-drop, or the attachment control). The agent uploads the file and fills attachments before calling schedulePostTool.
Rate limits
Public API and MCP share the same 30 requests per hour limit per token. Batch multi-channel schedules into one schedulePostTool call when possible.