QVeris MCP Gateway for Dify

QVeris MCP Gateway is a Dify Extension plugin that exposes six QVeris operations through a Dify-hosted Streamable HTTP MCP endpoint. Install the plugin, create an endpoint, and connect any compatible MCP client to the generated Dify URL.

This gateway is for teams that want a workspace-owned Dify endpoint. If you only need direct QVeris access, use the hosted endpoint at .

Chinese documentation

Available tools

Use the safe sequence . Show the selected capability's pricing information before calling it, then use or for final settlement details.

Requirements

• Dify 1.3.0 or later
• A QVeris API key from QVeris API Keys
• A strong, user-generated endpoint bearer token
• Outbound HTTPS access to

Configure the extension

1. Install the in Dify.
2. Create a QVeris MCP Gateway endpoint.
3. Enter the QVeris API key. The gateway sends it only to in the header.
4. Create and enter a strong endpoint bearer token. This is separate from the QVeris API key.
5. Copy the generated endpoint URL ending in .

Example MCP client configuration:

The server negotiates MCP protocol versions , , and . It supports , , , , and . Session termination is available through with . SSE is not supported; clients must use Streamable HTTP POST.

Security and network behavior

• The endpoint bearer token protects the Dify-generated URL.
• The QVeris API key is never returned to MCP clients or written to application logs.
• Outbound requests use a fixed base URL, reject redirects, time out quickly, and cap responses at 2 MiB.
• The plugin does not execute local commands or access Dify host files.
• QVeris capabilities can process financial, medical, location, personal, or other sensitive inputs depending on the selected tool. Review the tool schema and provider before calling it.
• Some calls are billable. Probe and surface the quote before a paid call.

See PRIVACY.md and QVeris Privacy.

Local development

Python 3.12 is required.

On macOS or Linux, activate the virtual environment with the platform-specific command. For remote Dify debugging, copy to , enter the Dify debug credentials, and run:

Package with the current Dify plugin CLI:

The expected package name for Marketplace submission is .

Marketplace submission

Submit exactly one package file to the official repository at:

Use an English PR title such as , select New plugin and High risk, and disclose that the plugin is a broad capability gateway that can process sensitive queries and make billable calls.

Support

• Source: https://github.com/QVerisAI/dify-qveris-mcp
• QVeris: https://qveris.ai
• Contact: [email protected]