Answer
Answers: MCP, private docs, and access
Direct answers on role-aware MCP, private documentation, .docignore, and connecting AI agents to your docs.
6 articles
6 articles in this section.
How to connect Claude to your documentation (via MCP)
Connect Claude Code, Claude Desktop, or Cursor to your documentation over MCP so the agent answers from your real docs. Here's how, with role-aware access on private docs.
AnswerIs there an MCP server for private documentation?
Most documentation MCP servers only work on public docs. Here's how to get an MCP server that works on private documentation — with per-user permissions and no leaked internal files.
AnswerDoes Mintlify's MCP work on private docs? (No — here's the fix)
Mintlify's MCP server only works on public documentation. If you need an MCP on private docs, here's why Mintlify can't and what to use instead for role-aware access to private docs.
AnswerNotion MCP doesn't work for guests — here's why and what to do
Notion's MCP server blocks guest users, so clients and contractors on guest seats can't query your workspace through their AI agent. Here's the cause, the open issue, and the workarounds.
AnswerWhat is a role-aware MCP server for documentation?
A role-aware MCP server answers an AI agent's questions from your docs while respecting each user's permissions — so a client's agent sees only what that client can see. Here's how it works and why it matters for private docs.
AnswerWhat is .docignore? Keeping internal files out of shared docs
A .docignore file tells your documentation portal and MCP server which files to never render, index, or return — like .gitignore, but for docs you share. Here's what it is and how to use it.