GoodBarber's MCP server now reaches your CMS — articles, events, maps, galleries, podcasts. Manage your app's content by talking to your AI assistant. One sentence, one publish.
The publishing jobs that don't need a laptop
If you publish content in a GoodBarber app, you know the pattern. A new walking trail opens in your area, and your readers will want to know before the weekend. None of the work is hard. An article with a photo and a route description. A guided-walk event on Saturday morning. Three points of interest along the way — the spring, the viewpoint, the old chapel.
But every one of those tasks means the same thing: open a laptop, log in, find the right section, fill a form, order the body blocks, save. Repeat for the event. Repeat for the map. By the time it's done, the afternoon is gone — or the idea has slipped onto a to-do list that never gets shorter.
When we introduced GoodBarber's MCP server, we closed that gap for the shop side of the platform. The response told us something we should have seen sooner: the value of acting on your app from a sentence wasn't limited to commerce. It was just as useful for everything else the back office manages. So we extended the MCP server to cover content too.
One Connection, Now Wider: Managing Shop and CMS via MCP
MCP — the open Model Context Protocol, introduced by Anthropic in late 2024 — is the bridge. It's a standard that lets an AI assistant like Claude or ChatGPT securely connect to an external service and perform real actions on it. Plug GoodBarber's MCP server into your assistant, and it gets a direct line to your app. We covered the full picture in the MCP server launch article — and before GoodBarber had its own server, we showed how to drive an app through Zapier's MCP relay, still a useful route when you want to chain GoodBarber actions with other tools.
What's new is the scope. The connection that already managed your shop now reaches every content section of your app. Nothing changes for shop users — the catalog, order, marketing, customer, and analytics tools are exactly where they were. There's just more on the other end of the same line.
The MCP server is the bridge: one connection from your AI assistant to your whole app — shop and content.
Here's the full content scope, and the kind of sentence that drives each part:
| Content Section | Capabilities | Conversational Prompt Example |
|---|---|---|
| Articles & News | Create and update articles, build block-based layouts (text, photos, quotes, embeds), rearrange paragraph order, and configure premium access with free paragraph previews. | "Create a premium article about the trail with a 2-paragraph free preview, and insert a photo block after the intro." |
| Agenda & Events | Create, reschedule, and list events on your app's calendar using date, time, and address. | "Move the guided-walk event from this Saturday at 9 AM to next Sunday at 10 AM." |
| Maps & Points of Interest | Plot geographic coordinates, add locations with physical addresses and short notes. | "Add a new map point for 'The Spring' at 12 Trailhead Rd with the note: 'Fresh drinking water station'." |
| Media Galleries | Create and populate photo galleries, upload videos, and organize audio/podcast sections. | "Create a new photo gallery called 'Trail Views' and upload the last three pictures I sent you." |
One Conversation, Multiple Updates: How App Content Automation Works
Take a real example from our own roadmap. Your app just got a new AI chatbot, and you want to announce it. Here's the back office it used to need — and the sentence it needs now.
"Create an article in the News section titled 'Meet our new AI chatbot'. Add a short intro paragraph and three text sections about: what it does, how to use it, and privacy & trust."
The assistant builds it and reports back: the article live in News, four paragraphs in place. One sentence, one finished post.
From there it stays a conversation, not a form. An article body is a sequence of blocks, and you rearrange them the same way you wrote them — by asking:
"In that article, move the intro photo above the first text section."
The assistant doesn't have free rein. Every action is scoped to your app, and sensitive operations ask for your confirmation before they run. You stay the editor. You just stop navigating.
A New Rhythm: Managing Your App in Real Time with AI
Before, content work happened in dedicated sessions. You sat down, opened the back office, and went through your list. That works for planned work. But a lot of publishing is reactive — a trail opens, an event time moves, a reader sends you a place worth adding to the map.
Now it happens when the thought does. You're already in your AI assistant. You add a line, the assistant does it, you keep working. Shop and content live in the same conversation: you can check an order and publish an article in the same breath.
Double Impact: Feeding Your App's RAG Chatbot with MCP Content
There's a second payoff. The articles, events, and map points you create this way are exactly what GoodBarber's RAG Chatbot draws on to answer your users. Publish the trail article by voice, and a hiker asking your app "is the Ridge Loop open?" gets an answer grounded in what you just said. You manage the content in one conversation; your app holds a conversation of its own with the people who read it.
Getting Started: Connecting Your App to Claude or ChatGPT
If you already use the MCP server for your shop, there's nothing to do — the content tools are part of the same connection. Just ask your assistant what content it can manage.
If you're starting fresh, setup takes about three minutes: add the MCP server URL to your AI client, sign in with OAuth using your GoodBarber account, and ask your first question. "What content can you manage on my app?" is a good one — the assistant lists everything it can reach.
What's Next for AI-Driven App Management
This is the pattern we want to keep: as your app grows, the MCP server grows with it, over the same connection you already set up. And as AI models get better at planning multi-step work, that connection gets more capable without you updating anything.
We've been building tools for app creators since 2011, with one constant — more power, less complexity. Your back office already learned to listen. Now it can write.
Connect your app today and start talking to your content.
FAQ
Can the MCP server create articles, events, and maps?
Yes. GoodBarber's MCP server exposes the full CMS — articles (with text, photo, quote and embed blocks), agenda events, map points of interest, photo galleries, videos, and audio sections — as actions an AI assistant can perform on your app.
Do I need a separate setup for content tools?
No. If you already connected the MCP server for your shop, the content tools are on the same connection. New users add the server URL to their AI client and sign in with OAuth — about three minutes.
Which AI assistants work with it?
Any client that supports the Model Context Protocol — Claude, ChatGPT, and others. You bring your own AI; GoodBarber provides the connection to your app.