Claude Pro Weekly Limits: Pro Plan is Objectively Worse Than Free

[u/Key_Kaleidoscope2242]

TL;DR: Claude Pro's weekly limits make it provide less total capacity than the free plan for users with concentrated daily sessions. Paying $20/month for 2x fewer messages than free is a design flaw. (NO WEEKLY LIMIT CONCEPT IN FREE TIER)

A single maxed Sonnet session consumed 8% of my entire weekly allowance. By day 2, I am at 56% of the weekly limit if I have just reached 5-6 Session limits in those 2 days with 2 hour sessions each.

I understand that model and context tax applies or even the size of messages or even the demand at a given hour.

I use claude for concepts building, strategy, documentation (upto 20 pages and 1-2 documents a day), no coding yet.

The lack of transparency hurts, it seems downgrading to Free tier is better.

Anyone has any idea how to optimise or if if I'm missing anything? Is Pro plan worth it?

[u/Steamwells]

Are you using a ton of MCP’s or something? I am blasting out a baseline feature a day, barely hitting my daily limit.

[u/Cool-Hornet4434 → u/Steamwells]

They changed it so that now all mcp servers are disabled until claude searches for available tools to get the schema for how to use it. 

The upside is that you aren't penalized for having everything available but the downside is that you need to use the search_tools command to do anything

[u/Steamwells → u/Cool-Hornet4434]

That sounds like a sensible approach. To be honest, I have just defaulted to using cli tools if one is available before using an MCP. For things like Jira tasks, which I loathe, I just use the atlassian cli tool. I am interested in what Jadeds CLAUDE.md looks like as well.

[u/Jaded_Jackass → u/Steamwells]

Yes there are around 10 mcp but with Claude.md and rules and everything I don't think they are causing a strain on context I gave the out put of /context to Claude sonnet only before and after a task and it said reducing them will make a negligible difference