Skip to main content
Use Postsiva tools inside Claude via the Model Context Protocol. There are two MCP URLs and different auth rules: Web search is not an MCP tool — Claude already has built-in search.

​
Requirements

  • Postsiva plan with mcp_enabled
  • Claude account with Connectors support (web) or Claude Code (CLI)
  • Workspace membership (you pick the workspace during OAuth on Claude.ai)

​
Claude.ai — OAuth only

Use the web MCP URL with no API key in the URL or connector fields. Claude strips query API keys on tool POSTs, so key-based connectors fail.
1

Open Claude Connectors

In Claude, open Customize → Connectors (or Settings → Connectors).
2

Add a custom connector

Click + → Add custom connector.
3

Name and URL

Name:
Remote MCP server URL (no query string, no api-key):
Leave OAuth Client ID / Client Secret empty for CIMD, or paste these Postsiva Claude credentials:OAuth Client ID (OAUTH_CLAUDE_CLIENT_ID):
OAuth Client Secret (OAUTH_CLAUDE_CLIENT_SECRET):
4

Connect and authorize

Click Connect. Sign in to Postsiva, select a workspace, and allow access.
5

Use in chat

Enable the Postsiva connector in a chat. Upload media via the iframe, then when publishing, use the publish preview App (caption + media, account toggles by name, Post / Schedule / Draft / Reject).

​
Claude Code — API key header + CLI URL

For local files: upload_media(file_path=..., media_type=image|video|document) → run returned curl_command → use media_id / public_url in publish.

​
What Claude can do

Same MCP tool catalog: publish, posts, comments, analytics helpers, OAuth connect helpers, AI content, queue/drafts. Upload tools differ by URL (iframe vs curl). No web-search tool.