Prerequisites
- Pro plan with
mcp_enabled - Workspace API key (
psk_live_…) from Settings → API Keys - At least one social account connected in that workspace
- Cursor with MCP support (Settings → MCP)
Install
Configure HTTP transport
- Type: HTTP (Streamable HTTP)
- URL:
https://mcp.postsiva.com/mcp - Header:
X-API-Key= yourpsk_live_…key
mcp.json (project or global)
Add to .cursor/mcp.json in your project, or ~/.cursor/mcp.json globally:
Verify connection
In Cursor Agent chat, try:What social accounts are connected to my Postsiva workspace?The agent should call
get_accounts and list linked platforms.
If you see “API key required” or “Invalid or expired API key”, check the header and Pro plan status.
Example prompts
Accounts and OAuth
Content pipeline
Publishing
Read and engage
Queue management
Common workflows
Draft → review → publish
- Ask for
idea_to_content— review copy in chat - Ask for
content_to_image— confirm image URLs - Ask to
publishwithdraft: truefirst, then live when ready
Weekly analytics review
Comment triage
Tool reference
Cursor exposes all 13 MCP tools. See the Tool catalog for arguments and REST equivalents.| Category | Tools |
|---|---|
| Accounts | get_accounts, manage_platform_connection |
| Posts | publish, get_user_posts, get_queued_posts |
| Inbox | get_comments, reply_to_comment |
| Analytics | get_unified_analytics |
| AI | idea_to_content, content_to_image, media_to_content, analyze_media |
| Utility | web_search_duckduckgo |
clear_workspace_chat_history is not on MCP — use DELETE /user-agent-chats or ask the WhatsApp/website agent to clear history.Tips
- Scoped keys: Use
linkedin_onlyor comma-separated platform scopes for safer automation — see IDs and scopes. - LinkedIn refresh:
get_user_postswithrefresh_posts=trueon personal LinkedIn is expensive (Apify) and caps at 2 posts — prefer cached data unless syncing live. - Character limits: Generated copy may exceed platform limits — ask Cursor to trim before
publish. - Parallel platforms:
idea_to_contentandcontent_to_imagerun per platform in parallel; one failed platform does not block others.
Troubleshooting
| Symptom | Fix |
|---|---|
| MCP server red / disconnected | Verify URL, restart Cursor, check key prefix psk_live_ |
| Plan upgrade message | Upgrade to Pro; confirm mcp_enabled |
| Empty tool list | Re-add server; ensure Streamable HTTP (not stdio) |
| 403 on OAuth connect | API key scope may restrict platforms — use full scope |
Next
Connect to MCP
Transport and auth details
n8n integration
Automation workflows
Tool catalog
All 13 tools