Positioning & Strategy — GrowthKit Revenue Intelligence MCP Resource
Positioning & Strategy
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 Positioning & Strategy from your client
- Claude Code GrowthKit Revenue Intelligence Resource/Positioning & Strategy run in your project directory
- Claude Desktop GrowthKit Revenue Intelligence Resource/Positioning & Strategy ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor GrowthKit Revenue Intelligence Resource/Positioning & Strategy ~/.cursor/mcp.json
- VS Code GrowthKit Revenue Intelligence Resource/Positioning & Strategy .vscode/mcp.json
- Zed GrowthKit Revenue Intelligence Resource/Positioning & Strategy ~/.config/zed/settings.json
- Windsurf GrowthKit Revenue Intelligence Resource/Positioning & Strategy ~/.codeium/windsurf/mcp_config.json
- Cline GrowthKit Revenue Intelligence Resource/Positioning & Strategy ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI GrowthKit Revenue Intelligence Resource/Positioning & Strategy ~/.gemini/settings.json
- Grok GrowthKit Revenue Intelligence Resource/Positioning & Strategy .mcp.json (in your project root)
- ChatGPT GrowthKit Revenue Intelligence Resource/Positioning & Strategy Settings → Connectors → Advanced → Developer mode
- Claude.ai GrowthKit Revenue Intelligence Resource/Positioning & Strategy Settings → Connectors → Add custom connector
- LangChain GrowthKit Revenue Intelligence Resource/Positioning & Strategy 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.