Metadata-Version: 2.5
Name: nexatron-mcp
Version: 1.0.4
Summary: Nexatron MCP server: governed access to enterprise data for Claude, Cursor, VS Code and other MCP clients. 12 read-only tools over the Nexatron REST API.
Project-URL: Homepage, https://nexatron.io
Project-URL: Documentation, https://docs.nexatron.io
Project-URL: Support, https://nexatron.io/support
Project-URL: MCP quickstart, https://docs.nexatron.io/quickstart/mcp
Author-email: dotSolved Inc <info@nexatron.io>
Maintainer-email: Nexatron Engineering <engineering@nexatron.io>
License: MIT
License-File: LICENSE
Keywords: ai,analytics,bi,business-intelligence,claude,claude-code,claude-desktop,cursor,data,enterprise,mcp,model-context-protocol,natural-language,nexatron,nl-to-sql,semantic-layer,text-to-sql,voice
Classifier: Development Status :: 5 - Production/Stable
Classifier: Environment :: Console
Classifier: Environment :: Plugins
Classifier: Framework :: AsyncIO
Classifier: Intended Audience :: Developers
Classifier: Intended Audience :: Information Technology
Classifier: Intended Audience :: System Administrators
Classifier: License :: OSI Approved :: MIT License
Classifier: Natural Language :: English
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Classifier: Programming Language :: Python :: Implementation :: CPython
Classifier: Topic :: Database
Classifier: Topic :: Office/Business
Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
Classifier: Topic :: Scientific/Engineering :: Information Analysis
Classifier: Topic :: Software Development :: Libraries
Classifier: Topic :: Software Development :: Libraries :: Python Modules
Classifier: Typing :: Typed
Requires-Python: >=3.10
Requires-Dist: httpx<1,>=0.27.0
Requires-Dist: mcp<3,>=1.0.0
Requires-Dist: pydantic<3,>=2.0
Provides-Extra: dev
Requires-Dist: build>=1.2.0; extra == 'dev'
Requires-Dist: mypy>=1.11.0; extra == 'dev'
Requires-Dist: pytest-asyncio>=0.23.0; extra == 'dev'
Requires-Dist: pytest-cov>=5.0.0; extra == 'dev'
Requires-Dist: pytest-httpx>=0.30.0; extra == 'dev'
Requires-Dist: pytest>=8.0.0; extra == 'dev'
Requires-Dist: ruff>=0.6.0; extra == 'dev'
Requires-Dist: tomli>=2.0.0; (python_version < '3.11') and extra == 'dev'
Requires-Dist: twine>=5.1.0; extra == 'dev'
Description-Content-Type: text/markdown

# nexatron-mcp

<!-- mcp-name: io.nexatron/mcp -->

MCP server for [Nexatron](https://nexatron.io), enterprise context for every AI agent. Ask
questions about your enterprise data from Claude, Cursor, VS Code and other MCP clients. Users
see only data they're already authorized to see.

- Website: [nexatron.io](https://nexatron.io)
- Documentation: [docs.nexatron.io](https://docs.nexatron.io)
- MCP quickstart: [docs.nexatron.io/quickstart/mcp](https://docs.nexatron.io/quickstart/mcp)

## Add Nexatron from the Claude Connectors Directory

Nexatron is listed in the [Claude Connectors Directory](https://claude.ai/directory/nexatron) as
a Community connector. In Claude, open the Connectors Directory, search for **Nexatron**, choose
**Connect**, and sign in to your Nexatron workspace with your existing account (company SSO is
optional). Nothing to install and no API key to copy. A workspace admin approves the app before
users connect it.

Setup guide: [docs.nexatron.io/integrations/claude](https://docs.nexatron.io/integrations/claude).

## Two ways to connect

- **Hosted endpoint (recommended):** `https://api.nexatron.io/api/v1/mcp`, Streamable HTTP
  with OAuth 2.1. This is what the Claude Connectors Directory listing uses, and other
  remote-capable clients (Cursor, VS Code) can add the same URL. It has up to ten tools (seven
  analytics, three action), filtered by workspace entitlement and the scopes you grant. A
  read-only grant sees the seven analytics tools: `ask`, `list_sources`, `list_metrics`,
  `explain_metric`, `query_metric`, `compare_metric_across_sources` (several metrics in one
  call) and `audit`. The action tools are `list_actions`, `dry_run` and `execute_action`.
  See [docs.nexatron.io/quickstart/mcp](https://docs.nexatron.io/quickstart/mcp).
- **Local stdio package (this package):** `uvx nexatron-mcp`, authenticated with an `nxa_`
  API key. A set of 12 read-only tools over the Nexatron REST API, for self-hosted Nexatron
  instances and local use; see [Available tools](#available-tools-local-stdio-package). The
  two surfaces have different tools and are versioned independently.

The rest of this README covers the local stdio package.

## Install

```bash
pip install nexatron-mcp
# or
uvx nexatron-mcp
```

## Setup

### Claude Desktop

Add this to `claude_desktop_config.json`. On macOS it is at
`~/Library/Application Support/Claude/claude_desktop_config.json`; on Windows,
`%APPDATA%\Claude\claude_desktop_config.json`.

```json
{
  "mcpServers": {
    "nexatron": {
      "command": "uvx",
      "args": ["nexatron-mcp"],
      "env": {
        "NEXATRON_API_KEY": "nxa_your_api_key",
        "NEXATRON_URL": "https://api.nexatron.io/api/v1"
      }
    }
  }
}
```

Restart Claude Desktop. The Nexatron tools then appear.

### Claude Code

```bash
claude mcp add nexatron \
  --env NEXATRON_API_KEY=nxa_your_key \
  --env NEXATRON_URL=https://api.nexatron.io/api/v1 \
  -- uvx nexatron-mcp
```

Options for `claude` go before `--`; everything after it is the command that starts the server.

### Cursor / VS Code

Add to `.cursor/mcp.json` (project) or `~/.cursor/mcp.json` (global), or to your VS Code MCP settings:

```json
{
  "mcpServers": {
    "nexatron": {
      "command": "uvx",
      "args": ["nexatron-mcp"],
      "env": {
        "NEXATRON_API_KEY": "nxa_your_key",
        "NEXATRON_URL": "https://api.nexatron.io/api/v1"
      }
    }
  }
}
```

## Environment Variables

| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
| `NEXATRON_API_KEY` | Yes | (none) | Your Nexatron API key (starts with `nxa_`) |
| `NEXATRON_URL` | No | `https://api.nexatron.io/api/v1` | Nexatron API URL |
| `NEXATRON_MCP_LOCAL_TOKEN` | No | (generated) | Bearer token for [local SSE mode](#local-sse-mode-development) only |

## Available tools (local stdio package)

These are the 12 tools the `nexatron-mcp` stdio package exposes against the Nexatron REST API. All are read-only. The hosted endpoint has a different set; see [Two ways to connect](#two-ways-to-connect).

| Tool | Description |
|------|-------------|
| `query` | Ask questions about your data in plain English |
| `list_connections` | See all data source connections |
| `list_metrics` | View certified metrics in the semantic layer |
| `list_views` | View logical views |
| `get_schema` | Explore database schemas |
| `test_connection` | Test data source connectivity |
| `detect_schema_drift` | Find schema changes |
| `search_knowledge_base` | Search uploaded documents (RAG) |
| `list_conversations` | View recent query history |
| `get_report` | Retrieve a saved report |
| `get_credit_balance` | Check remaining query credits |
| `whoami` | Show your user info and organization |

The package also provides one resource, `nexatron://platform/info`.

## Example

After setup, ask Claude:

> "Use Nexatron to show me total revenue by product category for Q4"

Claude calls the `query` tool, which sends your question through Nexatron and returns the answer with the generated query and results.

## Local SSE mode (development)

```bash
NEXATRON_API_KEY=nxa_... nexatron-mcp --sse --port 8001
```

This starts a local SSE server on `127.0.0.1:8001` that uses your API key for every request,
so it guards itself:

- Every request needs `Authorization: Bearer <local token>`. Without `NEXATRON_MCP_LOCAL_TOKEN`
  set, a token is generated at start and printed once to your terminal (stderr); set the variable
  to a long random value (24+ characters) to choose your own.
- A browser request from any origin other than the server's own address is refused, and the
  `Host` header must be the server's address (DNS-rebinding protection).
- `--host` other than a loopback address is refused unless you set `NEXATRON_MCP_LOCAL_TOKEN`
  yourself: everyone who has that token acts as you.
- A wildcard `--host` (`0.0.0.0`, `::`) is refused unless you name each address clients use with
  `--allowed-host HOST[:PORT]` (repeatable; the port defaults to `--port`). The `Host` a client
  sends has to match one of them exactly. `--allowed-host` also adds addresses to a specific
  `--host`, such as a DNS name for it. An IPv6 address is written in brackets in client URLs,
  for example `http://[::1]:8001/sse`.

It is for development on your own machine. It is not the hosted remote server; remote clients
should use `https://api.nexatron.io/api/v1/mcp`.

## Working from source

To work against the package locally, install it from the source distribution:

```bash
pip download nexatron-mcp --no-binary :all: --no-deps
tar xf nexatron-mcp-*.tar.gz && cd nexatron-mcp-*
pip install -e .
nexatron-mcp
```

Customers with a source agreement can contact `ai@nexatron.io` for repository access.

## Privacy Policy

Full policy: **<https://dotsolved.ai/privacy>**. Summary of how this connector handles data:

**What is collected.** The server sends the question or arguments you pass to a tool, plus
your `NEXATRON_API_KEY`, to the Nexatron instance at `NEXATRON_URL`. It collects nothing
else: no conversation history, no chat transcripts, no files, and no telemetry of its own.
It does not read Claude's memory, conversation summaries, or user files.

**How it is used and stored.** Requests are processed by your Nexatron instance to answer
the question and are recorded in that instance's audit trail, which exists so your
administrators can review who asked what. Query results are returned to the caller and are
not retained by this package, which holds no local database and writes no data to disk; the
API key is read from the environment and kept only in memory for the life of the process.

**Third-party sharing.** dotSolved does not sell or rent this data. Your Nexatron instance
routes questions to whichever LLM provider that instance is configured to use; on a
bring-your-own-LLM deployment that is your own Azure OpenAI, Bedrock, or Anthropic
contract, and no question transits a dotSolved-default provider. Self-hosted deployments
send nothing to dotSolved at all.

**Retention.** Governed by your Nexatron instance's tenant configuration, which its
administrators control. This package imposes no retention of its own.

**Contact.** Data updates and removals: `privacy@nexatron.io`. General privacy questions,
including requests for a copy of your personal information: `info@nexatron.io`. Security
disclosures: `security@nexatron.io` (see [SECURITY.md](SECURITY.md)). These are the
addresses named in the full policy linked above.

## License

MIT. Copyright (c) 2026 dotSolved Systems, Inc. See [LICENSE](LICENSE).
