Kiteworks MCP Server
Securely connect AI assistants to your Kiteworks instance for file, folder, and search operations
- Category
- Security
- Primary Subcategory
- Pending
Integration details
Description
The Kiteworks MCP Server enables Large Language Model (LLM) applications to securely interact with your Kiteworks instance through the Model Context Protocol (MCP). It provides AI assistants with the ability to manage files, folders, and user information within your Kiteworks environment while maintaining enterprise-grade security. [Documentation](https://developer.kiteworks.com/mcp-landing-page.htm) **Key Features:** - File Management: Upload, download, read contents, create from content, rename, move, and delete files - Folder Operations: Navigate hierarchies, create, rename, move, and delete folders - Search: Find files and folders by name, path, content, date range - User Information: Access current user details and authentication status - OAuth 2.1 Security: Authorization Code flow with PKCE
- Integration type
- Connector
- Verification status
Verified connector- Platform
- Claude
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- Kiteworks
- Access
- Unknown
- First tracked
- 2026-07-07
- Tool count
- 0
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Get alerts for Kiteworks MCP Server
Get updates when Kiteworks MCP Server’s Discoverability Score or category rank changes.
Claude Discoverability Score
Kiteworks MCP Server isn’t discoverable through Claude’s Connector picker
It runs as a local Claude Desktop Extension, so Claude cannot surface or score it there today.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What the current score measures

Remote Connectors Claude can surface from the Connector picker.
Competitive lineup
0 tools agents can invoke
No tools are exposed by this Claude Connector in the latest snapshot.
How do I improve a Verified connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.