Timothe's Growth Calendar vs Openaffiliate MCP
A side-by-side look at the Timothe's Growth Calendar and Openaffiliate MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Timothe's Growth Calendar for marketing work over a hosted endpoint; choose Openaffiliate MCP for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Timothe's Growth Calendar when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Choose Openaffiliate MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
search_programs, get_program, list_categories.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 36/100 · Fair | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 119 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Timothe's Growth Calendar | View Openaffiliate MCP |
Tools & capabilities
Timothe's Growth Calendar tools
No tool names declared yet. Check the project README from the listing page.
Openaffiliate MCP tools 3
search_programsSearch affiliate programs by keyword, category, or commission typeget_programGet full details of an affiliate program including agent instructions, commission terms, restrictions, and signup infolist_categoriesList all affiliate program categories with the number of programs in each
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Timothe's Growth Calendar
{
"mcpServers": {
"timothe-s-growth-calendar": {
"url": "https://timothe.ai/mcp/growth-calendar"
}
}
}
Openaffiliate MCP
{
"mcpServers": {
"openaffiliate-mcp": {
"command": "npx",
"args": [
"openaffiliate-mcp"
]
}
}
}
Frequently asked questions
Timothe's Growth Calendar is categorized under Marketing and uses a remote HTTP/SSE transport. Openaffiliate MCP belongs to Marketing and uses a local stdio subprocess. Pick Timothe's Growth Calendar for marketing work and Openaffiliate MCP for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Timothe's Growth Calendar has no declared pricing — check the project's own site. Openaffiliate MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add timothe-s-growth-calendar and openaffiliate-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Timothe's Growth Calendar has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Openaffiliate MCP has 65/100 (Great) with 2 views, 0 installs and 119 GitHub stars.