MCP capabilities
Navi MCP exposes a focused set of tools that mirror the public Navi API.Current tool list
navi_whoaminavi_list_agentsnavi_list_dealsnavi_get_dealnavi_list_runsnavi_get_runnavi_create_runnavi_create_morning_briefnavi_create_meeting_briefnavi_get_usage_summary
What each tool is for
navi_whoami
Returns the connected environment, organization, principal type, and available scopes.
navi_list_agents
Lists the agents available in the current organization.
navi_list_deals
Lists deals with pagination options.
navi_get_deal
Fetches a single deal in detail.
navi_list_runs
Lists prior runs for the current organization.
navi_get_run
Fetches one run by ID.
navi_create_run
Starts a new run by providing:
agentIdmessage- optional
dealId
navi_create_morning_brief
Generates the current organization-level morning brief.
navi_create_meeting_brief
Generates a meeting brief for a specific deal with an optional contact name.
navi_get_usage_summary
Returns request, run, and token usage summary data for the current billing period.
Example MCP workflow
In Claude Desktop, you can ask:- “Show me the top deals in Navi.”
- “Open the Revenue Analytics Platform deal.”
- “Generate a meeting brief for that deal.”
- “Create a meeting prep run with focus on executive objections.”
Tool design rules
- MCP mirrors the public API rather than bypassing it
- tools use structured inputs and typed responses
- authentication, rate limits, and metering stay anchored to the public API
- internal-only services are not exposed as public MCP tools

