Memory Chapter Overview — GrowthKit Revenue Intelligence MCP Resource

Memory Chapter Overview 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 Memory Chapter Overview from your client

• Claude Code GrowthKit Revenue Intelligence Resource/Memory Chapter Overview run in your project directory
• Claude Desktop GrowthKit Revenue Intelligence Resource/Memory Chapter Overview ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor GrowthKit Revenue Intelligence Resource/Memory Chapter Overview ~/.cursor/mcp.json
• VS Code GrowthKit Revenue Intelligence Resource/Memory Chapter Overview .vscode/mcp.json
• Zed GrowthKit Revenue Intelligence Resource/Memory Chapter Overview ~/.config/zed/settings.json
• Windsurf GrowthKit Revenue Intelligence Resource/Memory Chapter Overview ~/.codeium/windsurf/mcp_config.json
• Cline GrowthKit Revenue Intelligence Resource/Memory Chapter Overview ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI GrowthKit Revenue Intelligence Resource/Memory Chapter Overview ~/.gemini/settings.json
• Grok GrowthKit Revenue Intelligence Resource/Memory Chapter Overview .mcp.json (in your project root)
• ChatGPT GrowthKit Revenue Intelligence Resource/Memory Chapter Overview Settings → Connectors → Advanced → Developer mode
• Claude.ai GrowthKit Revenue Intelligence Resource/Memory Chapter Overview Settings → Connectors → Add custom connector
• LangChain GrowthKit Revenue Intelligence Resource/Memory Chapter Overview pip install langchain-mcp-adapters

Other resources on this server

• Ideal Customer Profile
• Brand Voice & Messaging
• Positioning & Strategy
• Intent Signals
• Sales Analytics & KPIs

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.