NAVI Protocol MCP User Guide

A public DeFi data and explanation interface for AI clients. No API key required, ready to use out of the box, and suitable for user queries, content research, and technical integrations.

In One Sentence

NAVI Protocol MCP is an open Model Context Protocol service. It packages scattered capabilities across the NAVI Protocol ecosystem-including lending, swapping, bridging, DCA, Volo Vault yield vaults, wallet assets, and Sui transaction interpretation-into a standardized toolset that AI clients can call directly.

Its core value is not just "one more API." It turns information that normally requires jumping between protocol pages, block explorers, and multiple product pages into structured context that AI can understand, combine, and explain. Users can simply ask questions in natural language, and AI can call NAVI Protocol MCP to produce answers closer to real decision-making needs.

Who It Is For

• Everyday users who want to quickly understand the NAVI Protocol ecosystem without manually checking multiple pages
• On-chain users already active in Sui who want AI help interpreting assets, positions, transactions, and risks
• Developers, researchers, or teams that want a public, free, no-auth DeFi MCP service
• Content creators and analysts who want AI to handle data retrieval and result interpretation so they can focus on analysis and decisions

Core Access Information

Item	Details
Endpoint	https://open-api.naviprotocol.io/api/mcp
Authentication	No API key required
Cost	Free
Recommended transport	Streamable HTTP
Capability boundary	Read-only querying and interpretation; does not handle signing, authorization, or transaction execution

Get Started in 3 Minutes

Option A: Add Directly in a Client That Supports Remote MCP

If your client provides entries like Add MCP Server, Remote MCP, or HTTP MCP, you only need the following:

• Server Name: navi-protocol
• URL: https://open-api.naviprotocol.io/api/mcp
• Headers: leave empty

Save and reconnect. Then you can ask questions directly in chat without memorizing specific tool names.

Option B: Example with Cursor

If you use Cursor, add a remote server in your MCP configuration:

{
  "mcpServers": {
    "navi-protocol": {
      "url": "https://open-api.naviprotocol.io/api/mcp"
    }
  }
}

After configuration, refresh the MCP list or restart the client, then ask questions directly in the chat box.

Option C: Example with Claude Code

If you use Claude Code, you can add an HTTP MCP service through the command line:

claude mcp add --transport http navi-protocol https://open-api.naviprotocol.io/api/mcp

Option D: Example with Codex

If you use OpenAI Codex, add the MCP server in global or project-level config.toml (for example, ~/.codex/config.toml or .codex/config.toml):

[mcp_servers.navi-protocol]
url = "https://open-api.naviprotocol.io/api/mcp"

You can also add it quickly via CLI:

codex mcp add navi-protocol --url https://open-api.naviprotocol.io/api/mcp

After setup, use the two prompts below to quickly verify connectivity:

• Please explain in plain language what capabilities NAVI Protocol mainly supports right now.
• Please list NAVI's major lending pools.

How to Ask Better Questions

Regular users do not need to call tools manually. The best way is to tell AI your goal, target object, and preferred output format directly.

Recommended Prompt Styles

• Please introduce NAVI Protocol's current overall status in non-technical language.
• I want to see the key parameters of the SUI lending pool. Please explain them to me.
• If I swap 1 SUI to USDC, roughly how much would I get? Quote only, do not execute any transaction.
• Help me check DEEP's contract address, decimals, and current price.
• Which chains are currently supported by NAVI Astros Bridge? Can USDC on Sui be bridged?
• Help me explain what happened in this Sui transaction: 2aWS5J9i4SxW3DVfKheR9Sdx6iMKPW6vfka56v5tuTSw
• What Volo Vault yield vaults are available right now? Which one has the highest APY?
• This is my Sui address: <YOUR_SUI_ADDRESS>. Please summarize my assets, positions, and risks.

Habits for Higher-Quality Prompts

• Specify output style, such as "explain in plain language" or "summarize in research report format"
• Specify constraints, such as "quote only, do not execute trades" or "Sui mainnet only"
• Specify priorities, such as "focus on risks first," "focus on claimable rewards first," or "focus on bridge reachability first"

Public Capabilities Available Today

The table below summarizes the main capabilities currently exposed by NAVI Protocol MCP and example natural-language prompts users can ask directly.

Use Case	Representative Tools	Recommended Prompt
Protocol overview	navi_get_protocol_stats	What is the current overall scale of NAVI Protocol?
Lending pool analysis	navi_get_pools, navi_get_pool	What are the supply/borrow rates, LTV, and risk parameters for the SUI pool?
Risk checks	navi_get_health_factor, navi_get_price_feeds	Is this address's health factor safe?
Reward information	navi_get_lending_rewards, navi_get_available_rewards	What lending rewards are still unclaimed for this address?
Wallet and positions	navi_get_coins, get_positions	Please summarize this address's current assets and DeFi positions.
Market configuration	navi_get_market_config	Which assets are currently supported in NAVI Main Market?
Token information	navi_search_tokens	Help me check DEEP's contract address, decimals, and current price.
Swap quotes	navi_get_swap_quote	If I swap 1 SUI to USDC, about how much can I get?
Bridge discovery	navi_get_bridge_chains, navi_search_bridge_tokens, navi_get_bridge_quote	Which chains support bridging? Can this token bridge cross-chain?
Bridge tracking	navi_get_bridge_tx_status, navi_get_bridge_history	Help me check what stage this bridge transaction is currently in.
DCA queries	navi_get_dca_orders, navi_get_dca_order_details, navi_list_dca_orders	Please list DCA orders for this address.
Volo Vault overview	volo_get_vaults, volo_get_vault, volo_get_vault_system_summary	What Volo Vault yield vaults are available? What is the overall TVL and revenue?
Volo Vault analytics	volo_get_vault_apy_history, volo_get_vault_share_price_history, volo_get_vault_tvl_history, volo_get_vault_total_tvl_history	How has this Volo Vault's APY trended over the past month?
Volo Vault user positions	volo_get_vault_user_positions, volo_get_vault_user_status, volo_get_vault_user_transactions	How much has this address staked in Volo Vault? What are the earnings?
Transaction explanation	sui_get_transaction, sui_explain_transaction	Please translate this transaction into plain human-readable language.

Recommended Template for Address-Based Questions

If you are willing to provide your Sui address, AI can further summarize your assets, positions, risks, and rewards. Here is a template you can copy and use directly:

This is my Sui address: <YOUR_SUI_ADDRESS>.
Please help me with the following 5 things:
1. Summarize what assets I currently hold;
2. Summarize my positions in NAVI and other protocols;
3. If my health factor has risk, warn me directly;
4. Tell me whether I have any unclaimed rewards;
5. Summarize my Volo Vault positions and earnings.

These requests usually combine the following capabilities:

• navi_get_coins
• get_positions
• navi_get_health_factor
• navi_get_available_rewards
• volo_get_vault_user_positions
• volo_get_vault_user_status

If address-based queries occasionally hit upstream rate limits or timeouts, retrying later usually works.

Direct Testing for Technical Users

If you want to verify service availability in a terminal first, you can send MCP requests directly. The initialization example below uses protocol version 2025-06-18, which has been verified in this guide. If your client automatically negotiates protocol versions, manual specification is not required.

1. Initialize

curl https://open-api.naviprotocol.io/api/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data-binary '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-06-18",
      "capabilities": {},
      "clientInfo": {
        "name": "demo-client",
        "version": "1.0.0"
      }
    }
  }'

2. List Tools

curl https://open-api.naviprotocol.io/api/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data-binary '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/list",
    "params": {}
  }'

3. Call a Tool Directly

curl https://open-api.naviprotocol.io/api/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data-binary '{
    "jsonrpc": "2.0",
    "id": 3,
    "method": "tools/call",
    "params": {
      "name": "navi_get_protocol_stats",
      "arguments": {}
    }
  }'

Usage Tips

• If this is your first time with DeFi, ask AI to explain results in plain language instead of outputting raw JSON directly.
• If you want to evaluate whether an asset or pool is worth deeper research, use this path first: protocol overview -> pool parameters -> quote -> risk.
• If you are unsure about a token's contract address or decimals, search by symbol directly, for example: Help me check DEEP token info.
• If you plan to provide your own address, ask AI to summarize assets, positions, and risks together for a fuller and more efficient result.
• If you only want to test connectivity first, start with a prompt that does not depend on wallet addresses, such as protocol overview, SUI pool parameters, or explanation of a public transaction.

Common Boundaries and Notes

• NAVI Protocol MCP currently serves as a read-only query and interpretation layer. It does not handle signing, authorization, or direct trade execution.
• Whether an AI client supports Remote MCP, Streamable HTTP, or automatic protocol negotiation depends on the client's own implementation.
• Address-based queries, bridge history, or some aggregated capabilities may be affected by upstream service status, rate limits, and timeouts.
• If you need interpretation rather than raw data, explicitly ask AI to summarize, compare, or highlight risks in your prompt.

Why This Matters for User Experience

The value of NAVI Protocol MCP is that it unifies multiple on-chain capabilities into a single access layer AI can call directly, significantly reducing user cognitive load.

A traditional usage flow is often:

• Check a number on a protocol page
• Track a transaction in a block explorer
• Open other pages to check swap routes or bridge support
• Manually piece together context and make a judgment

With NAVI Protocol MCP, AI can first fetch structured data, then combine it with your question to produce answers closer to real decision scenarios. For users, what truly matters is not the fields themselves, but "how should I interpret this data right now?" This is exactly where MCP delivers the most value at the product-experience level.