MCP Everywhere  ## Metadata - Author: [[Matt]] - Full Title: MCP Everywhere - Category: #articles - Document Note: --- tags: - #MCP - #WordPress - #AIintegration Author: Matt Source: Personal blog Reference: https://ma.tt/2025/09/mcp-everywhere/ date created: 2025-09-20 00:00 --- # Title: MCP Everywhere ## Table of Contents: - [🧭 Overview](#🧭-overview) - [🧩 Implementations across the Automattic ecosystem](#🧩-implementations-across-the-automattic-ecosystem) - [🔌 Why interoperability matters](#🔌-why-interoperability-matters) - [🛠️ Setup/Usage highlights](#🛠️-setupusage-highlights) - [🗒️ Notes](#🗒️-notes) - [📖 References](#📖-references) - [🗣️ Paraphrase](#🗣️-paraphrase) - [📰 Newsletter](#📰-newsletter) - [✅ Action Items](#✅-action-items) - [🧪 Hypotheses](#🧪-hypotheses) - [📊 Methodology](#📊-methodology) - [❓ Questions](#❓-questions) - [🔮 Future Research](#🔮-future-research) - [💡 Implications](#💡-implications) - [🧠 Learning Styles Assessment](#🧠-learning-styles-assessment) - [📊 Accessibility Assessment](#📊-accessibility-assessment) - [🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment](#🌍-deib-diversity-equity-inclusion-and-belonging-assessment) - [✅ Logical validity](#✅-logical-validity) - [🎯 Conclusion](#🎯-conclusion) ### References: - Model Context Protocol (general concept; “USB‑C for AI” analogy) - WordPress Abilities API + MCP Adapter - Woo 10.3 MCP - Clay’s MCP setup - Beeper’s MCP for unified messaging - Day One community MCP (Kevin Davinson) ## 📝 Summary: The post introduces MCP (Model Context Protocol) as a universal interface—“like a USB‑C port for AI applications”—enabling AI systems to interoperate with tools and data sources. It highlights early MCP integrations across the Automattic ecosystem: a WordPress MCP Adapter using a new Abilities API, WooCommerce MCP in 10.3, Clay’s MCP for contact queries, Beeper’s MCP to query multi‑network message history, and a community-built Day One MCP. The author is optimistic about emergent workflows as “nerds start connecting things,” while noting these aren’t yet daily drivers. ## 📖 Main Content: MCP provides a standardized way for AI agents to perform actions and retrieve context from diverse apps. Within the Automattic sphere, WordPress gains an MCP Adapter leveraging an Abilities API to perform CRUD and other operations; WooCommerce is adopting MCP in v10.3; and adjacent tools like Clay, Beeper, and Day One showcase broader reach—contacts intelligence, unified messaging queries, and journaling interfaces. The post frames MCP as plumbing for AI-era interoperability that invites experimentation and new workflows. ### 🗒️ Notes - Definition and analogy - MCP = Model Context Protocol; think universal port for AI integrations. - Emphasis on interoperability and standard actions. - WordPress - MCP Adapter integrates via an Abilities API. - Enables CRUD and beyond across WordPress resources. - WooCommerce - Core MCP slated for 10.3 (early October). - Early community work by Lawrence Sinclair on GitHub. - Clay - Example query: “Who are my contacts at Google I haven’t spoken to in 6 months?” - Demonstrates CRM-like retrieval via AI. - Beeper - MCP allows natural-language querying across iMessage (macOS), WhatsApp, Telegram, Signal, Instagram, etc. - Unified message search/history via AI. - Day One - Community MCP by Kevin Davinson. - Journal data accessible via standardized AI interface. - Author stance - Curious and bullish on emergent use cases. - Not yet a daily workflow, signaling early stage. ## 📖 References: - WordPress MCP Adapter with Abilities API (official Core announcement when available) - WooCommerce 10.3 release notes (forthcoming) - Lawrence Sinclair’s GitHub prototype - Clay’s MCP setup guide - Beeper’s MCP documentation - Day One community MCP by Kevin Davinson ## 🗣️ Paraphrase: - Original idea: “MCP stands for Model Context Protocol… think of it like a USB‑C port for AI applications…” - Paraphrase: Model Context Protocol acts as a universal connector for AI tools, similar to how USB‑C standardizes hardware connections. - Original idea: “When nerds start connecting things, interesting stuff happens… none of these have made it into a critical daily workflow for me…” - Paraphrase: As tinkerers link systems together, novel outcomes emerge; although promising, these integrations haven’t yet become indispensable in the author’s routine. ## 📰 Newsletter: AI is getting a USB‑C. MCP (Model Context Protocol) is rapidly landing across our ecosystem: WordPress now sports an MCP Adapter powered by a new Abilities API for smooth CRUD and more; WooCommerce’s MCP arrives in 10.3; Clay enables queries like “Which Google contacts haven’t I pinged in 6 months?”; Beeper lets you search iMessage, WhatsApp, Telegram, Signal, and Instagram with natural language; and there’s a community-built Day One MCP. If you’re learning web dev, this is your moment to blend PHP/JS chops with AI interfaces: build Abilities in WordPress, wire MCP to your data, and ship automations your future self will thank you for. Community shoutouts to early contributors pushing prototypes to GitHub and documenting setups. New plugin ideas? MCP-powered editorial workflows, commerce ops assistants, and unified inbox search. Start here: WordPress Abilities API, Woo 10.3 notes, Clay/Beeper setup guides, and Day One’s community MCP. The future’s interoperable—and a little mischievous. ## ✅ Action Items: Prompt for aligning articles with your role and OSPO goals: “Analyze how this article’s AI interoperability (MCP) advances open-source advocacy, contributor onboarding, and education within WordPress and adjacent communities. Map: - Open-source leverage: Which standards, repos, and licenses are involved? How can contributions be modular (Abilities, adapters)? - Contributor engagement: Identify beginner-friendly issues, docs gaps, mentorship paths, and community recognition. - Education: Outline curriculum modules (PHP/JS + Abilities API, MCP security, data ethics), workshop labs, and assessment rubrics. - OSPO alignment: Define governance, compliance, security, and sustainability needs (usage telemetry with privacy, funding models, contribution policies). - Transparency & inclusivity: Propose DEIB-conscious documentation, multilingual guides, and accessible tutorials. - Ecosystem impact: Sketch pilots for WordPress core, Woo, and integrations like Clay/Beeper/Day One; establish metrics (adoption, PR velocity, time-to-first-contribution). Conclude with a roadmap (90/180/365 days) to operationalize MCP in the WordPress ecosystem.” ## 🧪 Hypotheses: - Standardized AI interfaces (MCP) reduce integration cost and increase plugin adoption in WordPress/Woo ecosystems. - MCP-backed editorial assistants improve content team throughput without degrading quality. - Cross-network message querying via MCP shortens support response times in commerce sites. - Community-built MCP modules accelerate innovation more than vendor-only efforts. ### 📊 Methodology: - Quasi-experimental rollout: A/B test MCP-enabled vs. non-enabled workflows in editorial and commerce ops; measure throughput, error rates, and satisfaction. - Repository analytics: Track PRs, issues, and time-to-first-PR across MCP-related projects. - User studies: Task-based evaluations of MCP features; SUS and NASA-TLX scores. - Telemetry (privacy-preserving): Feature usage, latency, success/failure rates. - Data sources: GitHub, WordPress.org plugin stats, Woo telemetry, user interviews, support tickets. ### ❓ Questions: - Which WordPress Abilities are most valuable to standardize first? - How should permissions/scopes be modeled for safe CRUD via AI? - What governance ensures MCP modules remain interoperable across vendors? - How do we prevent data leakage when querying cross-network messages? ### 🔮 Future Research: - Security models and least-privilege patterns for MCP Abilities. - Schema standards for content, commerce, and messaging domains. - Offline/edge-compatible MCP adapters for performance and privacy. - Developer experience tooling: validators, simulators, and test harnesses. ### 💡 Implications: - Stronger interoperability could catalyze a new plugin wave centered on AI agents. - Clear governance and security patterns will influence ent - Summary: MCP stands for Model Context Protocol. (The joke is the S in MCP stands for security, but that’s another post.) They say to think of it like “like a USB-C port for AI applications&#8221… - URL: https://ma.tt/2025/09/mcp-everywhere/ MCP stands for [Model Context Protocol](https://modelcontextprotocol.io/). (The joke is the S in MCP stands for security, but that’s another post.) They say to think of it like “like a USB-C port for AI applications” because it allows interoperability between AI chatbots and other tools. Here’s some of the MCP stuff happening across the [Automattic](https://automattic.com/) solar system: * Core WordPress now has [an MCP Adapter](https://github.com/WordPress/mcp-adapter/) that uses a new [Abilities API](https://make.wordpress.org/ai/2025/07/17/abilities-api/) to do [CRUD](https://en.wikipedia.org/wiki/Create,_read,_update_and_delete) and more operations across WordPress. * Woo’s core MCP is coming in version 10.3 in early October, though [Lawrence Sinclair already spun one up on Github](https://github.com/techspawn/woocommerce-mcp-server). * [Here’s how to set up Clay’s MCP](https://library.clay.earth/hc/en-us/articles/36405339564315-Clay-MCP-live-Make-integration-improved-Library-and-more) so your AI can ask things like “Who are my contacts at Google that I haven’t spoken to in 6 months?” * [Beeper’s MCP implementation](https://www.beeper.com/desktop-api) lets you query your entire message history across iMessage (on MacOS), WhatsApp, Telegram, Signal, Instagram, and many more with natural language. * Day One has a [community MCP implementation from Kevin Davinson](https://github.com/Quevin/mcp-dayone/). When nerds start connecting things, interesting stuff happens; that’s been my entire career, so while none of these have made it into a critical daily workflow for me, I’m curious to see what people come up with. [](https://ma.tt/2025/08/mcp-nyc-hackathon/), MCP Everywhere, Matt, 01k5je8v69ga6maq86fbfky2kr.