While many MCP servers have traditionally been developer-focused, we recognized that the technology could be highly effective in promoting the adoption of tools that are often hidden from end-user interfaces. We’re really interested to see if this side of the protocol could continue to mature.

One thing we struggled with was the inability to receive documents from the client (no client -> server resource support), thus we had to resort to file system support. (See this GitHub discussion: https://github.com/orgs/modelcontextprotocol/discussions/54#...) I’d love to know the communities thoughts on this.

It’s designed for Claude Desktop on macOS, but since it’s built on the Model Context Protocol, it’d be interesting to hear of other MCP client use cases. So feel free to reach out!

GitHub: https://github.com/PSPDFKit/nutrient-dws-mcp-server

NPM: https://www.npmjs.com/package/@nutrient-sdk/dws-mcp-server

More details + demo video: https://nutrient.io/blog/nutrient-dws-mcp-release

All thoughts, feedback, and issue reports welcome! :)