Growth Calendar MCP server
{
"mcpServers": {
"timothe-growth-calendar": {
"type": "http",
"url": "https://timothe.ai/mcp/growth-calendar"
}
}
}{
"mcpServers": {
"timothe-growth-calendar": {
"type": "http",
"url": "https://timothe.ai/mcp/growth-calendar"
}
}
}{
"mcpServers": {
"timothe-growth-calendar": {
"type": "http",
"url": "https://timothe.ai/mcp/growth-calendar"
}
}
}{
"servers": {
"timothe-growth-calendar": {
"type": "http",
"url": "https://timothe.ai/mcp/growth-calendar"
}
}
}{
"mcpServers": {
"timothe-growth-calendar": {
"type": "http",
"url": "https://timothe.ai/mcp/growth-calendar"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.1.0
What it does
Growth Calendar is a hosted MCP server that connects AI agents (Claude, Codex, ChatGPT) to Timothe's content calendar service. It lets agents view, plan, and schedule SEO articles, look up keyword search volumes, and check SERP rankings without leaving the agent interface.
- View what articles are scheduled this month and reschedule or retitle planned entries from within your agent.
- Research keyword demand and competitor traffic before committing to a topic cluster.
- Plan a topic cluster and queue articles for unattended generation on their publish dates.
Tools this server exposes
| Tool | Does |
|---|---|
| show_calendar | Retrieves the scheduled articles on the content calendar for a given period. |
| plan_cluster | Creates a topic cluster and schedules related articles on the calendar. |
| move_article | Reschedules or retitles a planned article on the calendar. |
| generate_article | Triggers immediate SEO article generation for a calendar entry. |
| keyword_volume | Returns monthly search volumes for keywords in a given market. |
| serp_lookup | Shows which sites currently rank for a specific search query. |
| competitor_keywords | Identifies which keywords drive traffic to a competitor's site. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.