Skip to main content

​
Product overview

Navi is Meridian7’s client-facing execution platform for AI-assisted sales workflows. It is designed so operators, AI clients, and engineering teams all work from the same public model. You can access Navi through:
  • the navi CLI
  • the Navi MCP server
  • the Navi REST API

​
What Navi is built around

Navi is built around durable work, not one-off chat messages. That gives you a stable object model to build operational workflows around.

​
Core concepts

​
Agents

Agents are named capabilities such as meeting preparation, briefing generation, or structured analysis. Each agent has a stable identifier that you can discover through the CLI, MCP, or API.

​
Runs

Runs are the core execution object in Navi. A run captures:
  • which agent you invoked
  • the input that was submitted
  • the current status
  • the resulting output or stream of events

​
Briefings

Briefings are opinionated outputs for common workflows such as:
  • daily pipeline review
  • meeting preparation for a specific deal

​
Deals

Deals provide the operating context that powers briefings and agent runs. Publicly available deal endpoints let you list deals and read a deal in detail before you generate downstream analysis.

​
Usage

Usage is tracked at the public boundary so request volume, run volume, and model consumption can be governed consistently across CLI, MCP, and API usage.

​
Choose the right interface

​
CLI

Use the CLI when you want a fast operational interface:
  • list agents
  • inspect deals
  • generate briefings
  • create or stream runs
  • install MCP for Claude Desktop

​
MCP

Use MCP when you want Claude Desktop to call Navi tools directly. This is the best experience for users who want an AI assistant to interact with deals, briefings, and runs in a structured way.

​
API

Use the REST API when you are integrating Navi into another product, script, or automation platform.

​
Who Navi is for

  • operators who want fast access from the terminal
  • AI-native clients that need structured tools
  • integration teams that need a stable public API

​
What is available today

  • Agent discovery
  • Deal listing and deal detail
  • Run creation, listing, inspection, and streaming
  • Morning briefing generation
  • Meeting briefing generation
  • Usage summary inspection

​
A typical first workflow

Here is a common first-day journey:
  1. Authenticate with the CLI.
  2. List deals and identify the one you care about.
  3. Generate a meeting brief for that deal.
  4. Create a run for a specific agent if you need deeper analysis.
  5. Install MCP so Claude Desktop can access the same workflows.
Example: 
navi auth whoami
navi deals list --limit 10
navi briefings meeting 11111111-1111-1111-1111-111111111111 --contact "Elena Vasquez"
navi runs create --agent navi.meeting_prep --message "Prepare me for tomorrow's call" --deal 11111111-1111-1111-1111-111111111111
navi mcp install

​
Integration boundaries

The supported integration model is simple:
  • the API is the source of truth for client integrations
  • the CLI is a thin client over that API
  • the MCP server is also a thin client over that API
Private services, internal orchestration, and internal operator tooling are not part of the client-facing surface.