Indholdet er maskineoversat. Se Ansvarsfraskrivelse for maskinoversættelse.

What credential and transport types can I use with MCP Assistant and AI platforms?

Hvilke legitimations- og transporttyper kan jeg bruge med MCP Assistant og AI-platforme?

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
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

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.

Gældende produkter

MCP Assistant
QTS
QuTS hero

Forklaring

Legitimationstyper

Enlegitimationer en metode til autentifikation, der gør det muligt for en MCP-klient at oprette en sikker forbindelse til en MCP-server. QNAP MCP Assistant understøtter to typer legitimationsoplysninger:

Token:En strengbaseret identifikator, der sendes i HTTP/HTTPS-headere. Dette gør det muligt at identificere MCP-klienten uden at kræve brugernavn og adgangskode. Denne metode er let og nem at bruge, hvilket gør den velegnet til de fleste generelle integrationer.
Nøgle:En certifikatbaseret pakke, der bruges over HTTPS til gensidig verifikation. Dette indebærer download af en legitimationspakke fra MCP-serveren, som inkluderer den eksekverbare qmcp. Under autentifikation bruger MCP-værten denne eksekverbare fil og det tilknyttede certifikat til at etablere en betroet forbindelse med MCP-serveren. Denne metode giver stærkere identitetsverifikation og anbefales til sikre eller virksomhedsmiljøer.

Legitimationsoplysninger er essentielle for at godkende adgang til MCP-værktøjer og sikre sikker kommunikation mellem komponenter.

Transporttyper

Entransporttypedefinerer, hvordan data overføres mellem en MCP-klient og en MCP-server. QNAP MCP Assistant understøtter følgende tre typer transport:

STDIO:En grundlæggende transportmetode, der bruger standard input- og outputstrømme. Dette bruges typisk til lokal kommunikation eller under testfaser. Det involverer ikke nogen netværkskommunikation og er hovedsageligt egnet til scenarier, hvor MCP-klienten og serveren kører på samme vært.
SSE (Server-Sent Events): En letvægts, envejs kommunikationsmetode, hvor serveren sender opdateringer til klienten over en HTTP-forbindelse. SSE er ideel til realtidsmonitorering eller statusopdateringer, der giver klienter mulighed for at modtage kontinuerlige datastrømme uden behov for gentagen polling. Det fungerer bedst til scenarier med lav-latens, begivenhedsdrevet kommunikationsbehov.
- Hvis du bruger SSE, skal URL'en ende med/sse, såsom:http://<NAS_IP>:8442/sse
Streamable HTTP:En tovejs HTTP-baseret transporttilstand, der tillader både forespørgsels- og svarindhold at blive streamet. Denne metode er velegnet til håndtering af store datamængder eller langvarige operationer, såsom filoverførsler eller realtidskommandoeksekvering. Den giver en god balance mellem fleksibilitet og ydeevne for moderne netværksapplikationer.
- Hvis du bruger Streamable HTTP, skal URL'en ende med/mcp, såsom:http://<NAS_IP>:8442/mcp

Note

Nøglen er til STDIO transporttypen, mens Token er til SSE og Streamable HTTP transporttyperne.
Forskellige MCP-værter understøtter forskellige typer. Se venligst MCP-værtens egen dokumentation for at bestemme dens gældende transporttype.

Legitimations- og transporttyper understøttet af AI-platforme

Her er en oversigt over, hvilke legitimations- og transporttyper der understøttes af forskellige AI-platforme for QNAP MCP Assistant:

AI-platform	Understøttede legitimationsoplysningstyper	Understøttet Transporttype
Claude Desktop	Nøgle	STDIO
Cline	Nøgle	STDIO
Copilot	Nøgle, Token	STDIO, SSE, streamable HTTP

Note

De understøttede legitimationsoplysningstyper for hver AI-platform kan ændres og opdateres over tid.
På grund af begrænsninger i AI-platformene selv understøtter platforme som ChatGPT, Deepseek og Grok ikke MCP-konfiguration.

Was this article helpful?

Yes. No.

Please tell us how this article can be improved:

The article is missing important information
The article's solutions do not work
The article is too complicated
The article contains incorrect information
The article is out-of-date

If you want to provide additional feedback, please include it below.

Lager

Netværk

Udvidelsestilbehør

Overvågning

NAS

Netværk

Overvågning

Applicable Products

Explanation

Credential types

Transport types

Credential and Transport Types Supported by AI Platforms

Gældende produkter

Forklaring

Legitimationstyper

Transporttyper

Legitimations- og transporttyper understøttet af AI-platforme

Choose Your Country or Region

Asia

Europe

America