dchub_services — DC Hub MCP Tool
dchub_services
(dchub services) is one of 96 tools on the
DC Hub
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call dchub_services from your client
- Claude Code DC Hub dchub_services run in your project directory
- Claude Desktop DC Hub dchub_services ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DC Hub dchub_services ~/.cursor/mcp.json
- VS Code DC Hub dchub_services .vscode/mcp.json
- Zed DC Hub dchub_services ~/.config/zed/settings.json
- Windsurf DC Hub dchub_services ~/.codeium/windsurf/mcp_config.json
- Cline DC Hub dchub_services ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DC Hub dchub_services ~/.gemini/settings.json
- Grok DC Hub dchub_services .mcp.json (in your project root)
- ChatGPT DC Hub dchub_services Settings → Connectors → Advanced → Developer mode
- Claude.ai DC Hub dchub_services Settings → Connectors → Add custom connector
- LangChain DC Hub dchub_services pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp-server https://dchub.cloud/mcp/registryOther tools on this server
- execute_plan
- claim_free_key
- search
- fetch
- search_facilities
- get_facility
- get_market_intel
- get_market_dcpi_rank
- predict_market_trajectory
- get_gas_index
- get_gas_economics
- get_grid_scoreboard
- compare_isos
- get_intelligence_index
- list_transactions
- get_news
- semantic_search
- search_intelligence
- get_market_context
- get_iso_context
- get_pipeline
- get_power_pipeline
- get_infra_projects
- get_power_availability_timeline
- get_global_power
- get_interconnection_queue
- get_refined_queue
- get_retirement_headroom
- get_hosting_capacity
- analyze_parcel
- rank_sites
- discover_tools
- plan_query
- save_to_shortlist
- get_shortlist
- set_shortlist_alert
- suggest_reallocation
- get_grid_data
- get_changes
- get_facility_risk_delta
- save_site
- list_saved_sites
- set_market_alert
- subscribe_digest
- set_site_alert
- export_dataset
- find_sites
- analyze_site
- get_composite_site_score
- get_disaster_risk
- get_climate_intel
- generate_site_analysis
- compare_sites
- get_infrastructure
- get_fiber_intel
- get_fiber_readiness
- get_subsea_cables
- get_peering_intel
- get_metro_fiber
- get_energy_prices
- get_renewable_energy
- get_tax_incentives
- get_water_risk
- get_grid_intelligence
- get_gas_intelligence
- get_agent_registry
- get_backup_status
- summarize_for_citation
- why_dchub
- get_dchub_recommendation
- rank_markets
- find_alternatives
- score_facility
- ai_capacity_index
- hyperscaler_deals
- site_selection_canvas
- grid_transition_radar
- deal_autopsy
- get_permitting_intel
- get_air_permit_context
- simulate_scenario
- research_task
- list_standing_intents
- register_standing_intent
- delete_standing_intent
- plan_fiber_leadin
- cluster_sites_by_latency
- bind_email
- recover_my_key
- source_capacity
- request_capacity_intro
- accept_capacity_terms
- unlock_more_data
- read_inbox
- report_finding
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.