Feature Request

Description: Developers increasingly build and integrate with APIs using AI tools such as Cursor, Claude, Claude Code, and ChatGPT. The MCP is becoming the standard way for these tools to connect to external knowledge sources. It lets developers explore endpoints, review request and response schemas, and make live API calls directly from their development environment. MCP server support for API documentation projects would let AI tools and agents work with the complete API reference from within a developer’s own workflow. Proposed Capabilities Support for listing, searching, and retrieving endpoint details, including parameters, schemas, examples, and authentication requirements. Administrative controls to choose which endpoints are exposed and to enable or disable live API execution. Optional execution of live API calls using the end user’s own credentials. Benefits Faster API exploration and integration for developers, directly from the tools they already use. Accurate, up-to-date API context for AI agents and assistants. A seamless experience between API documentation and AI-assisted development.

The Document360 MCP should be expanded to support managing broken links and redirects. This is particularly important now because the link validator reports many external links as broken when they do not respond within the 5-second timeout. As a result, we have to manually review and ignore a large number of working links before we can identify the links that actually need attention. The MCP should allow us to retrieve validation results, review and ignore incorrectly flagged links, identify where broken links are used, and update or replace them. It should also support retrieving, creating, updating, and deleting redirects. Having these capabilities in the MCP would make it much easier to manage large validation reports and handle broken links and redirects without spending hours reviewing and updating them manually in Document360.

Please enable users to upload an entire folder from their device to Document360 Drive while preserving the existing folder structure, including all subfolders and files. This will reduce the duplicate efforts to sort the files again in the Drive.

Currently, the Pre-publish check displays a warning if a broken link is detected (though it is often wrong), but does not display what link it is detecting as broken. This makes the warning a liability and a time-sink, as you have to check every link on the page to verify that they are still working and often discover that there is no issue with any link on the page. The Pre-publish check should list the link that it is referencing as "broken" and give us the option to ignore the warning so it does not appear again.

To have PDF download analytics for the end-user site to track who is downloading PDFs (where user identification is available), which articles or PDFs are downloaded most frequently, the number of downloads, and download trends over time. This would help us understand content engagement and identify popular resources.

Provide an option to configure the maximum number of PDFs that can be generated within a single reader session. Once the configured limit is reached, further PDF export requests from that session should be restricted. This would help prevent excessive PDF generation within a single session, particularly through automated requests, and reduce the risk of rapidly exhausting the monthly PDF export credits.

Provide an option to allow PDF exports only for signed-in readers. When enabled, readers who are not authenticated should not be able to export PDFs from the knowledge base. This would help prevent anonymous visitors from exporting PDFs and consuming the available monthly PDF export credits without signing in when the project is mixed.

Provide a way to track PDF export activity and identify the readers performing exports wherever reader identification is available. This should help admins/owners understand who is exporting PDFs, monitor export activity, and investigate unexpected consumption of monthly PDF export credits.

I use the "compare with" feature often because I'm trying to see what content was newly added and published by other users. So my workflow is this: I open up "Version History". This opens up the most recently published, newest version of the article (V2). I want to compare the newest version, V2, to the older version, V1, because I want to see what was added to the new article. I press "Compare with" and then "V1". Doc360 shows me content that was added and removed. But I have to double-take, because it's currently set to highlight the new V2 text as "removed" text, which doesn't make sense. It's backwards to what I would anticipate as an end-user, especially considering the above workflow. If I'm starting in v2 of the article, and comparing to an older version, then I would think added content (from v1 to v2) would show as added. You can see the issue in the attached screenshots. V1 has one sentence, and v2 has two sentences, the second one having been added to the newly published version. But when comparing V2 to V1, the added line is listed as having been removed from the article as if I had been viewing v1 to begin with and wanted to compare it to v2. I hope I've explained this in an understandable way. Thanks for reading!

Feature description: The customer would like an API endpoint that allows them to replace an existing file in Document360 Drive without having to upload it as a new file or manually replace it through the UI. Use case: The customer wants to programmatically update existing files in Drive, making it easier to maintain files and their content through API integrations and automated workflows. Expected behavior: Provide an API endpoint to replace an existing file in Drive. Allow users to identify the existing file and upload its replacement through the API. Preserve the existing file reference, where technically feasible, to avoid having to update links or references wherever the file is used. Customer impact: This would improve automation capabilities, reduce manual effort, and simplify file maintenance for customers managing Drive content programmatically.