Prompt-caching – auto-injects Anthropic cache breakpoints (90% token savings)
1–10 of 33 posts
Re: Prompt-caching – auto-injects Anthropic cache breakpoints (90% token savings)
#2[dead]
Re: Prompt-caching – auto-injects Anthropic cache breakpoints (90% token savings)
#3Will this work for Cowork as well?
Re: Prompt-caching – auto-injects Anthropic cache breakpoints (90% token savings)
#4Hasn't this been largely solved by auto-caching introduced recently by Anthropic, where you pass "cache_control": {"type": "ephemeral"} in your request and it puts breakpoints automatically? https://platform.claude.com/docs/en/build-with-claude/prompt...
Re: Prompt-caching – auto-injects Anthropic cache breakpoints (90% token savings)
#5Will this work for Cowork as well?
This is not at all an MCP server you want to use with a regular tool, as this is about low level context window management. Tbh it’s really trivial to do this, and I have no idea why OP decided to make an MCP server for this as it’s completely useless for that.
As a matter of fact, i think this is not a problem at all as Anthropic makes it extremely easy to cache stuff; you just set your preferred cache level on the last message, and Anthropic will automatically cache it under the hood. Every distinct message is another “cache” point, eg they first compute the hash of all messages, if not found, compute the hash of all messages - 1, etc.
It’s really a non problem.
Re: Prompt-caching – auto-injects Anthropic cache breakpoints (90% token savings)
#6I don't understand, Claude code already has automatic prompt caching built in.[0] How does this change things?
Re: Prompt-caching – auto-injects Anthropic cache breakpoints (90% token savings)
#7Hasn't this been largely solved by auto-caching introduced recently by Anthropic, where you pass "cache_control": {"type": "ephemeral"} in your request and it puts breakpoints automatically? https://platform.claude.com/docs/en/build-with-claude/prompt...
Yes, it has, this is a non-problem, and even if it was a problem, an MCP server would most definitely be one of the worst ways to fix it.
Re: Prompt-caching – auto-injects Anthropic cache breakpoints (90% token savings)
#8Hasn't this been largely solved by auto-caching introduced recently by Anthropic, where you pass "cache_control": {"type": "ephemeral"} in your request and it puts breakpoints automatically? https://platform.claude.com/docs/en/build-with-claude/prompt...
Looking at my own usage with claude code out of the box and nothing special around caching set up. For this month according to ccusage I have in tokens 0.2M input, 0.6M output, 10M cache create, 311M cache read for 322M total tokens.
Seems to me that it caches out of the box quite heavily, but if I can trim my usage somehow with these kind of tools I'd love to know.
Re: Prompt-caching – auto-injects Anthropic cache breakpoints (90% token savings)
#9[deleted]
Re: Prompt-caching – auto-injects Anthropic cache breakpoints (90% token savings)
#10> This plugin is built for developers building their own applications with the Anthropic API.
> Important note for Claude Code users: Claude Code already handles prompt caching automatically for its own API calls — system prompts, tool definitions, and conversation history are cached out of the box.
Source: their GitHub