In-depth architectural comparison of the Crawlie and Timothe's Growth Calendar MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Crawlie
Marketing · Local stdio
Quality: 41/100 (Fair) | Auth: No auth required
Timothe's Growth Calendar
Marketing · Remote HTTP/SSE
Quality: 39/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Crawlie if you need specialized Marketing tools running via a local process. Choose Timothe's Growth Calendar if your workspace requires Marketing integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Crawlie when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Crawlie is categorized under Marketing and uses a local stdio subprocess. In contrast, Timothe's Growth Calendar belongs to Marketing using remote streaming HTTP/SSE transport. Select Crawlie when you need capabilities focused on marketing and Timothe's Growth Calendar when you require tools for marketing.