set_opportunity_status — VarynForge MCP Tool Mutating
set_opportunity_status
(set opportunity status) is one of 57 tools on the
VarynForge
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call set_opportunity_status from your client
- Claude Code VarynForge set_opportunity_status run in your project directory
- Claude Desktop VarynForge set_opportunity_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor VarynForge set_opportunity_status ~/.cursor/mcp.json
- VS Code VarynForge set_opportunity_status .vscode/mcp.json
- Zed VarynForge set_opportunity_status ~/.config/zed/settings.json
- Windsurf VarynForge set_opportunity_status ~/.codeium/windsurf/mcp_config.json
- Cline VarynForge set_opportunity_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI VarynForge set_opportunity_status ~/.gemini/settings.json
- Grok VarynForge set_opportunity_status .mcp.json (in your project root)
- ChatGPT VarynForge set_opportunity_status Settings → Connectors → Advanced → Developer mode
- Claude.ai VarynForge set_opportunity_status Settings → Connectors → Add custom connector
- LangChain VarynForge set_opportunity_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http server https://app.varynforge.com/api/mcpOther tools on this server
- get_instructions
- get_changelog
- get_writer_system_prompt
- get_account_status
- list_organizations
- get_onboarding_guide
- send_feedback
- create_project
- get_project
- get_project_asset
- update_niche
- list_destinations
- add_destination
- list_competitors
- set_competitor_importance
- add_competitor_by_domain
- update_asset_profile
- set_posting_cadence
- resync_asset_profile
- remap_asset
- start_research_run
- list_projects
- get_competitor_detail
- get_project_overview
- get_research_status
- get_pitch_report_payload
- get_starting_point_report
- list_opportunities
- get_opportunity_detail
- set_excluded_terms
- list_keywords
- get_keyword_detail
- list_pages
- get_page_dossier
- list_article_suggestions
- create_content_plan_from_opportunities
- add_article_suggestion
- create_article_suggestion_with_input
- update_article_status
- generate_article_brief
- get_article_suggestion
- get_draft_status
- get_article_brief
- delete_article_suggestion
- download_brief_markdown
- mark_article_published
- register_derived_asset
- get_lint_rubric
- lint_draft
- get_write_handoff
- expand_idea
- accept_idea
- check_idea
- list_radar_topics
- expand_radar_topic
- add_radar_topic
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.