Skip to main content

MCP Server (Remote)

Connect to the Nava-hosted MCP server. Authentication is handled via standard OAuth. The MCP client opens the Nava UI in the user’s browser, the user logs in and authorizes the connection, and the server provisions credentials for the session.

MCP Client Configuration​

{
  "mcpServers": {
    "nava": {
      "url": "https://internal.navalabs.dev/api/mcp"
    }
  }
}

No env block is needed. The remote server manages authentication via OAuth.

Authentication Flow​

MCP Client                Nava MCP Server              Nava UI (Browser)
  │                            │                            │
  ├── connect ─────────────────►│                            │
  │                            │                            │
  │◄── OAuth challenge ────────┤                            │
  │                            │                            │
  │── open browser ────────────┼───────────────────────────►│
  │   https://testnet.navalabs.dev/oauth/authorize?session=...
  │                            │                            │
  │                            │◄── user logs in & grants ──┤
  │                            │        access              │
  │                            │                            │
  │◄── authenticated ──────────┤                            │
  │    (session ready)         │                            │
  │                            │                            │
  ├── requestVerification ────►│                            │
  │◄── result ─────────────────┤                            │
  1. The MCP client connects to https://internal.navalabs.dev/api/mcp.
  2. The server initiates an OAuth flow, directing the user’s browser to https://testnet.navalabs.dev/oauth/authorize?session=....
  3. The user logs in to the Nava UI and authorizes the connection.
  4. The server receives the authorization grant and provisions credentials for the session.
  5. The agent can now use the same tools described in MCP Server (Local): requestVerification, checkVerificationStatus, requestAndAwaitVerification, and getUserAddress.

This is compatible with any standard MCP client that supports OAuth (Claude Desktop, Cursor, etc.).