Start with your Nakamate account
Create your account, confirm your email, then open your Nakamate home. Keep your Nakamate home open in its first tab while a verified AI client opens the connection flow in a second tab.
Getting started · compatibility evidence
Connect your AI.
Nakamate uses remote Model Context Protocol (MCP) and OAuth. Compatibility belongs to an exact AI app, version and connection path, not to a model family.
Choose your starting point
Both paths meet at your home.
Start from your AI app
Add Nakamate only after your exact client path is marked live-supported. OAuth can ask you to sign in or create an account. OAuth returns the authorization tab to your AI app. When you select “Open my home and return to my AI”, Nakamate can also open Home in a new tab. An existing Home tab continues checking server state and tells you when to refresh; the authorization tab does not control it.
The connection flow
Use two tabs. Trust the state on your home.
Check your exact client row
Continue only when the same client, version, registration mechanism and callback have a live-supported result. A vendor documentation page is not connection proof.
Add the remote MCP address
Use the connector or MCP settings named in the client section. Copy the complete HTTPS address, including
/mcp.Remote MCP address
https://mcp.nakamate.app/mcpAuthorize in the second tab
Review the service name and requested access, sign in with your Nakamate account, then approve or deny it. OAuth returns this authorization tab to your AI app. Select “Open my home and return to my AI” if you also want Nakamate to open Home in a new tab.
Start your profile with one exact prompt
After your home shows Connected, return to the AI app and send:
First prompt
Use Nakamate. Create my profile.Your AI should use only context its app makes available, separate supported details from gaps, ask what you seek and let you correct its reading before anything is published.
Compatibility matrix · 1.0.0-candidate.1
Capability documented. Live path unproved.
A row becomes live-supported only after registration, callback, authorization, token exchange, authenticated initialization and a safe account-resolved tool call pass for that exact path.
| Client path | Capability evidence | Nakamate live proof | Instructions |
|---|---|---|---|
| ChatGPT web | DOCS ONLY | UNPROVED LIVE | Read the documented path |
| Codex local host | DOCS ONLY | UNPROVED LIVE | Read the documented path |
| Claude hosted custom connector | DOCS ONLY | UNPROVED LIVE | Read the documented path |
| Generic reference client | LOCAL PARTIAL | UNPROVED LIVE | Read the documented path |
Client-specific paths
Read the documented route and its limit.
Interface labels were checked against official vendor documentation on 28 August 2026. They can change before Nakamate completes the live verification.
DOCS ONLY · UNPROVED LIVE
ChatGPT web
Open Settings → Security and login, turn on Developer mode, then open ChatGPT Plugins, select the plus button and enter the remote MCP URL.
What this does not prove: OpenAI documents this plugin path. Nakamate has not observed its registration, callback, OAuth exchange, initialization or safe tool call.
DOCS ONLY · UNPROVED LIVE
Codex local host
Codex documents codex mcp add nakamate --url https://mcp.nakamate.app/mcp followed by codex mcp login nakamate for a Streamable HTTP server with OAuth.
What this does not prove: Nakamate has not issued or observed the reviewed client registration and exact callback needed by this path. The local version recorded in the evidence matrix is codex-cli 0.150.0-alpha.8.
DOCS ONLY · UNPROVED LIVE
Claude hosted custom connector
On an individual plan, open Customize → Connectors, select +, choose Add custom connector, enter the remote MCP URL, select Add, then Connect.
What this does not prove: Anthropic documents the hosted callback and custom-credential route. Nakamate has not run the complete hosted OAuth and tool-use journey.
LOCAL PARTIAL · UNPROVED LIVE
Generic reference client
Nakamate tested an in-process reference lane with @modelcontextprotocol/sdk 1.29.0 and protocol 2025-11-25. The official MCP Inspector remains a developer troubleshooting tool, not a supported Nakamate user path.
What this does not prove: The local check injected a signed bearer and proved initialization plus whoami. It did not run registration, browser callback, PKCE or token exchange, and it did not prove the 2026-07-28 protocol lane.
Recover safely
A failed connection does not publish a profile.
Connection testing is not open
The remote endpoint is disabled by the operator until the protected client and OAuth checks pass. Keep your account and return when your exact client row is live-supported. Do not change provider registration settings to work around this state.
The client is unconfigured or unavailable
Check that your app exposes the documented remote MCP path. A model name alone is not enough. Do not paste credentials into the server URL or use an unreviewed proxy.
Authorization denied
No connection is created. Return to the AI app and start a new authorization only if you want to review the request again.
Authorization expired
Return to the AI app and begin a new OAuth authorization. Do not reuse an old callback URL or code.
Callback error
Return to the AI app and restart its connection flow. If the same error returns, stop and contact support with the client name, version and time. Do not send tokens, callback codes or passwords.
Your home still says Not connected
Ask the AI app to use Nakamate so it performs a safe account-resolved call, then refresh your home. Initialization alone is not enough.