# OAuth MCP integration

Connect a local client with PKCE, scoped consent, fixture tools, token rotation and revocation.

## Connect locally

The website hosts the OAuth authorization server and the protected MCP endpoint. No domain or third-party sign-in account is needed for this local flow.

MCP: https://datanavoapi.com/api/mcp

Authorization server metadata: https://datanavoapi.com/.well-known/oauth-authorization-server

Protected resource metadata: https://datanavoapi.com/.well-known/oauth-protected-resource/api/mcp

## Authorize, test, revoke

Open Agent connections, start the built-in inspector or register a public client with exact loopback redirect URIs. Sign in, inspect the client, callback and permissions, then approve or deny. PKCE S256 binds the one-time code to the client. The inspector validates state and issuer before exchanging the code.

[Manage Agent connections](https://datanavoapi.com/account/agent-connections/)

## Permission boundaries

`mcp:read`: find, describe. `mcp:demo`: call, read_more; requires mcp:read.

OAuth tools return the public catalog and fixed fictional samples. They do not expose account records, use customer TEST credit, or call suppliers. Existing stdio and separate Key-based HTTP clients retain their own demo, simulated and live-read modes.

## Credential lifecycle

Access tokens last 10 minutes. Refresh tokens rotate; reuse of a consumed refresh token revokes that family. Revoking an authorization or client immediately prevents subsequent authenticated MCP requests, including requests using an existing session. The browser inspector keeps tokens only in memory; reload requires reconnection.

## Transport and recovery

This endpoint pins the supported 2025-06-18 Streamable HTTP handshake: initialize, initialized, tools/list and tools/call. It returns JSON, has no SSE feed and performs no automatic retries. Reconnect after session expiry; do not put bearer tokens in URLs, prompts or tool arguments.

## Before connecting cloud clients

A cloud client cannot reach this loopback endpoint. Public hosting needs a stable HTTPS domain, a deployed authorization service, registered callback URLs, production storage and rate limits. That deployment and compatibility testing are still pending. Real APIs, payments and outbound email remain disabled.

[MCP overview](https://datanavoapi.com/en/mcp/)

[MCP authorization specification](https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization)
