kortex-mcp
Enables Claude to discover and semantically search enterprise datasets through the Kortex data plane, exposing list_collections and retrieve tools for natural-language queries.
README
kortex-mcp
MCP server that exposes the Kortex data plane to Claude Desktop. Wraps the two data plane endpoints so Claude can discover and search enterprise datasets without leaving the conversation.
Prerequisites
- Python 3.11+
uv(recommended) or pip- A running Kortex backend (
kortex/src/back) - An active Kortex API key with at least one collection in scope
Installation
cd kortex/src/kortex_mcp
uv sync # creates .venv and installs mcp + httpx
Or with pip:
pip install -e .
Configuration
The server reads two environment variables:
| Variable | Required | Default | Description |
|---|---|---|---|
KORTEX_API_KEY |
yes | — | API key in kx_live_<id>_<secret> format |
KORTEX_API_URL |
no | http://localhost:8000 |
Base URL of the Kortex backend |
Claude Desktop setup
Edit ~/.config/Claude/claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json).
Choose one of the two options below, then restart Claude Desktop. The Kortex tools will appear in the tool picker (hammer icon).
Option A — Local clone
Use this if you have cloned the repo and want to run your working copy.
{
"mcpServers": {
"kortex": {
"command": "uv",
"args": [
"run",
"--project", "/absolute/path/to/kortex/src/kortex_mcp",
"python", "-m", "mcps.kortex_mcp.server"
],
"env": {
"KORTEX_API_URL": "http://localhost:8000",
"KORTEX_API_KEY": "kx_live_<id>_<secret>"
}
}
}
}
Replace /absolute/path/to/kortex/src/kortex_mcp with the actual path on your machine.
Option B — Directly from GitHub (no clone needed)
Use this to always run the latest tagged release without maintaining a local clone. uvx downloads, caches, and runs the package in one step.
{
"mcpServers": {
"kortex": {
"command": "uvx",
"args": [
"--from", "git+https://github.com/ibkortex/kortex_mcp@v0.0.1",
"kortex-mcp"
],
"env": {
"KORTEX_API_URL": "http://localhost:8000",
"KORTEX_API_KEY": "kx_live_<id>_<secret>"
}
}
}
}
Tools
list_collections
Lists all collections the API key has access to.
Returns each collection with:
id— use this inretrievenombre/descripcion— human-readable name and descriptionavailableVersions— logical version labels you can query (e.g.["v1", "v2"])
Call this first to understand what data is available before issuing a search.
retrieve(query, ...)
Semantic search against Amazon Bedrock Knowledge Bases.
| Parameter | Type | Default | Description |
|---|---|---|---|
query |
string | — | Natural-language question or search phrase |
collections |
string[] |
all accessible | Collections to search. Each entry is "collection_id" or "collection_id:version_label". Omit to search all accessible collections at their default version. |
number_of_results |
integer | 10 |
Maximum passages to return |
Each result includes collectionId, versionLabel, content, score, and sourceUri.
Requesting a collection outside the API key's scope returns a 403 — Claude cannot query collections it has not been granted access to.
Example conversation
User: What collections do I have access to?
Claude calls list_collections and summarises the response.
User: Search for documents about credit risk models in the regulatory collection.
Claude calls retrieve with the appropriate collection_id and surfaces the most relevant passages.
User: Show me the v1 version only.
Claude calls retrieve again with collections: ["<id>:v1"].
Testing with MCP Inspector
MCP Inspector wraps the server process and opens a local web UI where you can call tools interactively — no Claude Desktop needed.
Local clone:
KORTEX_API_KEY=kx_live_... KORTEX_API_URL=http://localhost:8000 \
npx @modelcontextprotocol/inspector \
uv run --project /absolute/path/to/kortex/src/kortex_mcp \
python -m mcps.kortex_mcp.server
From GitHub:
KORTEX_API_KEY=kx_live_... KORTEX_API_URL=http://localhost:8000 \
npx @modelcontextprotocol/inspector \
uvx --from git+https://github.com/ibkortex/kortex_mcp@v0.0.1 kortex-mcp
Open http://localhost:5173 in your browser. Use the Tools tab to call list_collections and retrieve and inspect the raw responses.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.