This comment from Tadas Antanavicius, about Claude Code from Anthropic caused quite the response in this week's newsletter from PulseMCP:

(1/7) Inspired largely by cat's post claiming that Claude Code + Opus 4 was a new unlock for software engineering, I dug in to try it out myself. It sure delivers. The secret sauce: combine Claude Code with git worktrees 🧵

Thanks for the shout, May Walter!

We released a new MCP specification: 2025-06-18. It contains a lot of improvements over the previous version: We improved how authorization works making it easier for enterprises to build with MCP, added elicitation and resource links and more: modelcontextprotocol.io/specification/…

MCP is proving sticky: usage numbers are growing steadily, month over month. We saw an all time high of 7.4m estimated downloads of local MCP servers across the ecosystem last month. This is all still hamstrung by so-so MCP server implementation quality and the spec having

Was away from X for a while. Lots of catch up to do. In the meantime, MCP now has a bit more formal governance process on how to propose changes and a more formal set of decision makers, that will help the project scale. See github.com/modelcontextpr…

big goose update today

Looks like GitHub is working with PulseMCP on an MCP registry. Talking about the drawbacks of the current solution…

We believe a lot of automation projects fail because they try to change everything at once. Parts II & III of our Goose handbook (w/ @blockopensource ) are now live, covering: ✅ How to sequence your roadmap for continuous value and small wins at every step ✅ Why agent

Good automation is opinionated. @PulseMCP built a Goose workflow where each subagent has a single role, clear boundaries, and predictable handoffs so the human stays in charge. block.github.io/goose/blog/202…

MCP servers have a killer use case: you can use them to “close the agentic loop” for agents like Claude Code, Cursor, Goose, Cline, and others. I’ve found that closing the loop with an MCP server is often what evolves “cute demo” to “actually practical use case”

𝗔𝗿𝗲 𝘆𝗼𝘂 𝗷𝗼𝗶𝗻𝗶𝗻𝗴 𝘂𝘀? London is calling 💂 On 2 October, the MCP Dev Summit EU will gather the community for a full day of learning and connection. Details are here: mcpdevsummit.ai #MCP #MCPDevsummit #LondonTech

Thanks to PulseMCP for this amazing article! The killer feature of MCP is Iteration and closing the loop: pulsemcp.com/posts/closing-…

How do you price something that's never been priced before? We're excited to share a guest post from Matt Dailey, founder of Ref, who tackled this exact challenge while building what may be the first standalone paid MCP server. Read it here: pulsemcp.com/posts/pricing-… His

Super excited to be included in the latest MCP Weekly Pulse by the PulseMCP team! We're only in the 1st or 2nd inning of MCP and agentic systems, but I couldn't be more excited to be building open tooling for MCP developers. V1 of Shinzo is out now, DM me for access :)

We like how you think :)