Skip to main content
Use Postsiva MCP inside Cursor to manage social accounts from your editor: check connections, draft posts, publish, read analytics, and reply to comments — all via natural language. Cursor uses the CLI MCP endpoint (https://mcp.postsiva.com/mcp) with an API key as the X-API-Key header (not a query param) and curl-based media upload.

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

1

Open MCP settings

Cursor → SettingsMCPAdd server
2

Configure HTTP transport

  • Type: HTTP (Streamable HTTP)
  • URL: https://mcp.postsiva.com/mcp
  • Header: X-API-Key = your psk_live_… key
3

Restart Cursor

Reload MCP or restart Cursor so the server connects.

mcp.json (project or global)

Add to .cursor/mcp.json in your project, or ~/.cursor/mcp.json globally:
Do not commit real API keys. Use environment-specific config or Cursor’s secret storage for production keys.
Alternative auth via query string (less recommended):

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

  1. Ask for idea_to_content — review copy in chat
  2. Ask for content_to_image — confirm image URLs
  3. Ask to publish with draft: true first, 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.
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_only or comma-separated platform scopes for safer automation — see IDs and scopes.
  • LinkedIn refresh: get_user_posts with refresh_posts=true on 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_content and content_to_image run per platform in parallel; one failed platform does not block others.

Troubleshooting

Next

Connect to MCP

Transport and auth details

n8n integration

Automation workflows

Tool catalog

All 13 tools