Connect the hosted MCP endpoint once, then let Codex, Claude, Cursor, or another MCP client inspect campaigns, schedule Zernio-backed automations, check delivery health, and manage Instagram workflows.
Share this URL with an agent
https://app.swaycue.com/docs/mcp/agent.md
Authenticated remote server
The guide tells the agent how to connect. The transport endpoint is https://app.swaycue.com/api/mcp and requires a revocable token.
01 — Install
Sign in to SwayCue, open Settings, and create a named token under Remote MCP access. The token is bound to your user and workspace and is displayed only once.
Remote endpoint
https://app.swaycue.com/api/mcp
Store the one-time token as OPENREPLY_MCP_TOKEN in your MCP client environment. Never commit it.
02 — Configure
The access token determines the user, workspace, and role automatically. No database credentials, user IDs, repository checkout, or local server process are required.
Codex
~/.codex/config.toml or a trusted project config
[mcp_servers.openreply]
url = "https://app.swaycue.com/api/mcp"
bearer_token_env_var = "OPENREPLY_MCP_TOKEN"
startup_timeout_sec = 30
tool_timeout_sec = 120Claude, Cursor, and JSON clients
Use the MCP settings file supported by the client
{
"mcpServers": {
"openreply": {
"url": "https://app.swaycue.com/api/mcp",
"headers": {
"Authorization": "Bearer ${OPENREPLY_MCP_TOKEN}"
}
}
}
}Restart the MCP client after saving. In Codex, run codex mcp list or use /mcp to inspect the connection.
03 — Verify
A successful MCP connection is not enough. The agent should verify infrastructure, account identity, and current campaign state before it changes anything live.
Check the system
Call openreply_health and require database, Redis, queue, and worker checks to pass.
Confirm the account
Call openreply_list_instagram_accounts before creating or changing a campaign.
Read before writing
Inspect the relevant campaign or scheduled post, then present the intended change.
Confirm live actions
Supply confirm: true only after the user authorizes an external, destructive, or live automation action.
04 — Tool directory
The running server advertises authoritative input schemas for every tool. Agents should inspect those schemas instead of inventing arguments.
Check infrastructure, dashboards, analytics, logs, and operational events.
Connect accounts, inspect posts and insights, and manage webhook subscriptions.
Create, review, import, update, and remove comment-to-DM automations.
Find future posts and attach an automation before Instagram publication.
Inspect Postiz integrations and schedule a mapped Instagram post from the agentic flow.
Read conversations and send explicit Instagram replies within Meta's rules.
Inspect membership, accept invitations, and administer non-owner members.
05 — Zernio
The scheduled-post record gives SwayCue a stable target before Instagram has assigned a media ID. Publication later fills that exact ID without changing unrelated campaigns.
Schedule the Instagram post in Zernio and retain its provider post ID.
Call openreply_sync_zernio_post with that ID.
Use the returned scheduledPostId in openreply_create_campaign.
Review the waiting campaign before the Instagram post exists.
At publication, the signed webhook binds the exact Instagram media ID. The worker repairs missed events every five minutes.
06 — Postiz
Postiz remains a private publishing sidecar, while SwayCue owns the workspace mapping, scheduled-post record, campaign binding, and reconciliation lifecycle.
An operator configures the server-only Postiz API key and the Postiz/Meta Instagram credentials.
In SwayCue Settings → Postiz Publishing, connect Instagram through SwayCue and map the SwayCue Instagram account to its Postiz integration.
Call openreply_list_postiz_integrations and verify the mapping.
Call openreply_schedule_postiz_post with the account, content, future timestamp, and optional media URL.
Use the returned scheduledPostId in openreply_create_campaign when the scheduled post should trigger comment-to-DM automation.
The worker reconciles Postiz and binds the exact published Instagram media ID after publication.
07 — Security
Every request is authenticated to a SwayCue user and workspace. The server applies the same membership roles as the dashboard and adds rate limits and tool-call auditing.
Every token is permanently scoped to the workspace that issued it.
Campaign and access changes require the token owner to remain an owner or admin.
Live changes, destructive actions, DMs, and public replies require confirm: true.
MCP tokens are stored as hashes, shown once, rate-limited, audited, and revocable in Settings.
08 — Troubleshooting
The endpoint uses standard Streamable HTTP with bearer authentication. Connection failures usually come from a missing, revoked, or stale client token.
curl -i https://app.swaycue.com/api/mcp -H "Authorization: Bearer $OPENREPLY_MCP_TOKEN"HTTP 401: create a new token in Settings, update the client secret, and restart the client.
HTTP 429: wait for the Retry-After interval before reconnecting.
Writes rejected: confirm the token owner is still an owner or admin member.
Scheduled posts absent: verify the Zernio connection, exact account mapping, and feature flag on both web and worker.
Worker unhealthy: repair the Railway worker before expecting DMs or publication reconciliation.
Ready to hand off
The raw guide is self-contained. Copy the prompt below into a coding-agent task, then create a one-time token in SwayCue Settings when the agent asks for it.