Postroom Docs
AI assistants / Claude connector setup

Claude connector setup

Connect an authenticated workspace and review exact publishing previews in Claude.

Connect

Use https://social.notacompanynameyet.com/mcp/claude with Streamable HTTP. Choose Sign in now and Register automatically (OAuth dynamic client registration). Leave custom request headers blank. Postroom currently advertises no Client ID Metadata Document support. Each customer signs into their own Postroom account and authorizes their own workspace.

Catalog

The explicit Claude endpoint exposes 18 tools: yet_profile, yet_accounts, yet_brand, yet_queue, yet_post_status, yet_analytics, yet_pinterest_boards, yet_held_previews, yet_attach_preview_media, yet_create_media_upload, yet_complete_media_upload, yet_get_media_upload, yet_create_image_upload, yet_complete_image_upload, yet_preview, yet_run_workflow, yet_approve and yet_cancel. It excludes yet_import_file and the app-only yet_schedule. The existing /mcp ChatGPT catalog is preserved. Catalog selection uses the URL, never User-Agent or a client display name.

Authorization

Both endpoints use the existing canonical OAuth resource https://social.notacompanynameyet.com/mcp and the same PKCE S256 authorization server, scope checks, token expiry and workspace ownership checks. Discovery is public; workspace reads require social.read. State-changing tools require social.read and social.write. Choosing a catalog grants no additional access.

Media in Claude web

Claude web does not automatically transfer its chat attachments through Postroom. Use yet_create_media_upload, open its browser_upload_url and sign into the same workspace. Select a JPEG, PNG, WebP or MP4 and choose Upload and verify. Back in Claude, use yet_get_media_upload with upload_id to retrieve media_url. Keep the temporary upload_url private. Compatible file/HTTP clients can PUT actual bytes and call yet_complete_media_upload. Images are limited to 3 MB; MP4 to 20 MB; requests expire after ten minutes.

Read and prepare

Verify yet_profile identifies the intended workspace, then use yet_accounts and yet_brand. For Pinterest, use yet_pinterest_boards to choose a real board. An image preview needs an enabled Pinterest account, workspace media_url, title, caption, explicit board_id and future scheduled_at with an explicit offset. yet_preview stores a new immutable preview; yet_run_workflow prepares previews without scheduling.

Approval and delivery

Review the exact saved image, text, destination and time before approving. yet_approve requires draft_id and confirmation approve_exact_preview. Changed or expired previews require another preview and approval. yet_cancel requires separate explicit approval and applies only to queued, unclaimed posts. After an uncertain response, inspect the existing draft or post rather than create a replacement. yet_post_status is the source of delivery confirmation.

Held Content Brain batches

yet_attach_preview_media needs a genuine held batch created in Content Brain or a connected companion. It attaches supplied workspace media and creates fresh previews; it does not generate images. Content Brain drafting requires a configured managed or workspace writer and saved processing consent. An empty held list is valid, but does not constitute a successful attachment test.

Directory testing

A working custom connector is separate from directory approval. SDK schema or integration tests do not replace exercising every advertised tool in MCP Inspector and Claude. Reviewer credentials must be provided privately through the submission form, never public documentation.