Skip to main content

​
Navi

Navi gives your team three supported ways to work with Meridian7:
  • the navi CLI for operators and analysts
  • a local MCP server for AI-native clients such as Claude Desktop
  • a versioned REST API for direct integrations
All three surfaces are aligned around the same public model, so you can move between terminal workflows, AI workflows, and application integrations without learning three different products.

Overview

Learn the core concepts, choose the right interface, and understand how Navi fits into your workflow.

CLI

Configure the CLI, authenticate once, and run your first deal, briefing, and run workflows.

MCP

Connect Claude Desktop in one command and start using Navi tools from a chat-based client.

API

Build directly against the public Navi API with stable routes, request envelopes, and examples.

​
Start here

If you are brand new to Navi, use this path:
  1. Read the product overview to understand agents, runs, deals, and briefings.
  2. Complete the CLI quickstart to configure your workspace and verify access.
  3. If you use Claude Desktop, follow the MCP setup guide.
  4. If you are building an integration, move to the API overview.

​
What you can do with Navi today

  • discover the agents available to your organization
  • list deals and inspect deal context
  • generate morning briefings
  • generate meeting briefings for a specific deal
  • create, inspect, and stream agent runs
  • connect Claude Desktop to Navi through MCP
  • inspect high-level usage summary data

​
Choose the right interface

​
Use the CLI when you want to work fast from a terminal

The CLI is best for repeatable operational workflows such as:
  • checking identity and environment
  • listing deals and agents
  • generating briefings
  • creating or streaming runs
  • installing MCP for Claude Desktop

​
Use MCP when you want Navi inside an AI client

The MCP server is best when you want Claude Desktop to call Navi tools directly instead of relying on free-form prompts or raw HTTP requests.

​
Use the API when you are integrating Navi into software

The REST API is the right choice for:
  • custom applications
  • automation scripts
  • external systems that need stable, versioned contracts

​
A 5-minute first run

navi config set-base-url https://dev.meridian7.io
navi auth login --cookie "<your-session-cookie>"
navi auth whoami
navi briefings morning
navi deals list --limit 10
navi mcp install
After that, you can:
  • ask Claude Desktop to use Navi tools through MCP
  • create a run from the CLI
  • call the REST API directly

​
Documentation scope

This site documents the public Navi experience only:
  • product behavior
  • client setup
  • authentication expectations
  • CLI usage
  • MCP setup and tools
  • public API routes, envelopes, and limits
It does not publish internal infrastructure, secrets, or operational runbooks.