Kyvos Model Context Protocol (MCP) Server 2.1.0

This section details the Kyvos Model Context Protocol (MCP) Server, which enables AI applications or agents to connect with the Kyvos platform, submit natural language queries, and retrieve insights from Kyvos semantic models through standardized MCP communication.

The Kyvos MCP Server is a server-side component that connects the Kyvos platform with the Model Context Protocol (MCP) client-server architecture. The server supports both SSE and STDIO communication modes and allows secure authentication using user-provided Kyvos credentials (basic and OAuth2.0). It accepts natural language (NL) queries, translates them into executable SQL, and retrieves results from the Kyvos engine. This setup allows users to query Kyvos semantic models using natural language, enabling AI-driven insights without the need for advanced technical skills.

Authentication Support

To ensure secure integration and access, the Kyvos MCP Server supports the following authentication mechanisms:

• Basic Authentication: Using a valid username and password combination.

• OAuth 2.0 Authentication: For token-based secure access, suitable for enterprise-grade deployments.

Supported Kyvos Model Context Protocol (MCP) Server Versions

Kyvos supports Model Context Protocol (MCP) Server versions 2.0.0 and 2.1.0.

Supported Deployment Modes

Kyvos MCP Server can be deployed in the following communication modes:

• Local Mode

  • Standard Input/Output (STDIO)

• Remote Mode

  • Streamable HTTP

  • Server-Sent Events (SSE)

This flexibility allows integration in a variety of system architectures, including containerized environments or remote LLM agents.

The MCP Kyvos Server enables agentic applications to interact with the Kyvos platform for querying business data. It supports two transport modes:

• Streamable HTTP: The recommended transport for remote integrations. It operates statelessly over HTTP POST to the /mcp endpoint. It also supports Basic and OAuth authorization.

• SSE (Server-Sent Events): This transport is suited for remote integrations. It uses HTTP requests for communication. It allows servers to handle multiple client connections efficiently. SSE mode supports both Basic and OAuth authorization. OAuth requires users to authenticate using their Kyvos credentials before establishing a connection, providing a secure and standardized login mechanism.

• STDIO (Standard I/O): This transport is primarily used for inter-process communication within the same system. It’s particularly suitable for command-line tools and local integrations where the client and server operate within the same process. Only Basic authorization is supported in this mode.
  
  

Open

1. A user poses a natural language (NL) question.

2. The MCP Client uses an LLM to interpret the question and interacts with the MCP Kyvos Server to retrieve relevant answers.

3. The server translates the natural language input into an SQL query.

   • It communicates with the Kyvos Semantic Model, sending queries and receiving both metadata and data.

   • The response is then sent back to the MCP Client, which forwards the final answer to the user.

The Kyvos MCP Server helps you to:

• Enable Conversational BI within dashboards and analytical applications.

• Provide self-service analytics through natural language without requiring SQL expertise.

• Accelerate insight generation for business users using AI-driven query transformation.

MCP Server Tools

The Kyvos MCP Server provides a set of standardized tools accessible to MCP clients:

• kyvos_list_semantic_model: Retrieves a list of all available and accessible semantic models for the authenticated user within Kyvos.

• kyvos_list_semantic_model_details: Retrieves column metadata for a specified semantic model as:

  • Column name

  • Associated tags

  • Descriptions

  • Query generation rules

  • Querying instructions

  • Summary instructions

• kyvos_execute_query: Executes a Spark SQL query on Kyvos and returns a json based result set.

Support for No Authentication

The MCP Kyvos Server supports for no authentication mode for scenarios where the client application only supports OAuth-based MCP servers, but the user does not want to go through a real OAuth flow.

In this mode:

• The client does not perform real OAuth authentication.

• The MCP server authenticates internally using configured Kyvos username and Personal Access Token.

• The server generates and returns simulated OAuth tokens to the client.

How It Works

When no authentication is enabled:

1. The client connects as if using OAuth.

2. The MCP server authenticates to Kyvos using:

   • KYVOS_USERNAME

   • KYVOS_PERSONAL_ACCESS_TOKEN

3. The server returns those tokens to the client as a simulated OAuth response.

This allows clients that only support Basic-style authentication to operate in environments where OAuth mode is expected.

Starting the Server in No-Auth Mode

When to Use No-Auth

Use no_auth when:

• Your client (e.g. Claude connector) requires an OAuth-based MCP server.

• You do not want to configure or go through a real OAuth flow.

• You prefer to authenticate using a username and PAT set directly in the server environment.

Support for AI Space 

The MCP Kyvos Server supports scoped querying through URL query parameters appended to the `/sse` endpoint. The `type` parameter determines the querying mode.

Query Parameters

Mode: AI Space (`requestType=AI_Space`)

Targets semantic models residing within a specific Kyvos AI Space. Both `AISpaceName` and `folderName` are required.
http://<machine_ip>:<port>/sse?requestType=AI_Space&folderName=SalesFolder&AISpaceName=SalesSpace

Mode: Semantic Model (`requestType=Semantic_Model`)

Targets semantic models of a particular folder, or a specific semantic model directly. `semanticModelName` is optional — if not provided, all semantic models within the given folder will be available for querying. If the user intends to query only a particular semantic model, `semanticModelName` can be passed as a parameter; otherwise, only `folderName` is sufficient.
http://:/sse?requestType=Semantic_Model&folderName=SalesFolder&semanticModelName=…

Without `semanticModelName`: http://<machine_ip>:<port>/sse?requestType=Semantic_Model&folderName=SalesFolder

Client Configuration Example

Scoped Querying in STDIO Mode

Similar to SSE mode's URL query parameters (`requestType`, `folderName`, etc.), STDIO mode supports scoped querying via environment variables or CLI `--env-file`.

Python Requirements

Python >=3.10 is need for Kyvos MCP Server.

Installation

Install the mcp-kyvos-server package from pip:

Configuration and Parameters

The server can be configured via environment variables or command-line flags. CLI flags override environment variables.

Creating .env file

To create a .env file with the required parameters for your MCP-Kyvos server:

Usage

Streamable HTTP

1. Start the MCP server with streamable-http transport (or omit --transport since it is the default), and do one of the following:

   • Using env file: mcp-kyvos-server --transport streamable-http --env-file /path/to/.env

   • Provide arguments directly:

     mcp-kyvos-server --kyvos-url https://your-kyvos-endpoint --kyvos-username user123 --kyvos-personal-access-token your-token

2. Configure your client application to point to the /mcp endpoint:

   {   "mcpServers": {     "kyvos-http": {       "url": "http://<machine_ip>:<port>/mcp"     }   } }

   1. With scoped query parameters:

      • AI Space mode: http://<machine_ip>:<port>/mcp?entityType=AISpace&folderName=SalesFolder&entityName=SalesSpace

SSE Mode

1. Start the MCP server with SSE transport.

   mcp-kyvos-server --transport sse --env-file /path/to/.env

   or provide arguments directly:

   mcp-kyvos-server \ --kyvos-url https://your-kyvos-endpoint \ --kyvos-username user123 \ --kyvos-password pass123

2. Configure your client application to include the SSE server in its MCP server configuration. For example:

   { "mcpServers": { "kyvos-sse": { "url": "http://<machine_ip>:<port>/sse" } } }

STDIO Mode

1. Configure your client application. For example:

OR

Claude Desktop Usage

Streamable HTTP Mode Support (Remote)

To connect Claude Desktop to a remote Streamable HTTP MCP server, use mcp-remote, a CLI tool that bridges remote servers to local stdio clients.

To setup with mcp-remote, perform the following steps.

1. Install Node.js (v18 or higher) from here.

2. Configure Claude Desktop to use mcp-remote via npx:

   { "mcpServers": { "mcp-server": { "command": "npx", "args": [ "mcp-remote", "<http://<your-machine-ip>>:<port>/mcp", "--allow-http" ] } } }

3. Replace <your-machine-ip> and <port> with the actual address of your Streamable HTTP server. Use the --allow-http flag if using HTTP-based MCP server URL. After saving the configuration file, completely quit Claude Desktop and restart it. The application needs to restart to load the new configuration and start the MCP server.
   If you encounter an OAuth authorization error, try the following steps:

4. Delete the .mcp-auth folder.

   • On Linux/macOS:

     ~/.mcp-auth

   • On Windows (Command Prompt):

     C:\Users\<your-username>\.mcp-auth

5. Restart the mcp-kyvos-server.

Passing Scoped Query Parameters via Headers (Recommended for Claude Desktop)

1. Claude Desktop uses mcp-remote as a stdio-to-http bridge. Because Claude Desktop cannot append query parameters to the mcp URL directly, you can pass scoped query parameters as custom request headers instead. The server reads these headers as a fallback when URL query parameters are absent.

Supported Headers

Configuration Example

1. Add this to your claude_desktop_config.json:

Mode-specific Examples
AI Space mode:

Semantic Model mode (specific semantic model):

Semantic Model mode (all models in folder):

Security and Access Control

Kyvos enforces all existing data security policies and access privileges based on the authenticated user's profile. The MCP server ensures that only authorized users can access specific semantic models, metadata, and business data, in alignment with the organization’s governance and role-based access controls.

For a sample client implementation to interact with Kyvos MCP server, refer to Kyvos Sample Client.