Integrações MCP
A starting point for connecting document workflows to MCP-aware clients.
Model Context Protocol clients that want to drive Paperlane tools on a user's behalf should treat the same capability metadata and discovery routes documented on the Developer hub as the source of truth, with a few MCP-specific expectations below.
Before invoking a tool#
Present the selected tool's capabilities, whether it runs locally or requires network access, and any required user consent before invoking it — the same information a human would see in the tool's own UI. Do not invoke a network-assisted feature without the user's explicit, informed action.
Discovery for MCP clients#
/llms.txt and /llms-full.txt are the fastest way for an MCP-aware client to enumerate available tools, their categories, and the trust routes (this page, Privacy, Security) that govern how they may be used.
/agents/webmcp.json is the static catalog for the browser integration. In a compatible browser, the live document.modelContext tools are authoritative because they reflect the current page and user-selected inputs.
/.well-known/security.txt is published for automated security tooling and follows RFC 9116; it is not a general capability-discovery route and should not be treated as one.
WebMCP and remote MCP are different surfaces#
WebMCP runs inside a compatible browser and shares the visible page, authentication state, selected local files, progress, and results with the user. It works without sending document bytes to a separate MCP server.
A desktop or server-side MCP client does not automatically gain these browser tools. Such clients need a WebMCP-capable browser integration, or a separate remote MCP server for operations that are safe and available server-side.
Local execution is not remote-callable#
A tool marked as local-only cannot be invoked as a server-side API. A WebMCP-capable browser agent can invoke it inside the user's active page after the user selects the required files; a remote MCP client without that browser context can only guide the user to the tool.
Surfacing honest refusals#
Where a tool refuses an operation instead of faking success (again, Encrypt PDF is the clearest example — see Security), an MCP client should pass that refusal message through to the end user rather than silently retrying or masking it as a generic error.