Timothe's Growth Calendar

Official registry Productivity

Plan, schedule and generate SEO articles on a content calendar, from your agent.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http timothe-s-growth-calendar 'https://timothe.ai/mcp/growth-calendar'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "timothe-s-growth-calendar": {
            "type": "http",
            "url": "https://timothe.ai/mcp/growth-calendar"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Timothe plugins

Plugins that connect Timothe tools to your AI agent, so you can work with them from Claude Code, Claude, Codex or ChatGPT instead of switching to a browser tab.

Each plugin bundles a skill (how to use the tool well) with a connection to Timothe's hosted MCP server. There is nothing to run locally.

Growth Calendar

Plan, schedule and generate SEO articles on a content calendar.

Ask your agent to show what is scheduled this month, plan a topic cluster, move or retitle a planned article, or write one now. Article generation runs unattended on its publish date, so the calendar keeps working after you close the terminal.

Your agent can also check real Google search demand before you commit to anything: monthly search volumes for a market, who currently ranks for a query, and which keywords bring a competitor its traffic. It is the same data our own research runs on, so you can settle whether a topic is worth the effort in the same conversation where you plan it.

Install

Claude Code

/plugin marketplace add u17g/timothe-ai-plugins
/plugin install timothe-growth-calendar@timothe-plugins

Codex

codex plugin marketplace add u17g/timothe-ai-plugins
codex plugin add timothe-growth-calendar@timothe-plugins

OpenClaw

openclaw mcp add growth-calendar --url https://timothe.ai/mcp/growth-calendar --transport streamable-http --auth oauth
openclaw mcp login growth-calendar
openclaw skills install @timothe/growth-calendar

Claude, Cowork and Claude Desktop do not use plugins. Add the server directly under Settings > Connectors with this URL:

https://timothe.ai/mcp/growth-calendar

ChatGPT needs developer mode enabled (Plus plan or above), then add a custom connector with the same URL.

Signing in

The first call opens your browser to sign in to Timothe. Your agent handles the rest, including refreshing the session later. In Claude Code you can trigger it explicitly with /mcp; in Codex, with codex mcp login growth-calendar; in OpenClaw, with openclaw mcp login growth-calendar.

The connection acts on one Timothe workspace. If you belong to several, it binds to your current one the first time you use it.

What you need

A Timothe account on a paid plan. Reading the calendar is free. The keyword and SERP lookups spend a few credits each; planning a cluster and generating an article spend a lot more. Your agent is told every cost up front and will tell you before spending anything.

License

MIT

Frequently asked questions

What is Timothe's Growth Calendar?

Plan, schedule and generate SEO articles on a content calendar, from your agent.

How do I install Timothe's Growth Calendar?

It runs as a remote server. In Claude Code: claude mcp add --transport http timothe-s-growth-calendar 'https://timothe.ai/mcp/growth-calendar'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Timothe's Growth Calendar need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Timothe's Growth Calendar open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Timothe's Growth Calendar?

It is published by u17g. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.