schedule_post — Siren MCP Tool
schedule_post
(schedule post) is one of 36 tools on the
Siren
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call schedule_post from your client
- Claude Code Siren schedule_post run in your project directory
- Claude Desktop Siren schedule_post ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Siren schedule_post ~/.cursor/mcp.json
- VS Code Siren schedule_post .vscode/mcp.json
- Zed Siren schedule_post ~/.config/zed/settings.json
- Windsurf Siren schedule_post ~/.codeium/windsurf/mcp_config.json
- Cline Siren schedule_post ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Siren schedule_post ~/.gemini/settings.json
- Grok Siren schedule_post .mcp.json (in your project root)
- ChatGPT Siren schedule_post Settings → Connectors → Advanced → Developer mode
- Claude.ai Siren schedule_post Settings → Connectors → Add custom connector
- LangChain Siren schedule_post pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http siren https://mcp.mysiren.ai/mcp
Other tools on this server
- get_account
- list_runs
- get_run
- create_campaign
- list_films
- describe_film
- clarify_brief
- render_asset
- upload_media
- post_run
- get_brand_dna
- update_brand_dna
- list_product_screens
- upload_product_screen
- update_product_screen
- delete_product_screen
- upload_logo
- get_mascot
- create_mascot
- mascot_step
- list_people
- add_person
- delete_person
- list_media
- get_performance
- list_posts
- buy_credits
- list_brand_videos
- upload_brand_video
- delete_brand_video
- delete_media
- studio_templates
- studio_card
- studio_automate
- studio_schedule
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.