Skip to main content

​
MCP overview

Navi MCP lets AI clients call Navi through structured tools instead of raw HTTP requests. Today, the primary supported client is Claude Desktop.

​
When to use MCP

Use MCP when you want your AI client to:
  • inspect your connected Navi environment
  • list agents
  • inspect deals
  • create and inspect runs
  • generate briefings
  • check usage

​
How it works

  1. Claude Desktop launches the local Navi MCP server on your machine.
  2. The local MCP server reads the same Navi config as the CLI.
  3. The MCP server calls the public Navi API.
  4. Responses come back as structured tool results inside Claude Desktop.

​
What you can do today

  • inspect identity and environment
  • list available agents
  • list deals and fetch a deal in detail
  • create a run
  • read a run
  • list past runs
  • generate a morning brief
  • generate a meeting brief
  • inspect usage summary

​
Example prompts for Claude Desktop

  • “List the top 10 deals in Navi.”
  • “Generate a meeting brief for deal 11111111-1111-1111-1111-111111111111.”
  • “Create a meeting prep run for the BrightWave opportunity.”
  • “Show me which Navi agents are available in this workspace.”

​
What MCP is not

Navi MCP is not:
  • a direct connection to private internal services
  • a separate authentication system
  • a different product surface from the public API
It is a structured client layer over the same public Navi platform used by the CLI and REST API.