run_business_study — opportunity exchange MCP Tool Mutating
run_business_study
(run business study) is one of 72 tools on the
opportunity exchange
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call run_business_study from your client
- Claude Code opportunity exchange run_business_study run in your project directory
- Claude Desktop opportunity exchange run_business_study ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor opportunity exchange run_business_study ~/.cursor/mcp.json
- VS Code opportunity exchange run_business_study .vscode/mcp.json
- Zed opportunity exchange run_business_study ~/.config/zed/settings.json
- Windsurf opportunity exchange run_business_study ~/.codeium/windsurf/mcp_config.json
- Cline opportunity exchange run_business_study ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI opportunity exchange run_business_study ~/.gemini/settings.json
- Grok opportunity exchange run_business_study .mcp.json (in your project root)
- ChatGPT opportunity exchange run_business_study Settings → Connectors → Advanced → Developer mode
- Claude.ai opportunity exchange run_business_study Settings → Connectors → Add custom connector
- LangChain opportunity exchange run_business_study pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http opportunity-exchange https://veilpoint.ca/mcpOther tools on this server
- investigate_economic_question
- inspect_knowledge_frontier
- resolve_entities
- get_entity_context
- query_knowledge_graph
- get_knowledge_graph_status
- compare_municipalities
- list_roles
- get_role
- compare_roles
- search_hiring_activity
- compare_outcomes
- rank_communities
- list_sectors
- get_sector
- summarize_credential_demand
- search_employers
- get_trade_overview
- get_real_estate
- search_licensed_businesses
- get_wages
- get_rents
- list_noc_groups
- evaluate_pathways
- inspect_procurement_activity
- assess_procurement_relevance
- assess_workforce_demand
- find_potential_suppliers
- find_potential_customers
- list_economic_signals
- get_economic_signal
- get_emerging_signals
- get_data_sources
- get_data_providers
- get_source_provenance
- resolve_citation
- get_economy_overview
- get_municipality_evidence_coverage
- get_community_economy
- resolve_entity
- get_entity
- search_entities
- search_businesses
- get_business_evidence
- get_community_profile
- compare_communities
- get_labour_demand
- get_wage_evidence
- traverse_relationships
- find_connected_entities
- get_evidence
- explain_confidence
- explain_truth_state
- check_comparability
- check_business_health
- explain_business_claim
- list_health_capabilities
- create_sandbox_business
- list_sandbox_businesses
- get_business_health
- get_business_health_markdown
- update_business_record
- grant_business_consent
- set_website_domain
- get_generated_asset
- start_health_action
- report_health_action_complete
- recheck_business_health
- get_health_action_history
- check_opportunity_readiness
- run_business_study_markdown
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.