Connect a client
Add the connector
In your MCP client’s connector settings, add a remote MCP server with the Nikiwa endpoint:
Start authorization
The client detects that Nikiwa requires authorization and opens Nikiwa’s consent page in your browser.
Sign in
If you are not already signed in to nikiwa.com, you are asked to log in first, then returned to the consent screen.
Approve access
The consent screen names the application requesting access and the account it will act as. Click Allow to grant it, or Deny to cancel.
How it works
Nikiwa acts as the OAuth authorization server. The flow is standard OAuth 2.0 authorization code with PKCE (S256), so it works with any compliant MCP client, and clients that support dynamic registration need no pre-registration.
The relevant endpoints, advertised through standard discovery metadata, are:
| Endpoint | Purpose |
|---|---|
/.well-known/oauth-protected-resource/mcp | Points clients at the authorization server |
/.well-known/oauth-authorization-server | Authorization server metadata (RFC 8414) |
/oauth/register | Dynamic client registration |
/oauth/authorize | Authorization and consent |
/oauth/token | Token exchange |
With OAuth you never paste a token into your client. The browser-based consent handles it. Login and approval happen on
nikiwa.com, and the client only ever receives a short-lived access token.Use your assistant
Once connected, ask naturally and let the assistant call Nikiwa. For example: “Use Nikiwa to check the risk score and top counterparties of0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on Ethereum.”