Hacking Strapi by Cultivating the Stream: Why We Build the Tools We Need

# **Hacking Strapi by Cultivating the Stream: Why We Build the Tools We Need** ## **Directing your own stream** For enabling an agent to create blog posts directly in Strapi without the GUI, try this sidecar approach. It takes about five minutes to plumb the connection: 1. **Tap the Reservoir**: Install the foundational community server to give your agent "X-ray vision" into Strapi23. \`claude mcp add \--scope user strapi-community \-- npx \-y @anthropic/strapi-mcp-server 24\` 2. **Direct the Stream**: Install our specialized layer for directed workflows. \`claude mcp add \--scope user ainative-strapi-new \-- npx \-y ainative-strapi-mcp-server 26\` In practice, the difference is distinct. Instead of asking the agent to "construct a complex JSON object," you can simply say: "Create a blog post titled 'Getting Started' with this markdown". The agent calls one function, the post appears, and the friction disappears. Here's the story of why we took this approach instead of hacking directly on the Strapi MCP server. ## **Navigating business needs and good citizenship** If you look at the architecture of a healthy open source ecosystem, it usually resembles a watershed. You have massive reservoirs of raw capability—the upstream projects—and the specific, directed streams that bring that value to the fields. Recently, at AINative Studio, we faced a classic hydrology problem while building our own AI-native content workflow. We wanted our agents to manage our Strapi-powered community platform—writing posts, publishing tutorials, and shepherding events. We found that the official @anthropic/strapi-mcp-server is an excellent reservoir to draw from—it provides raw primitives like listing content types and basic CRUD. But when we tried to use it for our specific "garden" of markdown blogs, we found the friction was in the flow. To write a single post, our agent had to navigate a complex sequence of API calls. It was like trying to water a single plant with a firehose—effective at getting everything wet but messy and prone to eroding the soil. ### **The Catalyst Moment: Building the Builder** Here is the part I find most compelling (and frankly, a bit recursive): When we hit these limitations, we didn't spend weeks in a boardroom. We asked the agent to build the solution that the agent needed. We analyzed the architecture, defined the TypeScript interfaces, and published ainative-strapi-mcp-server to npm in about 53 minutes. The tool built the tool. It serves as a reminder that in this era, we aren't just coders; we are catalysts. We identify the friction in our own daily work, use the intelligence at our fingertips to smooth the path, and then realize that the bridge we built for ourselves might help others cross the same river. ### **Principles and Practices: Enhance, Don't Fragment** In wanting to develop features not already found in an upstream project, we faced a choice every open source developer eventually faces: Do we fork the upstream project to change it to our will (and possibly end up on an island of our own making), or do we build a bridge? At AINative Studio, we operate under the axiomatic belief that openness is the default state. Forking the official server might have solved our immediate problem, but it would have severed us from the virtuous water cycle of future upstream updates. Instead, we chose a side-by-side approach: * **Principle**: Maintain upstream compatibility and ecosystem health.. * **Practice**: Run two complementary MCP servers together. We kept the upstream server for its raw power (the "how") and layered our specialized server—ainative-strapi-new—to handle the specific workflows (the "why"). This allows us to have both our pure water source and custom drinking flow too. ### **Tending the garden** This architecture—layering specialized workflows over generic capabilities—respects the upstream work while acknowledging that sometimes, you just need a simple button to press. We are all just figuring out the best way to tend this garden together.

Hacking Strapi by Cultivating the Stream: Why We Build the Tools We Need

Check your site's AX Score