News and tips

What do we write about on the blog?

We write about the parts of running MCP that the docs don’t explain in story form. The docs tell you which variable goes where. The articles here explain why the setup works the way it does, what a typical day with Claude connected to your store or inbox looks like, and which trade-offs we made when we built mcp-core.

Every article sticks to what the software does today. When something changes in MCP Self-hosted or the shop, we update the article instead of leaving an outdated version online. New to the protocol itself? Start with What is MCP, then come back here.

Which articles should you read first?

That depends on where you are. Three articles cover the questions we get most:

• Claude WooCommerce integration walks through daily store work with Claude: finding orders, answering customer questions, checking stock, and where read-only access stops.
• MCP licensing explained covers why MCP Self-hosted uses a yearly license with entitlements instead of usage-based fees, and what happens when an add-on lapses.
• MCP server with Docker looks inside the generated compose file and explains why you only ever run ./mcp-update.sh.

Evaluating MCP Self-hosted for a team or a client? Read them in reverse order. The Docker article shows what you will run and maintain, the licensing article shows what it costs over a year and what happens when a payment fails, and the WooCommerce article shows what the result looks like in practice. Together they answer most questions we get before a first purchase, in about fifteen minutes of reading.

How does the blog relate to the documentation?

The blog explains, the documentation instructs. An article on this MCP blog gives context and examples; it links to the matching doc for the exact steps. If you want to install MCP Self-hosted right now, skip the articles and follow Install MCP Self-hosted. If you want to know whether self-hosting suits your team at all, an article is the better starting point.

The documentation has two parts: the MCP docs for MCP Self-hosted and its tool add-ons, and the plugin docs for AddoBase and the WordPress add-ons. Both are public, so you can read everything before you buy.

Who writes these articles?

The people who build MCP Self-hosted and run this shop. That means the articles come from the code and from support questions, not from a content calendar. When a customer asks the same question twice, it usually turns into a doc; when the answer needs more background, it turns into an article here.

What topics are coming to the blog?

We publish when there is something worth explaining, not on a fixed schedule. Topics follow the product: new tool add-ons such as Lightspeed eCom, changes to how seats and tool modes work, and patterns we see in how teams use Claude with their own data. Agencies running MCP Self-hosted for several clients are a recurring theme, because their setups show the edges of the model fastest.

Have a topic you want covered, or a question an article didn’t answer? Send it through the contact form. Questions with a short answer often end up in the FAQ instead.

Where do you go after reading?

If an article convinced you, the next step is small. Look at MCP Self-hosted to see what the server includes and what it costs, pick the tool add-ons that match your systems in the shop, and follow the install guide. Prefer not to run Docker yourself? The MCP Hosted seat gives you the same tools on a server we run.

Either way, the MCP blog stays here for the background: why a tool behaves the way it does, and how other teams put it to work.