How to Connect Your Wiki to Claude, ChatGPT, or Cursor with MCP

TL;DR

• MCP lets AI tools search, read, create, and update pages in Docmost programmatically.
• An admin turns it on once in Settings > AI settings > MCP, and it needs the paid edition.
• Most clients connect with OAuth: you sign in, choose read-only or read and write access, and approve.
• The AI tool acts as you, so it can only reach the spaces and pages your account can.

Docmost provides a Model Context Protocol (MCP) server that lets AI tools like Claude, ChatGPT, and Cursor connect directly to your wiki. Once they're connected, they can search, read, create, and update pages in Docmost programmatically, so you don't have to copy content back and forth between your wiki and an AI chat.

Setup takes two parts. A workspace admin turns MCP on in Settings > AI settings > MCP. After that, each person adds the server URL to their AI client, signs in to Docmost with OAuth, and chooses whether the tool can only read or can also write. The AI tool acts as you, so it can only reach the spaces and pages your account can, and also, MCP needs the paid edition of Docmost.

This guide walks through each client step by step, plus the API key option for clients that don't support OAuth.

The table below shows how each client connects to Docmost.

What Is MCP and What Does It Do in Docmost?

MCP (Model Context Protocol) is an open protocol that lets AI tools connect to other software. Docmost runs its own MCP server, so any AI client that supports remote MCP servers can connect to your workspace and work with your content directly.

Once an AI tool is connected, it can search, read, create, and update pages in Docmost programmatically. You can ask Claude to find your latest release checklist, or ask Cursor to write up the change you just shipped as a new page. The AI works from what's in your wiki right now, instead of whatever you remembered to paste into the chat.

What an AI Tool Can Do in Docmost

If you connect in read-only mode, the AI tool can only search and read content. It can't create or change anything. An API key works differently. It doesn't have a read-only option, so a tool connected with one can use every action in the table. Two things still limit it. Your admin can block API keys by turning on Enforce OAuth (covered below), and the tool can only change spaces and pages your account has permission to edit.

If you're still working out how your team finds information in the first place, see AI search vs keyword search for internal wikis.

If your team's docs are still scattered in a few different places, our guide to the best documentation tools for product teams is a good place to start before you connect anything.

MCP connects outside AI tools to your wiki. If you'd like the AI to answer questions from your docs inside Docmost itself, see how RAG works for internal documentation.

Does Docmost MCP Work If I Self-Host?

Yes. MCP works on self-hosted Docmost, using the https://YOUR_DOCMOST_URL.com/mcp server URL format, as long as you're using the paid edition.

Swap in your own Docmost address, and that's the URL you'll give each AI client.

If you haven't picked where your docs will live yet, see how self-hosted documentation tools compare.

What You Need Before You Connect Your Wiki to Claude or ChatGPT

Check that you have these in place before you start:

• The paid edition of Docmost: MCP is part of the paid edition. If you're not on it yet, talk to our sales team about the paid edition.
• An admin to switch MCP on: It's a one-time workspace setting, and the steps are below.
• An AI client that supports remote MCP servers: Claude, ChatGPT, Claude Code, and Cursor are all covered in this guide.
• A paid ChatGPT plan, if you're using ChatGPT: Custom MCP connections in ChatGPT need a paid plan and only work on the web.

You can find the full setup reference in Docmost's MCP setup guide. If your team doesn't have a wiki yet, start with how to set up a corporate wiki.

How Admins Enable MCP in Docmost

A workspace admin has to turn MCP on before anyone can use it:

1. Go to Settings > AI settings.
2. Click the MCP tab.
3. Toggle the MCP switch on.
4. Copy the MCP server URL shown on the page.

After that, any workspace member can connect their own AI tools.

How to Connect Your Wiki to Claude, ChatGPT, or Cursor with OAuth

OAuth is what most clients use to connect. You give the client your MCP server URL, and it handles the rest.

What Happens on the OAuth Authorization Screen

When you add Docmost to an AI client, the client registers itself, sends you to Docmost to sign in, and then asks you to authorize it. You don't copy any passwords or keys anywhere.

On the authorization screen, you choose what the app is allowed to do:

Both are selected by default. If you only want the AI tool to look things up, deselect "Write" before you approve. The app then connects in read-only mode and can only use the actions that read content, so it can't change anything in your wiki.

How to Connect Your Wiki to Claude (claude.ai)

1. In Claude, go to Settings > Connectors > Add custom connector.
2. Enter your MCP server URL.
3. Click Connect.
4. Authorize the connector in the Docmost window that opens.

Once that's done, you can ask Claude about anything in your wiki that your account can see.

How to Connect Your Wiki to ChatGPT

Custom MCP connections need a paid ChatGPT plan and only work on the web, so set this up in your browser:

1. Go to Settings > Security and login and turn on Developer mode.
2. Open chatgpt.com/plugins and click the + button.
3. Enter a name and a description, set the connection to your MCP server URL, and set authentication to OAuth.
4. Click Create.
5. Sign in and authorize the connection in the Docmost window that opens.

How to Connect Your Wiki to Claude Code

Run this command, with your own Docmost address in place of the placeholder:

claude mcp add Docmost --transport http https://YOUR_DOCMOST_URL.com/mcp

Then run /mcp inside Claude Code to start the login flow, and authorize Docmost in your browser when it opens.

How to Connect Your Wiki to Cursor and Other Clients

For Cursor and most other clients, add the server URL to the client's MCP configuration:

{

  "mcpServers": {

    "docmost": {

      "url": "https://YOUR_DOCMOST_URL.com/mcp"

    }

  }

}

Any client that supports remote MCP servers with OAuth will ask you to sign in the first time you use it.

How to Connect with an API Key (For Clients Without OAuth)

Some clients don't support OAuth. For those, you can connect with a personal API key, as long as your admin hasn't turned on Enforce OAuth (covered further down).

To create a key:

1. Go to Settings > API keys.
2. Click Create API Key.
3. Give the key a name you'll recognize later.
4. Choose when it expires, or pick no expiration.
5. Click Create.
6. Copy the key and store it somewhere safe. You won't be able to view it again.

The client sends the key as a Bearer token in the Authorization header. In the examples below, replace https://YOUR_DOCMOST_URL.com with your Docmost address and YOUR_API_KEY with the key you just created. The same snippets are in Docmost's MCP setup guide if you'd like to copy them from there.

Claude Desktop API Key Setup

Add this to your Claude Desktop configuration file, claude_desktop_config.json:

{

  "mcpServers": {

    "docmost": {

      "command": "npx",

      "args": [

        "-y",

        "mcp-remote",

        "https://YOUR_DOCMOST_URL.com/mcp",

        "--header",

        "Authorization: Bearer YOUR_API_KEY"

      ]

    }

  }

}

Claude Code API Key Setup

You can pass the key as a header:

Or connect through mcp-remote:

Cursor API Key Setup

Add this to your Cursor MCP configuration file, .cursor/mcp.json:

{

  "mcpServers": {

    "docmost": {

      "command": "npx",

      "args": [

        "-y",

        "mcp-remote",

        "https://YOUR_DOCMOST_URL.com/mcp",

        "--header",

        "Authorization: Bearer YOUR_API_KEY"

      ]

    }

  }

}

OAuth vs API Key for MCP: Which Should You Use?

Use OAuth whenever your client supports it. You get to choose read-only access, and you don't copy a key into a config file. Keep API keys for the clients that leave you no other option.

How Permissions Work When AI Tools Connect to Your Wiki

A connected AI tool acts as you. It can never do more than your own account can, so every space and page permission you already have still applies.

That means the AI can only search and read pages you're allowed to view. Creating or updating a page needs the same write permissions it would if you were doing it yourself in the browser, so if you can't edit a space, neither can the AI tool you've connected.

Can an AI Tool See Pages I Can't Access?

No. MCP follows the same permissions as the Docmost web app, so a connected client can only reach the spaces and pages your account has permission to view or edit.

How to Manage and Disconnect AI Apps

Every app you authorize shows up under Settings > API keys > Authorized apps. Each entry lists the permissions you granted, when you authorized it, and when it was last used, which makes it easy to spot an app you don't recognize or no longer need.

To remove an app's access, click the delete icon next to it. The change takes effect immediately, and the app has to be authorized again before it can reconnect.

To remove an API key, go to Settings > API keys, open the ... menu next to the key, and choose Revoke. Admins can see and remove every key in the workspace from Settings > API management.

A few other rules apply to connections:

• Access tokens are short-lived and renew automatically while the app keeps using them.
• An app that goes unused for 30 days has to be authorized again.
• Resetting your Docmost password removes access for every app you've authorized.

How Admins Can Require OAuth for Every MCP Client

1. Go to Settings > AI settings > MCP.
2. Turn on Enforce OAuth.

With this on, the MCP server rejects API keys. Clients that support OAuth go through the sign-in flow instead, and any client set up with an API key stops working until it's reconnected through OAuth.

Frequently Asked Questions

1. What Is MCP and What Can It Do with a Wiki?

MCP (Model Context Protocol) is an open protocol that lets AI tools connect to other software. With Docmost, a connected AI tool can search, read, create, and update pages programmatically.

2. Can I Connect Claude or ChatGPT to My Wiki?

Yes. With Docmost, you add your MCP server URL to Claude as a custom connector, or to ChatGPT as a custom MCP plugin, then sign in to Docmost and authorize the connection. ChatGPT needs a paid plan and works on the web only.

3. Can an AI Tool Edit My Wiki Pages?

Yes, if you leave "Write" selected on the authorization screen. If you deselect "Write," the tool can only search and read content.

4. Can AI Tools See Wiki Pages I Don't Have Access To?

No. The AI tool acts as you, so your space and page permissions apply to everything it searches, reads, or edits.

5. Can I Connect a Self-Hosted Wiki to Claude or ChatGPT?

With Docmost, yes. MCP works on self-hosted Docmost, using the https://YOUR_DOCMOST_URL.com/mcp server URL format, as long as you're using the paid edition.

6. How Do I Disconnect an AI Tool from My Wiki?

Go to Settings > API keys > Authorized apps and click the delete icon next to the app. It loses access immediately. If the tool connects with an API key instead, open the ... menu next to the key under Settings > API keys and choose Revoke.

7. Do I Need a Paid Plan to Connect My Wiki to AI Tools?

With Docmost, yes. MCP is part of the paid edition, and a workspace admin has to turn it on before anyone can connect.

Connect Your Wiki to AI Tools with Docmost

MCP comes with the paid edition of Docmost, and switching it on is a single toggle for your admin. Once it's on, everyone on your team can connect their own MCP-compatible AI tools, with the same access they have today. 

If you're still comparing options, see how team wikis with AI features compare. Contact our sales team to talk through your setup.