MCP Server Configuration
MCP servers in Cognivo Chat are configured and maintained by Cognivo. They are not user-configurable at this time.
This page describes the server configuration fields for reference.
Configuration Fields
Each MCP server is defined by the following fields:
| Field | Description |
|---|---|
| Name | A display name for the server, shown in the side panel |
| Description | Optional short description of what the server provides |
| Server URL | The address of the MCP server endpoint |
| Connection Type | How the client communicates with the server: Streamable HTTP or SSE |
| Authentication | The auth method the server requires |
| Trust | Confirmation that the server is trusted to process requests on behalf of the user |
Connection Types
Two connection types are supported:
- Streamable HTTP — the client sends requests over a standard HTTP connection; responses stream back as they are generated
- SSE (Server-Sent Events) — the server pushes a stream of events to the client over a persistent connection
The appropriate connection type depends on how the MCP server is hosted.
Authentication Methods
MCP servers may require authentication. Three methods are supported:
- Auto-detect — the client attempts to detect the appropriate method automatically
- API Key — a key is included with each request using a configured header format
- OAuth — the connection uses an OAuth authorization flow