get_competitive_profile — IndustryLens MCP Tool Read-only
get_competitive_profile
(get competitive profile) is one of 12 tools on the
IndustryLens
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_competitive_profile from your client
- Claude Code IndustryLens get_competitive_profile run in your project directory
- Claude Desktop IndustryLens get_competitive_profile ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor IndustryLens get_competitive_profile ~/.cursor/mcp.json
- VS Code IndustryLens get_competitive_profile .vscode/mcp.json
- Zed IndustryLens get_competitive_profile ~/.config/zed/settings.json
- Windsurf IndustryLens get_competitive_profile ~/.codeium/windsurf/mcp_config.json
- Cline IndustryLens get_competitive_profile ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI IndustryLens get_competitive_profile ~/.gemini/settings.json
- Grok IndustryLens get_competitive_profile .mcp.json (in your project root)
- ChatGPT IndustryLens get_competitive_profile Settings → Connectors → Advanced → Developer mode
- Claude.ai IndustryLens get_competitive_profile Settings → Connectors → Add custom connector
- LangChain IndustryLens get_competitive_profile pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp-public https://api.industry-lens.com/mcp/publicOther tools on this server
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.