Introduction to OpenQuok MCP
Connect Cursor, Claude Code, Codex, and other MCP (Model Context Protocol) clients to OpenQuok.
Connect your agent today
Draft from chat, review in your calendar, and publish only what you approve.
What is OpenQuok MCP?
OpenQuok ships two separate MCP servers on different origins. Both use the path /mcp, but they do not share tools or credentials.
| Server | Typical host | Auth | What agents use it for |
|---|---|---|---|
| Product (workspace) | https://api.openquok.com (or your BACKEND_DOMAIN_URL) | opo_ Bearer or token in URL | Channels, scheduling, posts, plugs, analytics |
| Documentation | https://www.openquok.com (or your web app origin) | None — published docs only | search_docs, read_page, get_site_overview, submit_feedback |
The product server is what this guide focuses on: list connected channels, schedule and manage posts, configure plugs, and read analytics without installing the CLI skill.
Use the same opo_ programmatic access token you generate under Developers → Access for the product server only.
Tip
On any docs page, use Copy MCP URL for manual client config and Connect to Cursor for one-click install of documentation MCP (OpenQuok Documentation pointing at your site /mcp). Scheduling still requires the product server (openquok in .cursor/mcp.json) with an opo_ key — see Client setup.
MCP documentation
Connect a native MCP client, then browse examples, tool reference, and per-client setup guides.
How it works
The server registers tools that AI clients discover at connect time. The agent reads each tool’s schema, then calls them on your behalf against the authenticated workspace.
A typical workflow:
- List — groupList (optional) then integrationList to find channel UUIDs; integrationSchema for platform rules.
- Schedule — schedulePostTool to draft, schedule, or publish now; uploadFromUrl when you need media ids before scheduling.
- Manage — postsList, postsStatus, postsReschedule, postsDelete, postsReviewTodo; postsMissing then postsConnect when release_id is missing.
- Analytics — analyticsPlatform or analyticsPost with days 7, 30, or 90.
- Plugs — plugsCatalog, plugsList, plugsUpsert for global like-threshold rules; cross-account comments on create go in schedulePostTool settings.
All of this can happen when you ask your agent something like:
Schedule a post to X for tomorrow at 10am: Excited to announce our new feature!
Endpoints (product MCP)
These routes live on the API host. Do not point workspace automation at the web origin /mcp — that entry is the documentation catalog.
| Endpoint | Auth | Purpose |
|---|---|---|
| GET/POST /mcp | Authorization: Bearer opo_… | Streamable HTTP product MCP |
| GET/POST /mcp/:token | API key in URL path | Clients that cannot set headers |
| OPTIONS on both | CORS * | Browser-based MCP clients |
Base URL (product)
| Environment | Product MCP URL |
|---|---|
| OpenQuok Cloud | https://api.openquok.com/mcp |
| Self-hosted | Your BACKEND_DOMAIN_URL origin + /mcp |
Base URL (documentation)
| Environment | Documentation MCP URL |
|---|---|
| OpenQuok Cloud | https://www.openquok.com/mcp |
| Self-hosted | Your public web origin + /mcp (same host as /docs and /llms.txt) |
Tip
Copy ready-to-run snippets from Account → Settings → Developers → Access → MCP client configuration. See Client setup.
Authentication
Send your workspace programmatic token as a Bearer credential:
curl -H "Authorization: Bearer opo_your_programmatic_token"
https://api.openquok.com/mcpIf your client cannot set headers, append the token to the path:
https://api.openquok.com/mcp/opo_your_programmatic_tokenOAuth2 access tokens from third-party apps also use the opo_ prefix and work the same way.
Available tools
| Group | Tool | Purpose |
|---|---|---|
| Channels | groupList | List channel groups (customers) |
| Channels | integrationList | List connected social channels; optionally filter by group |
| Channels | integrationSchema | Character limits, compose settings, and allow-listed provider tools |
| Channels | triggerTool | Invoke an allow-listed provider method on a connected channel |
| Scheduling | schedulePostTool | Draft, schedule, or publish-now posts; per-channel settings for plugs |
| Scheduling | uploadFromUrl | Fetch a public HTTPS URL into workspace media |
| Posts | postsList | List posts in a date window |
| Posts | postsFindSlot | Suggest a free schedule slot |
| Posts | postsStatus | Flip draft ↔ scheduled at the stored time |
| Posts | postsReschedule | Move post group to a new publish time |
| Posts | postsReviewTodo | Set or update a review-todo note |
| Posts | postsDelete | Delete a post row |
| Posts | postsMissing | List candidates when release_id is missing |
| Posts | postsConnect | Link a post to a provider release_id |
| Analytics | analyticsPlatform | Platform-level metrics for a channel (days 7, 30, or 90) |
| Analytics | analyticsPost | Per-post metrics for a published row |
| Plugs | plugsCatalog | List global plug types and field names |
| Plugs | plugsList | List saved global plug rules on a channel |
| Plugs | plugsUpsert | Create or update a global plug rule |
| Plugs | plugsActivate | Enable or disable a saved global plug |
| Plugs | plugsDelete | Delete a saved global plug |
Image and video generation MCP tools are not available yet. Local file upload and CLI device login stay on the openquok-core CLI skill.
Verify connection
After configuring your client, ask your agent:
List my connected social media accounts
If authentication succeeds, the agent calls integrationList and returns your workspace channels.
Related Section(s)
Other MCP sections plus the public API and CLI.