entity_profile — Data Brussels MCP Tool
entity_profile
(entity profile) is one of 39 tools on the
Data Brussels
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call entity_profile from your client
- Claude Code Data Brussels entity_profile run in your project directory
- Claude Desktop Data Brussels entity_profile ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Data Brussels entity_profile ~/.cursor/mcp.json
- VS Code Data Brussels entity_profile .vscode/mcp.json
- Zed Data Brussels entity_profile ~/.config/zed/settings.json
- Windsurf Data Brussels entity_profile ~/.codeium/windsurf/mcp_config.json
- Cline Data Brussels entity_profile ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Data Brussels entity_profile ~/.gemini/settings.json
- Grok Data Brussels entity_profile .mcp.json (in your project root)
- ChatGPT Data Brussels entity_profile Settings → Connectors → Advanced → Developer mode
- Claude.ai Data Brussels entity_profile Settings → Connectors → Add custom connector
- LangChain Data Brussels entity_profile pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http data-brussels https://gateway.pipeworx.io/data-brussels/mcp
Other tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- recent_changes
- validate_claim
- company_facts
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- search_datasets
- dataset_info
- query
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.