Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/vancovx/KunnaClienteMCP/llms.txt

Use this file to discover all available pages before exploring further.

This guide walks you through running the Kunna MCP Client inspector locally and connecting it to a live MCP server. By the end you will have the Vite development server running at http://localhost:5173, the inspector open in your browser, and a successful MCP handshake with a server of your choice.
1

Clone the repository

Clone the project from GitHub and move into the project directory:
git clone https://github.com/vancovx/KunnaClienteMCP.git && cd KunnaClienteMCP
2

Install dependencies

Install all Node.js dependencies declared in package.json:
npm install
Node.js 18 or higher is required. The project uses ES modules ("type": "module" in package.json), so older Node versions are not supported.
3

Start the development server

Start Vite in development mode:
npm run dev
Vite starts on http://localhost:5173 with Hot Module Replacement (HMR) enabled. Any change you save to a source file is reflected in the browser immediately without a full reload.
4

Open the Inspector

Navigate to http://localhost:5173 in your browser. From the top navigation bar, click Inspector to open the MCP inspection panel.
5

Connect to an MCP server

Fill in the connection form that appears in the Inspector:
  1. Transport — choose HTTP (Streamable HTTP) or SSE depending on what your server supports.
  2. URL — enter the full endpoint, for example http://localhost:3001/mcp.
  3. Auth — select None if the server is unauthenticated, or select Bearer and paste a token if the server requires it.
  4. Click Connect.
The client performs the MCP handshake, then calls listTools, listPrompts, and listResources automatically. The results appear in the sidebar within seconds.
6

Explore capabilities

After a successful handshake, the sidebar is populated with everything the server exposes: tools, prompts, and resources. Click any item to open its detail panel. For tools and prompts, a dynamic form is generated from the item’s JSON Schema — fill in the fields and click the execute button to call the server and view the formatted response in the activity console.

​
Typical workflow with the Kunna Server

If you are using the companion Kunna MCP server alongside this client, the recommended workflow is:
  1. Start the Kunna MCP server — it listens by default at http://localhost:3000/mcp.
  2. Open the Inspector, select HTTP transport, enter http://localhost:3000/mcp as the URL, choose Bearer auth, and supply the server’s MCP_AUTH_TOKEN. In development mode the server skips token verification, so auth is not strictly required.
  3. Explore the available tools — including search-campus-buildings, query-data, and query-aggregation — as well as the IoT report prompts exposed by the server.
  4. Select any tool or prompt, fill in the generated form (or switch to raw JSON mode), and execute directly from the browser. Review the formatted result and inspect the raw request/response pair in the activity console.

​
Available npm scripts

ScriptDescription
devStart the Vite development server with HMR at http://localhost:5173
buildCompile and bundle the app for production into the dist/ directory
previewServe the production build locally for a pre-deploy sanity check
lintRun ESLint across all source files
build-dockerBuild the Docker image tagged kunnaclientemcp-frontend:latest
If the connection attempt fails with a network error, the cause is almost always CORS. The MCP server must explicitly allow the origin from which the client is served (e.g. http://localhost:5173 during development). On the Kunna server this is configured with the CORS_ALLOWED_ORIGINS environment variable.

Build docs developers (and LLMs) love

Get started for freeTalk to us