Give your agents document superpowers. Publish the same tools through an OpenAPI 3.0 specification, an MCP server for Cursor and Claude Desktop, GPTs Actions, and Coze plugins — so an assistant can convert, OCR or compare a document on the user's behalf.
The MCP endpoint lets a local agent call the tools directly, which means the file handling stays on the machine that already has the document.
The Model Context Protocol is how desktop AI clients like Cursor and Claude Desktop discover and call external tools. Exposing the document tools over MCP lets an agent convert or compare files locally instead of asking you to do it by hand.
Standard requests within daily quotas require no API key and can be called directly. VIP and enterprise developers can pass an authorization token via 'Authorization: Bearer <TOKEN>' header for high concurrency and batch quotas. Exact endpoint schemas are published at /openapi.json and /mcp.
Yes — the OpenAPI spec is designed to be consumed by your backend or agent framework. For on-premise and commercial integration, see the enterprise edition.