What credential and transport types can I use with MCP Assistant and AI platforms?
Last modified date:
2025-09-03
Applicable Products
- MCP Assistant
- QTS
- QuTS hero
Explanation
Credential types
A credential is a method of authentication that enables an MCP Client to securely connect to an MCP Server. QNAP MCP Assistant supports two types of credentials:
- Token: A string-based identifier passed in HTTP/HTTPS headers. This allows the MCP client to be identified without requiring a username and password. This method is lightweight and easy to use, making it suitable for most general-purpose integrations.
- Key: A certificate-based package used over HTTPS for mutual verification. This involves downloading a credential package from the MCP Server, which includes the qmcp executable. During authentication, the MCP Host uses this executable and its associated certificate to establish a trusted connection with the MCP server. This method provides stronger identity verification and is recommended for secure or enterprise environments.
Credentials are essential for authorizing access to MCP Tools and ensuring secure communication between components.
Transport types
A transport type defines how data is transmitted between an MCP Client and an MCP Server. QNAP MCP Assistant supports the following three types of transport:
- STDIO: A basic transport method that uses standard input and output streams. This is typically used for local communication or during testing phases. It does not involve any network communication and is mainly suitable for scenarios where the MCP Client and Server run on the same host.
- SSE (Server-Sent Events): A lightweight, one-way communication method where the server pushes updates to the client over an HTTP connection. SSE is ideal for real-time monitoring or status updates, allowing clients to receive continuous data streams without the need for repeated polling. It works best for scenarios with low-latency, event-driven communication needs.
- If using SSE, the URL must end with
/sse, such as:http://<NAS_IP>:8442/sse
- If using SSE, the URL must end with
- Streamable HTTP:A bi-directional HTTP-based transport mode that allows both request and response bodies to be streamed. This method is suitable for handling large data volumes or long-running operations, such as file transfers or real-time command execution. It provides a good balance between flexibility and performance for modern network applications.
- If using Streamable HTTP, the URL must end with
/mcp, such as:http://<NAS_IP>:8442/mcp
- If using Streamable HTTP, the URL must end with
Note
- The Key is for the STDIO transport type, whereas the Token is for the SSE and Streamable HTTP transport types.
- Different MCP hosts support different types. Please refer to the MCP Host's own documentation to determine its applicable transport type.
Credential and Transport Types Supported by AI Platforms
Here is a breakdown of which credential and transport types are supported by various AI platforms for QNAP MCP Assistant:
| AI Platform | Supported Credential Types | Supported Transport type |
|---|---|---|
| Claude Desktop | Key | STDIO |
| Cline | Key | STDIO |
| Copilot | Key, Token | STDIO, SSE, streamable HTTP |
Note
- The supported credential types for each AI platform are subject to change and may be updated over time.
- Due to limitations of the AI platforms themselves, platforms such as ChatGPT, Deepseek, and Grok do not support MCP configuration.
