Growth Hacker MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_hooksC | Generate viral hooks for X (Twitter) threads based on a topic. |
| format_threadC | Split long text into a numbered X (Twitter) thread (1/x). |
| audit_copyC | Audit sales copy for Gumroad/Landing pages and give a score. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: auditing sales copy, formatting text into threads, and generating viral hooks. There is no overlap in functionality, making it easy for an agent to select the right tool without confusion.
All tool names follow a consistent verb_noun pattern (audit_copy, format_thread, generate_hooks), using snake_case throughout. This predictability enhances readability and usability.
With only 3 tools, the set feels thin for a 'Growth Hacker' domain, which typically involves broader tasks like analytics, A/B testing, or campaign management. While the tools are focused, the count may limit comprehensive growth hacking workflows.
The toolset is severely incomplete for growth hacking, missing core operations such as data analysis, user engagement tracking, or performance optimization. It covers only copy and social media aspects, leaving significant gaps that could hinder agent effectiveness.