Using Huwise's MCP server

MCP server functionality is not included directly in your plan. For more information, please contact our support team.

The Model Context Protocol (MCP) is a standard that makes it easier for AI systems and applications to talk to each other. Instead of every tool or model needing its own custom API connection, MCP provides a common language they can all use.

Accordingly, Huwise's MCP server allows generative AI agents to use Huwise APIs and to search our API documentation.

This documentation focuses on configuring Claude Desktop and a Microsoft Copilot agent, though you can use the Huwise MCP server with other tools that support it, such as AI-powered code editors like Cursor or Windsurf.

The Huwise MCP server is a stand-alone server, hosted by Huwise on its own infrastructure. It guarantees fast and easy access, without needing to worry about server maintenance and upgrades.

To set up an MCP server on Claude Desktop, the following prerequisites must be met:

• Claude Desktop is installed on your machine (Windows, macOS or Linux)

• You have Node.js version 18 or higher

• You have npm or yarn for package management

You must also have an API key with at least the Browse all datasets permission to be able to use the MCP server.

To define an API key, see Managing API keys.

The Claude Desktop configuration file is used to define and configure MCP servers on your tool.

You'll find the files for the different operating systems—Windows, Mac OS and Linux—at the following locations:

On macOS :

~/Library/Application Support/Claude/claude_desktop_config.json

On Windows :

%APPDATA%\Claude\claude_desktop_config.json

On Linux :

~/.config/Claude/claude_desktop_config.json

In the configuration file, it is necessary to add these lines and replace the values indicated below.

{
  "mcpServers": {    
    "": {
      "command": "npx",
      "args": [
        "-y",
        "supergateway@3.4.0",
        "--streamableHttp",
        "https://mcp.huwise.com/mcp",
        "--header",
        "x-domain: <URL OF HUWISE MARKETPLACE>",
        "--header",
        "x-apikey: <API KEY>"
      ]
    }
  }
}

It will be necessary to specify the actual values in these lines:

<URL OF HUWISE MARKETPLACE>

with the URL of your portal, and

<API KEY>

with the API key you want to use in the MCP server.

In order to use an Huwise MCP server in a Microsoft Teams and Microsoft 365 environment, you need to configure a Copilot agent.

In MCP terminology, the agent is the part that connects to the server and makes its features available, in this case Microsoft Teams and Microsoft 365.

• Users and creators must have a license to use Microsoft 365 Copilot

• Creators must have the necessary permissions to create and access a Copilot Studio environment.

According to the documentation provided by Microsoft:

The Huwise MCP server must be declared as one of the Copilot agent's tools, and configured with a customized connection by following the instructions here: Connect to an existing Model Context Protocol (MCP) server.

In order to facilitate the creation of the connector, you can use the following swagger:

swagger: '2.0'
info:
  title: Huwise MyDataMarketplace MCP Client
  description: MCP Client to connect to Huwise's Data Marketplace demo.
  version: 1.0.0
host: mcp.huwise.com
basePath: /
schemes:
  - https
paths:
  /mcp:
    post:
      summary: Huwise MCP Server
      x-ms-agentic-protocol: mcp-streamable-1.0
      operationId: InvokeMCP
      responses:
        '200':
          description: Success

At this point, declare the two header variables, "x-domain" and "x-apikey", in the connector. These variables are necessary to authenticate the assistant to your data marketplace, particularly for private data.

Then, add two strategies by clicking on the New Strategy button on the 3 - Definition tab.

The strategies need to be defined using these parameters:

explore_api_documentation

explore_get_datasets

explore_get_dataset

explore_get_dataset_records