data_centre_market_overview — ScienceShot data-centre intelligence MCP Tool
data_centre_market_overview
(data centre market overview) is one of 5 tools on the
ScienceShot data-centre intelligence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call data_centre_market_overview from your client
- Claude Code ScienceShot data-centre intelligence data_centre_market_overview run in your project directory
- Claude Desktop ScienceShot data-centre intelligence data_centre_market_overview ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ScienceShot data-centre intelligence data_centre_market_overview ~/.cursor/mcp.json
- VS Code ScienceShot data-centre intelligence data_centre_market_overview .vscode/mcp.json
- Zed ScienceShot data-centre intelligence data_centre_market_overview ~/.config/zed/settings.json
- Windsurf ScienceShot data-centre intelligence data_centre_market_overview ~/.codeium/windsurf/mcp_config.json
- Cline ScienceShot data-centre intelligence data_centre_market_overview ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ScienceShot data-centre intelligence data_centre_market_overview ~/.gemini/settings.json
- Grok ScienceShot data-centre intelligence data_centre_market_overview .mcp.json (in your project root)
- ChatGPT ScienceShot data-centre intelligence data_centre_market_overview Settings → Connectors → Advanced → Developer mode
- Claude.ai ScienceShot data-centre intelligence data_centre_market_overview Settings → Connectors → Add custom connector
- LangChain ScienceShot data-centre intelligence data_centre_market_overview pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http data-centres https://scienceshot.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 15 October 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.