plan_workflow — Meta Council MCP Tool
plan_workflow
(plan workflow) is one of 189 tools on the
Meta Council
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call plan_workflow from your client
- Claude Code Meta Council plan_workflow run in your project directory
- Claude Desktop Meta Council plan_workflow ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Meta Council plan_workflow ~/.cursor/mcp.json
- VS Code Meta Council plan_workflow .vscode/mcp.json
- Zed Meta Council plan_workflow ~/.config/zed/settings.json
- Windsurf Meta Council plan_workflow ~/.codeium/windsurf/mcp_config.json
- Cline Meta Council plan_workflow ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Meta Council plan_workflow ~/.gemini/settings.json
- Grok Meta Council plan_workflow .mcp.json (in your project root)
- ChatGPT Meta Council plan_workflow Settings → Connectors → Advanced → Developer mode
- Claude.ai Meta Council plan_workflow Settings → Connectors → Add custom connector
- LangChain Meta Council plan_workflow pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http decision-intelligence https://meta-council.com/mcpOther tools on this server
- run_council
- plan_council
- list_panels
- list_agents
- get_session
- get_visualization
- list_workflows
- test_workflow_step
- run_workflow
- get_workflow_session
- recommend_panel
- estimate_cost
- get_agent_detail
- advance_workflow
- retry_workflow
- get_settings
- list_integrations
- get_api_key_info
- rotate_api_key
- mint_child_api_key
- list_outreach_campaigns
- search_outreach_leads
- outreach_analytics
- score_locus_case
- locus_determine_from_scores
- ask_legal
- campaign_pipeline_stats
- list_campaign_triggers
- list_campaign_replies
- create_outreach_campaign
- add_outreach_lead
- assign_leads_to_campaign
- update_outreach_lead_status
- draft_outreach_email
- create_outreach_pitch
- list_deals
- get_deal
- list_sales_tasks
- get_business_suite_overview
- get_sales_analytics
- get_sales_recommendations
- get_deal_health
- create_deal
- update_deal
- convert_lead_to_deal
- log_deal_activity
- complete_sales_task
- list_invoices
- get_invoice
- get_invoice_aging
- create_invoice
- update_invoice
- add_invoice_line_item
- send_invoice
- mark_invoice_paid
- void_invoice
- convert_deal_to_invoice
- create_accounting_run
- list_accounting_runs
- get_accounting_run
- delete_accounting_run
- preview_accounting_ticket_sync
- sync_accounting_tickets
- ticket_plan
- ticket_batch_create
- ticket_list
- ticket_get
- ticket_comments
- get_ticket_attention_policy
- save_ticket_attention_policy
- get_ticket_attention_review
- save_ticket_attention_review
- get_ticket_attention_queue
- get_ticket_projects
- get_workspace_metrics
- get_meta_council_platform_metrics
- get_site_analytics
- get_feature_delivery_summary
- get_ticket_burndown
- get_ticket_label_history
- get_ticket_label_cohort
- list_saved_views
- get_saved_view
- execute_saved_view
- list_portfolio_snapshots
- get_portfolio_snapshot
- diff_portfolio_snapshots
- list_portfolio_snapshot_notes
- create_saved_view
- update_saved_view
- archive_saved_view
- restore_saved_view
- share_saved_view
- unshare_saved_view
- delete_saved_view
- create_portfolio_snapshot
- create_portfolio_snapshot_note
- ticket_validation_finalize
- ticket_scenario_create
- ticket_scenario_revise
- ticket_readiness
- ticket_scenario_list
- ticket_dependency_add
- ticket_dependency_remove
- ticket_dependency_list
- ticket_create
- ticket_update
- ticket_archive
- ticket_comment
- ticket_claim
- submit_meta_council_feedback
- list_meta_council_feedback
- triage_meta_council_feedback
- list_marketing_brands
- get_marketing_brand
- list_marketing_audiences
- get_marketing_audience
- list_marketing_campaigns
- get_marketing_campaign
- list_content_assets
- get_content_asset
- get_content_calendar
- create_marketing_brand
- update_marketing_brand
- create_marketing_audience
- update_marketing_audience
- create_marketing_campaign
- update_marketing_campaign
- create_content_asset
- update_content_asset
- create_content_asset_revision
- submit_content_asset
- approve_content_asset
- reject_content_asset
- list_consulting_clients
- create_consulting_client
- update_consulting_client
- list_consulting_engagements
- create_consulting_engagement
- update_consulting_engagement
- get_consulting_engagement
- create_consulting_document_revision
- update_consulting_document_revision
- initialize_consulting_milestones
- update_consulting_milestone
- create_consulting_deliverable
- update_consulting_deliverable
- submit_consulting_deliverable
- reopen_consulting_deliverable
- approve_consulting_document_revision
- approve_consulting_deliverable
- create_workflow_template
- update_workflow_template
- delete_workflow_template
- create_monitor
- list_monitors
- delete_monitor
- list_approvals
- decide_approval
- audit_export
- account_export
- project_list
- project_create
- project_get
- project_update
- project_link_feature
- project_unlink_feature
- project_document_create
- project_document_get
- project_document_revise
- create_scope_baseline
- list_scope_baselines
- get_scope_baseline
- compare_scope_baseline
- get_ticket_delivery_plan
- save_ticket_delivery_plan
- list_ticket_delivery_plan_history
- get_delivery_timeline
- create_comparison_set
- list_comparison_sets
- get_comparison_set
- add_comparison_runs
- get_comparison_eligibility
- run_comparison
- create_comparison_artifact
- get_comparison_artifact
- create_comparison_verdict
- get_comparison_verdict
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.