Now that you have connected the Document360 MCP server with your AI assistants, let's explore how the AI assistants can use MCP tools to search, retrieve, create, update, manage workflows, and publish content in your knowledge base.
These tools work together through prompts, making it possible to perform multi-step documentation tasks with a single instruction. For example, an AI assistant can search for existing articles, retrieve category details, create new documentation, update existing content, move content through workflow stages, and publish it to your knowledge base site, all based on your project structure and permissions. Understanding how these tools work helps you create more effective prompts and build efficient documentation workflows.
MCP tools
Search and retrieval tools
| Tool | What it does | Use this to |
|---|---|---|
document360-mcp-search |
Performs a semantic search across your knowledge base project. Searches all project versions by default, or a specific version when you need it. | Find relevant documentation, discover related articles, search across versions |
document360-mcp-get-article |
Retrieves the full content of any article using its ID or URL. Works across multiple languages and lets you access both published and draft versions. | Read existing articles, review draft content, fetch articles before updating |
document360-mcp-get-categories |
Retrieves the complete category structure for a selected project version, including child categories and associated articles. | Browse the knowledge base hierarchy, find category IDs, understand documentation structure |
document360-mcp-get-category |
Retrieves everything about a specific category — its content, subcategories, and associated articles using the category ID. | Inspect one category deeply, read category page content, validate category before updates |
document360-mcp-get-project-versions |
Lists all available versions of your project along with their identifiers, so you can run version-specific operations with precision. | Select the correct version, create version-aware prompts, retrieve valid version IDs |
document360-mcp-get-workflow-statuses |
Lists the workflow statuses configured for the project, along with their identifiers and flags. | Discover available workflow statuses, retrieve status IDs before moving content through review stages |
document360-mcp-get-workflow-assignees |
Lists the users and groups that can be assigned to a specific document's workflow. | Find valid assignee IDs before assigning a workflow step, identify who can review a document |
Write tools
| Tool | What it does | Use this to |
|---|---|---|
document360-mcp-create-article |
Creates a new article inside a specified category and project version by supporting structured content. | Create new documentation in the right category, draft missing help articles, generate first drafts from prompts |
document360-mcp-update-article |
Updates an existing article while preserving its structure and formatting. Built for partial updates so you can revise a section without touching the rest of the article. | Update outdated documentation, revise articles during product updates, rewrite specific sections without affecting the rest |
document360-mcp-create-category |
Creates a new category within a selected project version. Supports nested structures so you can build subcategories as your content grows. | Add new documentation sections, create subcategories for new features, organize content into new structures |
document360-mcp-update-category |
Updates category properties such as name, position, hierarchy, or visibility. | Rename categories, reorganize hierarchy, improve structure |
document360-mcp-update-category-content |
Updates the content of category pages while preserving the existing structure. | Update Page or Index category content, revise category overview or introductory sections, refresh category-level guidance without affecting the rest of the structure |
document360-mcp-set-workflow-status |
Sets the workflow status of an article or Page category, with an optional due date, comment, and assignees. | Move content through review stages, assign reviewers, set due dates for workflow tasks |
document360-mcp-publish-article |
Publishes an article by promoting its latest draft to the live version. | Make a draft article live on the knowledge base site after creating or updating it |
document360-mcp-unpublish-article |
Unpublishes an article and removes it from the live knowledge base site. Content is preserved and can be republished. | Take an outdated or incorrect article offline without deleting it |
document360-mcp-publish-category |
Publishes a Page category's latest draft content to the live version. | Make a Page category live after updating its content |
document360-mcp-unpublish-category |
Unpublishes a Page category and removes it from the live knowledge base site. Content is preserved and can be republished. | Remove a Page category from the live knowledge base site without deleting it |
Rate limits
MCP requests are subject to rate limits based on your Document360 plan. These limits apply per user across all MCP tool calls.
These limits help ensure reliable performance and fair usage across documentation workflows.
If the rate limit is exceeded, requests may be throttled until the next time window resets.
This can happen when:
- Running frequent automated prompts
- Performing repeated searches in quick succession
- Executing multiple create or update operations at the same time
Best practices for managing MCP request limits
To avoid throttling:
- Space out frequent or automated requests
- Break large workflows into smaller prompt sequences
- Reuse retrieved category or article context when possible
- Avoid repeated parallel searches across multiple versions
This helps maintain a smoother MCP experience and reduces the chance of interrupted workflows.