BlogMCP for help centres, in plain English

MCP for help centres, in plain English

5 min read

If you use Claude, Cursor or ChatGPT, you've probably seen "MCP" mentioned more and more. Lots of documentation and help centre tools now say they have an MCP server, including us. So what is it, and does your help centre need one?

Here's what it is in plain terms, what it's useful for with documentation, what it can't do, and how it works in Dedox.

MCP in one paragraph

MCP stands for Model Context Protocol. It's an open standard that lets an AI assistant connect to other software in a consistent way. Instead of you copying text out of a tool and pasting it into a chat, the assistant asks the tool directly: "search these articles", "create a draft", "show me last month's views". The piece of software that answers those requests is called an MCP server.

So an MCP server for documentation is a way for your AI assistant to read, and if you allow it, change your docs.

Why it matters for help centres

Without MCP, using AI with your help centre goes something like this: open the article, copy it, paste it into the chat, ask for changes, copy the answer back, paste it into the editor, fix the formatting. It works, but it's slow and easy to get wrong.

With MCP, you stay in the chat:

  • "Find every article that mentions the old pricing page."
  • "Draft a new article on resetting a password, in the same style as the login articles."
  • "Which five articles had the most views this month?"
  • "List the comments waiting for approval."

The assistant does the lookups and edits through the MCP server. You check the result.

What it's good for

These are the jobs where we think MCP is most useful for documentation.

Keeping docs in step with the product. If you write code in Cursor, you can ask it to update the help article when you change a feature, while the change is still fresh in your head.

Moving content in. Bringing articles across from another tool? An assistant can help structure them and create them in bulk.

Finding gaps. Ask the assistant to look at your analytics and suggest which articles need work.

Tidying up. Fixing categories and tags, or spotting articles that say the same thing twice. Boring jobs that take ages by hand.

Moderating comments. Review, approve or reject comments from the chat.

What it isn't

A few things worth being clear about.

  • It isn't a chatbot for your customers. MCP connects your own AI assistant to your docs. It doesn't put a chat widget on your help centre.
  • It doesn't replace checking the output. AI gets things wrong. Read anything it writes before you treat it as final.
  • It won't fix stale content. If your articles are out of date, an assistant connected through MCP will happily search out of date articles.

Is it safe?

The first thing to ask about any AI connection is what it can touch. In Dedox, you decide that per key:

  • You create an MCP key in Account Settings, under Security, and choose its permissions.
  • Permissions are separate for articles, knowledge bases, analytics, comments and search, so a key can be read only.
  • Delete permission for articles and knowledge bases is optional. Leave it off unless you need it.
  • Keys are shown once, when you create them, and are stored hashed rather than in plain text.
  • You can create separate keys for different assistants, and delete any key at any time.
  • Requests are rate limited by plan, and MCP activity is logged.

The help article on MCP permissions and security covers this in more detail. Dedox's MCP server is in beta, so we'd suggest starting with a read only key and adding write access once you're comfortable.

How to connect Claude or Cursor to Dedox

MCP is included on the Professional (£99 a month) and Enterprise plans. Once you're on one of those, setup takes a few minutes.

  1. Create a key. Go to Account Settings, then Security, and create an MCP key with the permissions you want.
  2. Add Dedox to your assistant. The server address is https://api.dedox.ai/mcp. For Claude Desktop you add it to claude_desktop_config.json, and for Cursor you add it in Cursor's MCP settings or .cursor/mcp.json. There are step by step guides for Claude Desktop and Cursor.
  3. Start with something harmless. "List my knowledge bases" or "search for articles about billing".

Rate limits are 1,000 requests an hour per key on Professional. Enterprise has no hourly limit. The MCP page has the full list of what the server can do.

Do you need one?

Probably not on day one. If you're getting your first help centre live, focus on importing your documents, checking the drafts and publishing. That's where most of the value is.

MCP starts to pay off when:

  • you already spend part of every day in Claude, Cursor or ChatGPT
  • your product changes often and the docs need to keep up
  • you have enough articles that tidying them by hand has become a chore
  • several people maintain the help centre and you want routine jobs done faster

If that sounds like you, it's worth trying.

Other ways to connect your help centre

MCP isn't the only option. Dedox also has a REST API (read only on Starter, read and write from Team) if you'd rather write your own scripts, and a Zapier integration on Professional and Enterprise to connect your help centre to other apps without code. See the API docs and the integrations page.

There's also a separate idea that often gets mixed up with MCP: llms.txt, a simple file that helps AI tools find their way around a site. We explain the difference in llms.txt for your help centre.

Get started

Start on the Free plan and build your help centre from the documents you already have. When you're ready to connect an AI assistant, MCP is there on Professional, and monthly plans come with a 14-day free trial.

Create your help centre free

Common questions

What does MCP stand for?

Model Context Protocol. It is an open standard that lets AI assistants connect to other software in a consistent way.

Which Dedox plans include MCP?

Professional and Enterprise. The MCP server is currently in beta.