Ntro MCP server

The Ntro MCP server exposes Ntropii Workspace as tools (write operations), resources (read-only data), and prompts (guided multi-step flows) for any Model Context Protocol client.

What’s included

Type	Count	Examples
Tools	8	`ntro_tenant_create`, `ntro_workflow_run`, `ntro_workflow_deploy`
Resources	11	`ntro://tenants`, `ntro://tasks/{id}`, `ntro://schedule`
Prompts	3	`onboard_spv`, `run_nav`, `platform_status`

Install

pip (production)
Editable (local dev)

pip install ntro-mcp
ntro-mcp --help

uv pip install -e ~/ntropii/ntro-python --python ~/.ntro-dev/bin/python
uv pip install -e ~/ntropii/ntro-mcp     --python ~/.ntro-dev/bin/python

~/.ntro-dev/bin/ntro-mcp --help

Configuration precedence

The server resolves the API connection in this priority order:

--ntro-host / --ntro-api-key CLI flags
NTRO_HOST / NTRO_API_KEY environment variables
--connection NAME → named entry in ~/.ntro/config.toml
default_connection_name in ~/.ntro/config.toml

Run ntro auth login first (API keys) to seed the config file.

Three transports

stdio (Claude Desktop / Claude Code)
Streamable HTTP (claude.ai)
HTTP (other MCP clients)

The recommended local transport. The MCP client spawns ntro-mcp as a child process and talks over stdin/stdout. Zero networking required.Claude Desktop — edit your config file:

OS	Path
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json`
WSL	`/mnt/c/Users/<Username>/AppData/Roaming/Claude/claude_desktop_config.json`

{
  "mcpServers": {
    "ntro": {
      "command": "/home/you/.ntro-dev/bin/ntro-mcp",
      "args": ["--transport", "stdio", "--connection", "production"]
    }
  }
}

Or use explicit env vars instead of a connection name:

{
  "mcpServers": {
    "ntro": {
      "command": "/home/you/.ntro-dev/bin/ntro-mcp",
      "args": ["--transport", "stdio"],
      "env": {
        "NTRO_HOST": "https://api.ntropii.com/v1",
        "NTRO_API_KEY": "ntro_prod_xxx"
      }
    }
  }
}

Restart Claude Desktop. The ntro tools appear in the tool picker.Claude Code uses the same JSON shape — drop it into ~/.claude/mcp.json (global) or <project>/.claude/mcp.json (project-local).

For claude.ai, the MCP server has to be reachable over HTTPS. Run it locally and tunnel with cloudflared:

# Terminal 1 — start the MCP server
ntro-mcp --transport http --port 8000 --connection production

# Terminal 2 — expose it over HTTPS
cloudflared tunnel --url http://localhost:8000
# → https://random-words.trycloudflare.com

In claude.ai: Settings → Connected Apps → Add MCP Server → paste the tunnel URL.For longer-term use, run on a server you control rather than relying on a development tunnel.

For Copilot Studio, custom orchestrators, or any MCP client that prefers HTTP:

ntro-mcp --transport http --port 8000 --connection production

The server speaks the standard MCP HTTP transport. See your client’s MCP setup docs for how to register the URL.

CLI reference

ntro-mcp [OPTIONS]

  --transport {http,stdio}    Transport (default: stdio)
  --port INT                  HTTP port (default: 8000)
  --host TEXT                 HTTP bind host (default: 127.0.0.1)
  -c, --connection NAME       Named connection from ~/.ntro/config.toml
  --ntro-host URL             Workspace API URL (overrides config)
  --ntro-api-key KEY          API key (overrides config)

Tools

Write operations — each tool accepts a structured payload, calls Ntropii Workspace, and returns the resulting object.

Tool	Purpose
`ntro_whoami`	Get the current user identity and accessible tenants
`ntro_integration_create`	Register a data platform (Databricks, Snowflake, Fabric, Postgres)
`ntro_integration_test`	Test connectivity to a registered data platform
`ntro_tenant_create`	Create a tenant (client)
`ntro_entity_create`	Create an entity (SPV / fund) within a tenant
`ntro_workflow_create`	Register a workflow definition
`ntro_workflow_deploy`	Deploy a workflow version to Ntropii Tenant
`ntro_workflow_run`	Trigger a workflow run — returns a task ID

Resources

Read-only URIs — the MCP client fetches these by URI to populate context.

URI	Description
`ntro://whoami`	Current user + workspace info
`ntro://integrations`	All data platform configs
`ntro://integrations/{id}`	Single data platform detail
`ntro://integrations/{id}/schemas`	Schema discovery (warehouse layout)
`ntro://tenants`	All tenants
`ntro://tenants/{slug}`	Single tenant detail
`ntro://entities`	All entities across tenants
`ntro://workflows`	All workflow definitions
`ntro://workflows/{id}`	Workflow detail
`ntro://tasks/{id}`	Task status + step progress
`ntro://schedule`	All tasks sorted by urgency

Prompts

Guided multi-step flows. The agent receives a structured plan it works through, asking the human for input at key decision points.

Prompt	Description
`onboard_spv`	Walks through SPV setup: entity → COA → email integration → workflow registration → dry-run test
`run_nav`	Monthly NAV execution with progress monitoring and exception handoffs
`platform_status`	Full platform overview — tenants, entities, workflows, active tasks

Coding agents overview

Why MCP matters for design-time runbook authoring.

Claude Code setup

Wire the MCP server into Claude Code.

Copilot Studio setup

Wire the MCP server into Microsoft Copilot Studio.

Ntro CLI

Same surface, exposed for humans in a terminal.

Get Started

Tooling

Ntro SDK

Deploy & Run

Ntro MCP server

What’s included

Install

Configuration precedence

Three transports

CLI reference

Tools

Resources

Prompts

Coding agents overview

Claude Code setup

Copilot Studio setup

Ntro CLI

Get Started

Tooling

Ntro SDK

Deploy & Run

Documentation Index

​What’s included

​Install

​Configuration precedence

​Three transports

​CLI reference

​Tools

​Resources

​Prompts

​Related

Coding agents overview

Claude Code setup

Copilot Studio setup

Ntro CLI

What’s included

Install

Configuration precedence

Three transports

CLI reference

Tools

Resources

Prompts

Related