Openaffiliate MCP vs Timothe's Growth Calendar
A side-by-side look at the Openaffiliate MCP and Timothe's Growth Calendar MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Openaffiliate MCP for marketing work as a local process; choose Timothe's Growth Calendar for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose Timothe's Growth Calendar when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 65/100 · Great | 36/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 119 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Openaffiliate MCP | View Timothe's Growth Calendar |
Tools & capabilities
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
Timothe's Growth Calendar tools
No tool names declared yet. Check the project README from the listing page.
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.
Openaffiliate MCP
{
"mcpServers": {
"openaffiliate-mcp": {
"command": "npx",
"args": [
"openaffiliate-mcp"
]
}
}
}
Timothe's Growth Calendar
{
"mcpServers": {
"timothe-s-growth-calendar": {
"url": "https://timothe.ai/mcp/growth-calendar"
}
}
}
Frequently asked questions
Openaffiliate MCP is categorized under Marketing and uses a local stdio subprocess. Timothe's Growth Calendar belongs to Marketing and uses a remote HTTP/SSE transport. Pick Openaffiliate MCP for marketing work and Timothe's Growth Calendar 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.
Openaffiliate MCP is listed as free. Auth: no auth required. Timothe's Growth Calendar has no declared pricing — check the project's own site. 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 openaffiliate-mcp and timothe-s-growth-calendar as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Openaffiliate MCP has a quality signal of 65/100 (Great) with 2 views, 0 installs and 119 GitHub stars. Timothe's Growth Calendar has 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.