Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.ntropii.com/llms.txt

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

Claude Code is Anthropic’s terminal-based coding agent. It speaks MCP natively and can run shell commands, which means it can use both the Ntro MCP server and the ntro CLI — exactly the two surfaces a runbook author needs.

​
Prerequisites

  • Claude Code installed and signed in
  • ntro-mcp installed and reachable on $PATH (or by absolute path)
  • A working ~/.ntro/config.toml (run ntro auth login if you haven’t)
Verify the MCP server runs: 
ntro-mcp --help

​
Add the MCP server

Claude Code reads ~/.claude/mcp.json for global config and <project>/.claude/mcp.json for project-local config. Pick whichever fits — global if you want Ntro available in every Claude Code session, project-local if you want it scoped to one workspace. 
{
  "mcpServers": {
    "ntro": {
      "command": "ntro-mcp",
      "args": ["--transport", "stdio", "--connection", "production"]
    }
  }
}
If ntro-mcp isn’t on $PATH (common with uv editable installs), use the absolute path: 
{
  "mcpServers": {
    "ntro": {
      "command": "/home/you/.ntro-dev/bin/ntro-mcp",
      "args": ["--transport", "stdio", "--connection", "production"]
    }
  }
}
Restart Claude Code (or /mcp reconnect inside it). The Ntro tools should appear in /mcp.

​
Verify it’s working

In Claude Code, ask: 
Run ntro_whoami and show me the result.
You should get back your identity, organisation, and accessible tenants. If you see an authentication error, check that ntro auth whoami works at the terminal — the MCP server uses the same config.

​
Make the CLI usable too

The MCP tools cover write operations. For reading runs, viewing schedules, and running the local test harness, Claude Code is most effective when it can shell out to the ntro CLI: 
ntro --help
ntro workflow test ./runbooks/nav-monthly --scenario happy
If ntro is on $PATH, Claude Code can run it directly. With editable installs from a custom venv, either:
  • Add the venv’s bin/ to $PATH in your shell init, or
  • Tell Claude Code to use the absolute path: /home/you/.ntro-dev/bin/ntro workflow test ...

​
Example: scaffold a runbook

A real session looks roughly like: 
You:    Read ntro://tenants/acme-fund-admin and the schemas at
        ntro://integrations/<id>/schemas. Then scaffold a new runbook
        at runbooks/document-ingest-acme/ that mirrors the structure
        of runbooks/document-ingest/ — but reading invoices from
        Acme's specific schema layout.

Claude: <reads tenant + schemas via MCP>
        <reads existing template at runbooks/document-ingest/>
        <writes the new files>

You:    Now run ntro workflow test ./runbooks/document-ingest-acme
        --scenario happy and fix anything that fails.

Claude: <runs the test, sees a failure, iterates>
That’s the design-time loop. Once the test passes, you review the diff, request changes, and merge.

​
Shipping it

Two ways to deploy from Claude Code: 
ntro workflow push <workflow-id> ./runbooks/document-ingest-acme.zip
ntro workflow deploy --workflow <id> --version <version-id> --tenant acme-fund-admin
The MCP path is shorter; the CLI path gives you visible logs. Pick whichever the situation calls for.

Copilot Studio

Same MCP server, different client.

Skill definitions

The prompts that teach a coding agent how to author Ntropii runbooks.