MCP
A protocol for connecting tools to AI agents; the newsletter contrasts bulky MCP setups with lighter skill-based integrations.
Key Highlights
- MCP is a protocol for connecting external tools and services to AI agents through structured interfaces.
- The newsletter positions MCP as powerful but often heavier-weight than local skill-based integrations.
- Security and authorization are recurring concerns, especially for autonomous agents acting across multiple systems.
- Anthropic, Claude Code, v0, and Figma are key examples of products operationalizing MCP workflows.
- For AI PMs, MCP is most useful when reliability, freshness, and deterministic access matter more than setup simplicity.
MCP
Overview
MCP, short for Model Context Protocol, is a protocol and integration pattern for connecting external tools, data sources, and services to AI agents. In the newsletter, it appears as the connective layer that lets systems like Claude Code, v0, and other agentic products access software such as Figma, GitHub, Storybook, Gmail, Google Calendar, Notion, Stripe, Telegram, and Discord through standardized tool interfaces.For AI Product Managers, MCP matters because it sits at the center of a major product design question: how should AI systems access capabilities and context safely, reliably, and with minimal friction? The coverage contrasts heavyweight MCP-based setups with lighter-weight, local “skills” or natural-language integrations. That tradeoff makes MCP strategically important: it can provide structured, up-to-date, schema-driven access to tools, but it also introduces product complexity around security, authorization, developer experience, and server design.
Key Developments
- 2026-02-23: Anthropic’s Advanced Tool Calling coverage highlighted programmatic tool calling via code execution, including MCP function invocation to reduce token usage and improve agent efficiency.
- 2026-02-27: Dharmesh Shah argued that platforms should consider CLIs alongside APIs and MCP for agentic workflows, while Peter Yang suggested MCP servers should come after single-purpose APIs and agent-readable documentation are in place.
- 2026-03-04: Newsletter coverage framed MCP as part of a growing agent security problem, noting that static API keys are inadequate and OAuth 2.1/PKCE can be too complex for autonomous multi-system agents.
- 2026-03-08: v0 added support for custom MCP servers in its API through an `mcpServerIds` parameter, making MCP a configurable part of product workflow orchestration.
- 2026-03-14: LlamaIndex compared MCP tools with local Skills, arguing that MCP’s fixed-schema API calls provide more precise and current context for fast-changing domains, while Skills are faster to set up but more prone to hallucination.
- 2026-03-17: Marily Nika, Aman Khan, and Tal Raviv were mentioned in connection with live OpenClaw and MCP builds focused on teaching practical AI product sense.
- 2026-03-18: Anthropic MCP connectors were highlighted as enabling agents to use Gmail, Google Calendar, Granola, Notion, and Stripe; the same mention contrasted these connectors with custom local skills stored in `.claude/skills`.
- 2026-03-20: Anthropic released Claude Code channels, allowing users to control Claude Code sessions through select MCPs, initially Telegram and Discord.
- 2026-03-30: Figma’s new MCP was highlighted in a workflow where a rough Figma sketch was turned into a polished design through Claude Code, showing MCP’s role in design-to-build loops.
- 2026-04-03: MCP was cited as one of the sources of truth teams use to import design systems into AI prototyping tools, alongside Figma, GitHub, and Storybook.
Relevance to AI PMs
1. Choose the right integration layer for the job. AI PMs need to decide when a structured MCP integration is worth the overhead versus when a lighter skill-based approach is sufficient. MCP is more valuable when accuracy, freshness, and deterministic tool access matter.2. Design for security and authorization early. MCP expands what agents can do across systems, which makes auth, credential scope, token lifetimes, and permissioning product requirements rather than backend details. If your product supports autonomous actions, security architecture becomes part of the user experience.
3. Sequence your platform strategy correctly. The newsletter repeatedly suggests that teams should first expose clean, single-purpose APIs or CLIs with strong documentation, then add MCP on top. For PMs, this means MCP should often be treated as an enablement layer, not the first product surface you build.
Related
- Anthropic / Claude / Claude Code: Major drivers of MCP adoption in the newsletter, especially via connectors, channels, and agent workflows.
- Figma, GitHub, Storybook: Examples of systems being used as sources of truth or integrated into AI prototyping and design workflows via MCP.
- Telegram, Discord: Early communication surfaces used with Claude Code channels through MCP.
- Gmail, Google Calendar, Notion, Stripe: Common SaaS tools connected to agents through MCP connectors.
- v0 and vercel-mcp: Examples of productized MCP server support in application APIs.
- LlamaIndex, skills, tool-calling: Closely related concepts used to compare structured tool access with lighter or more localized alternatives.
- OAuth 2.1, PKCE, APIs, CLI: Supporting infrastructure and adjacent patterns that shape how viable, secure, and usable MCP deployments are.
- OpenClaw, webMCP, Zapier MCP, studio-mcp-server, mcp-porter: Examples of the broader tooling ecosystem forming around MCP-based agent workflows.
Newsletter Mentions (18)
“in Colin Matthews reports that only ~20 of 51 teams importing design systems into AI prototyping tools use Figma as their source of truth, with the remainder on GitHub, Storybook or MCP.”
#9 in Colin Matthews reports that only ~20 of 51 teams importing design systems into AI prototyping tools use Figma as their source of truth, with the remainder on GitHub, Storybook or MCP. #10 𝕏 LlamaIndex 🦙 introduces Extract v2 with simplified tiers, pre-saved extraction configurations, and fully configurable document parsing for more powerful, streamlined data extraction.
“#8 𝕏 Thariq is excited about Figma’s new MCP, starting with a rough Figma sketch that Claude Code fleshes out into a polished design which he then iterates on before final review.”
#4 𝕏 Thariq sketched a new grocery-list feature in Figma and then prompted an AI to convert the mockup into his app’s style while adding extra components. #5 𝕏 Peter Yang suggests that any account replying to over a dozen posts within five seconds is likely AI-generated. #6 in Thomas Hendrickx recommends Claire Vo’s How I AI YouTube series for its hands-on, real-world AI workflows—product builds, system setups like Teresa Torres’ Obsidian setup—rather than generic demos. #7 𝕏 Lenny Rachitsky : Claire Vo built 9 OpenClaw agents across 3 Mac Minis to automate sales outreach (replacing a 10 hr/week rep), family scheduling, podcast prep, homework help, and course project management. #8 𝕏 Thariq is excited about Figma’s new MCP, starting with a rough Figma sketch that Claude Code fleshes out into a polished design which he then iterates on before final review. #9 𝕏 There's An AI For That unveiled upgraded autonomous bots that carry up to 25 kg (55 lb), clear 30 cm (12 in) obstacles, mount heavier payloads like micro-missiles and grenade launchers, and use a “collective brain” for real-time data sharing and coordinated action.
“Anthropic releases Claude Code channels - We just released Claude Code channels, which allows you to control your Claude Code session through select MCPs, starting with Telegram and Discord.”
#1 𝕏 Anthropic releases Claude Code channels - We just released Claude Code channels, which allows you to control your Claude Code session through select MCPs, starting with Telegram and Discord. Use this to message Claude Code directly from your phone. #2 📝 OpenAI News OpenAI to acquire Astral - OpenAI announces its intent to acquire Astral to enhance its capabilities, bringing together teams and technology to accelerate product development and research.
“MCP (Model-Context-Protocol) connectors by Anthropic enable agents to use Gmail, Google Calendar, Granola, Notion, and Stripe; custom skills stored in .claude/skills (e.g., ads analyst skill scraped 220 ads and landing pages to generate a competitor report that once required 3–4 hours manually).”
#10 ▶️ Building AI Agents that actually work (Full Course) Greg Isenberg Building an AI executive assistant agent using markdown context and memory files (agents.mmd, memory.mmd), MCP connectors for Gmail, Google Calendar, Granola, Notion, and Stripe, and custom skills within harnesses Claude Code, Codeex, and Anti-Gravity. Agent loop (observe, think, act) runs on LLMs such as Claude Opus 4.6, GPT 5.4, and Gemini 3 within harnesses Claude Code, Codeex, and Anti-Gravity, demonstrated by building a minimalist portfolio site for Greg Eisenberg via Perplexity research, code generation, localhost preview, and screenshot validation. Context is preloaded from agents.mmd (called claude.mmd or gemini.md per platform) and preferences are persisted in memory.mmd via “update memory.mmd” instructions to retain user settings across sessions. MCP (Model-Context-Protocol) connectors by Anthropic enable agents to use Gmail, Google Calendar, Granola, Notion, and Stripe; custom skills stored in .claude/skills (e.g., ads analyst skill scraped 220 ads and landing pages to generate a competitor report that once required 3–4 hours manually).
“#21 in Marily Nika, Ph.D warns that a rogue Chipotle burrito-bot demo exposed how AI products fail without steering guardrails.”
#21 in Marily Nika, Ph.D warns that a rogue Chipotle burrito-bot demo exposed how AI products fail without steering guardrails. She’s teaming with Aman Khan and Tal Raviv for live OpenClaw & MCP builds to teach true AI Product Sense.
“LlamaIndex 🦙 explains that MCP tools’ fixed-schema API calls give precise, always up-to-date context for fast-evolving domains, while local natural-language Skills offer quick setup at the cost of potential hallucinations; in practice, documentation MCPs beat custom Skills fo...”
LlamaIndex 🦙 explains that MCP tools’ fixed-schema API calls give precise, always up-to-date context for fast-evolving domains, while local natural-language Skills offer quick setup at the cost of potential hallucinations; in practice, documentation MCPs beat custom Skills fo...
“𝕏 v0 now supports custom MCP servers in its API—simply add an mcpServerIds array (e.g. ['vercel-mcp'] ) to your v0.chats.create call to route chat requests through your own MCP endpoints.”
𝕏 v0 now supports custom MCP servers in its API—simply add an mcpServerIds array (e.g. ['vercel-mcp'] ) to your v0.chats.create call to route chat requests through your own MCP endpoints.
“Santiago warns that the MCP-driven agent explosion has outpaced server security—static API keys are a disaster and wrestling with OAuth 2.1/PKCE is far too complex, yet you need dynamic, short-lived, tightly-scoped credentials for autonomous, multi-system agents.”
The newsletter frames MCP as part of the broader security and authorization problem for autonomous agents.
“in Dharmesh Shah argues that the composability and rich documentation of CLIs make them a perfect fit for agentic coding, and suggests platforms like HubSpot should offer a CLI interface alongside APIs and MCP to unlock more powerful agentic workflows.”
#13 in Dharmesh Shah argues that the composability and rich documentation of CLIs make them a perfect fit for agentic coding, and suggests platforms like HubSpot should offer a CLI interface alongside APIs and MCP to unlock more powerful agentic workflows. #16 𝕏 Peter Yang argues that building an MCP server should be the final step—first expose each capability as single-purpose, well-documented APIs with agent-readable docs and ensure your product works outside a human UI so AI agents can seamlessly chain tasks.
“#11 ▶️ Anthropic killed Tool calling AI Jason Entropic’s Advanced Tool Calling release introduces programmatic tool calling via a code execution sandbox, dynamic filtering for Web Fetch v2026209, deferred loading through Tool Search, and input examples for tool usage, boosting agent efficiency and reducing token consumption.”
#11 ▶️ Anthropic killed Tool calling AI Jason Entropic’s Advanced Tool Calling release introduces programmatic tool calling via a code execution sandbox, dynamic filtering for Web Fetch v2026209, deferred loading through Tool Search, and input examples for tool usage, boosting agent efficiency and reducing token consumption. Programmatic tool calling uses a code_execution sandbox and allowed_caller parameter to let models generate code that invokes multiple MCP functions, cutting token usage by 30–50%.
Related
Anthropic's coding-focused agentic tool for building and automating software workflows. In this newsletter it is discussed as being integrated with Vercel AI Gateway and as a Chrome extension for browser automation.
Anthropic is mentioned as a comparison point in the AI chess game and as the focus of a successful enterprise coding strategy. For PMs, it is framed as a company benefiting from sharp product focus.
Anthropic's general-purpose AI assistant and model family. It appears here as a comparison point for strategy work and in discussions around browser automation and coding.
An AI coding assistant/editor that can use dynamic context across models and MCP servers to reduce token usage. Useful for AI PMs thinking about agentic workflows, context management, and efficiency.
A writer/observer mentioned for a post about how vibe coding is reshaping developer workflows. Relevant to AI PMs for workflow and interface trends.
LlamaIndex is introducing integrations around agent workflows and spreadsheet cleanup. For AI PMs, it is building infrastructure for customizable agentic systems and data extraction workflows.
An open-source digital assistant built on Claude Code that can manage emails, transcribe audio, negotiate purchases, and automate tasks via skills and hooks.
OpenAI's chat-based AI assistant. It is mentioned as a comparison tool for strategy ideation alongside Claude.
A prompt monitoring and management tool referenced as a source to monitor AI feature developments. For PMs, it’s useful for staying current on model/API capabilities.
CRM and marketing software company whose agent platform is referenced as an example of low-code AI agents in RevOps.
A LinkedIn writer referenced for challenging hype-driven AI posting. Relevant to AI PMs for practical experimentation and operator-level sharing.
An AI app-building tool referenced here as highlighting a prompt directory for faster shipping. Relevant to PMs exploring rapid prototyping and app creation workflows.
Autonomous or semi-autonomous systems used here in sales and coding workflows. The newsletter highlights their role in replacing human SDR tasks and orchestrating complex tasks.
A design platform integrated into Notion’s AI-assisted prototype workflow through MCP. It serves as a source of frames and design context for prototype generation.
A software development platform included among Nebula’s integrations. It is mentioned as part of end-to-end AI agent workflows.
A W3C-backed browser extension that exposes website functionality to MCP-capable agents. It lets developers register site functions as structured tools in the browser.
An AI product leader or educator cited for showcasing live builds in Google AI Studio and GoogleLabs. She is relevant to AI PMs for prototyping and product experimentation workflows.
A messaging platform used here as a control surface for Claude Code channels.
Google's email product, referenced here as gaining Gemini-powered AI Inbox and Overviews features. For PMs, it is an example of AI being embedded into a mature productivity workflow.
A speaker or participant in a Zoom session about AI-fluency PM interviews. He is referenced in the same context as Ben Erez and Tal Raviv.
Programmable interfaces that let AI agents and software systems access services and complete tasks. The newsletter positions APIs as one of the means for agents to act on behalf of users.
An open-source tool that converts existing MCP tools into token-efficient skills runnable via CRI.
A tool interface used with skill.md to reduce token usage and run MCP commands in a more efficient way.
Mercury is a banking company referenced for its MCP connector, enabling Claude/Opus to access account data via OAuth.
A lightweight skills-based pattern for packaging agent capabilities in small context-efficient files.
Stay updated on MCP
Get curated AI PM insights delivered daily — covering this and 1,000+ other sources.
Subscribe Free