The Vellum 4.2 Backlash: Or Why MCP is not AI
Full disclosure: I’ve used lots of apps. Vellum is a book formatting app I’ve used for more than a decade, probably since they began (too lazy to check). I’ve been impressed by this small team of three people and what they’ve been able to offer my business. However, as a member of the writing community, I seek to understand what put this group under intense fire and why. I’m also the child of a computer scientist and I sometimes read the magazine Communications of the ACM for leisure, which may explain why it’ll take me two posts to get through this topic, but I am no expert.
The story
On November 4, I got an announcement from Vellum that they were introducing automation in their update 4.2. This was going to allow people to use their digital assistant to interact with the Vellum app. I didn’t know too much about it, so I just bookmarked it, expecting to get to it later, because I have a very busy schedule and I thought I’d get to it maybe in a couple days or so.
I was wrong.
The Very Next Day, the update was gone. I then received a notice from Vellum that they had removed the 4.2 update due to a backlash from the indie author community. I want to talk about this because I don’t understand the backlash. The automation, which was part of the update, was optional. It included a Model Context Protocol (MCP), which from my understanding, allows people to connect their app to a digital assistant and did not mean people had to use it. It was optional.
Why the outrage?
To me, it’s like going into the store and you have the option of using cash or a credit card. You’re not being forced to use a credit card if you want to use cash or vice versa.
MCPs are already being used in academic publishing, magazines and media and one week after Vellum removed its MCP connection, Adobe announced local MCP integrations for Photoshop, Illustrator, Premiere, and After Effects. (It’ll be in private beta in early 2027.)
Again why the outrage?
Did I miss something? Did Vellum add AI to its app? Is it forcing people to use digital assistants in order for their app to work? When I work in the app will a generative AI feature prompt pop up? Is this company in collusion with AI companies and signed a deal that will allow authors work to train AI?
No, no, no, and absolutely no.
Vellum didn’t add AI. It added an MCP, which isn’t AI.
It’s simply a connector that allows an author’s digital assistant (if they have one) to instruct it to do a task. For example: I need to change the type font in fourteen books, and I don’t want to have to spend the time doing that myself. You can, if you so choose, prompt your digital assistant to do it for you, using the MCP.
Now, yes, there are those writers who can hire human assistants. They have the income to be able to hire a person to do this repetitive, soulless task.
However, I doubt numerous virtual assistants (VAs) or contractors are losing their jobs because someone is using a machine to do repetitively boring tasks. There are some VAs who still have waiting lists.
So, it couldn’t be that these writers are upset over loss of work for VAs.
There had to be another reason for this backlash.
I was seriously confused. These are the same people who don’t bat an eyelash knowing people pay others to ghostwrite series of novels under their names and they’re going to freak out when a machine is directed (by a human) to change the back matter of a series of books?
Have I mentioned I think writers are crazy? (If you don’t get the reference, ignore it)
I mean there are people who want to (and are able to) take the stairs and those who prefer to use the elevator. Wasn’t it as simple as that? Preference. The Vellum update was meant for the authors/designers who are already using digital assistants. For those not using digital assistants, this update would not change anything about their workflow, their business, or Vellum itself.
It seemed clear to me, but it wasn’t to others. What I read (or rather skimmed, since reading in depth either made me shiver or laugh) from other writers made me see I was still missing the big picture. I wasn’t landing on the right analogy.
That’s when I realized what happened with Vellum was an emotional response rather than logical one, because when writers confuse repetitive, boring tasks you can hand out to a twelve year old, with true, professional creativity, then we’ve lost the plot.
Let me repeat this. The people at Vellum did not build AI into Vellum. They just provided a way for those who wanted to use a digital assistant to connect to Vellum.
However, the writers who objected weren’t completely mad (or daft). I didn’t want to completely dismiss them. I was still confused and when I don’t understand something I have to break it down, which is what I’m going to do over these two posts.
First, I’ll address what an MCP is, then I’ll address authors’ concerns (both real and imagined) and what we can conclude.
So let’s start with the basics.
What is MCP?
Picture the front desk at a hotel. The average guest, if they need something, doesn’t walk straight into the kitchen or the laundry room, right? Otherwise, there’d be chaos. No, like any civilized person they go to the front desk and ask for what they need that’s on the list: extra towels, a late checkout, an escort—I mean a taxi. The hotel gets to decide what’s on that list.
Model Context Protocol (MCP) is the design given to the front desk, the tool that connects. It lets a guest (an outside AI assistant) ask the hotel front desk (a piece of software) to do things. The front desk (the software) decides which requests it will accept. Nothing happens unless you set it up and invite the assistant in. Notice the word protocol.
I got this from the Merriam-Webster dictionary:
Protocol is a system of rules that explain the correct condut and procedures to be followed in formal situations.
What does that mean?
It means MCPs are not the following:
It is not AI. It’s merely a connector. It doesn’t write, think or generate anything. Think of it like a plug socket (or outlet). You can plug into it or not.
It does not put AI inside the app. The digital assistant stays outside and can only use the ‘front desk’ the app chooses to offer. Again, refer to the plug socket concept.
It’s really nothing new. Software has always talked to other software through connectors like APIs.
What are APIs? Glad you asked.
Well, it stands for Application Programming Interface, which meant nothing to me when I first saw this term years ago. The way I was able to understand it was like this—that it’s an agreed way for one program to make requests to another.
Let’s try another visual, shall we? Instead of a front desk let’s think of a restaurant.
You’re a hungry customer (one piece of software) and the kitchen is the other software, this is where the actual work happens (behind the scenes just like in real life). The menu lists what you’re allowed to order. If it’s not on the menu you can’t order it. The waiter is the API. They use the menu to take your order to the kitchen and moments later they bring back what you asked for.
The customer (you) never go into the kitchen and you don’t need to know how the food is made. Following certain protocols the kitchen never has to let strangers in. Everyone follows the menu and talks to the waiter.
Authors use APIs all the time, probably without noticing. Change a book’s details on your publishing dashboard and then see the changes show up on a retailer’s website? That’s an API (waiter) carrying your order to the kitchen. Same with ‘Sign in with Google/Apple/Facebook’
Companies design their own APIs, like restaurants create their own menus, language and way of ordering things.
So, back to MCP. An API is the waiter that refers to the menu (the documentation that lists the available requests) and takes the customer’s ‘request to the kitchen, while an MCP is a universal plug socket (outlet) that lets any digital assistant reach that waiter the same way.
For example, when you travel internationally, you’ll notice different countries have different socket shapes. But an MCP connection offers one standard socket shape for digital assistants.
Like a wall socket it does nothing until someone plugs something into it.
And that’s one of the reasons why MCP is not AI. Hope that clarifies some confusion.
In my next post I’ll address the fears and the myths that circulated about this recent Vellum update.
The Vellum 4.2 Backlash: Or Why MCP is not AI © 2026 Dara Girard
hotel front desk image © naobim/pixabay
