Ideal Customer Profile — GrowthKit Revenue Intelligence MCP Resource
Ideal Customer Profile
is one of 6 resources on the
GrowthKit Revenue Intelligence
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Ideal Customer Profile from your client
- Claude Code GrowthKit Revenue Intelligence Resource/Ideal Customer Profile run in your project directory
- Claude Desktop GrowthKit Revenue Intelligence Resource/Ideal Customer Profile ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor GrowthKit Revenue Intelligence Resource/Ideal Customer Profile ~/.cursor/mcp.json
- VS Code GrowthKit Revenue Intelligence Resource/Ideal Customer Profile .vscode/mcp.json
- Zed GrowthKit Revenue Intelligence Resource/Ideal Customer Profile ~/.config/zed/settings.json
- Windsurf GrowthKit Revenue Intelligence Resource/Ideal Customer Profile ~/.codeium/windsurf/mcp_config.json
- Cline GrowthKit Revenue Intelligence Resource/Ideal Customer Profile ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI GrowthKit Revenue Intelligence Resource/Ideal Customer Profile ~/.gemini/settings.json
- Grok GrowthKit Revenue Intelligence Resource/Ideal Customer Profile .mcp.json (in your project root)
- ChatGPT GrowthKit Revenue Intelligence Resource/Ideal Customer Profile Settings → Connectors → Advanced → Developer mode
- Claude.ai GrowthKit Revenue Intelligence Resource/Ideal Customer Profile Settings → Connectors → Add custom connector
- LangChain GrowthKit Revenue Intelligence Resource/Ideal Customer Profile pip install langchain-mcp-adapters
Other resources on this server
GrowthKit Revenue Intelligence also offers 6 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.