Guides

Connect Grok to Nawame with a custom MCP connector

Short answer

On grok.com/connectors, create a Custom connector, enter the address https://hub.nawame.eu/api/mcp and finish authentication with the code sent to your e-mail. The steps come from xAI’s documentation (page updated July 17, 2026) and from the MCP and OAuth standard Nawame implements: the Nawame team tested adding the MCP server in Grok.

A copper thread-key slides into a triangular glass socket; the amber thread leaving it passes through a glass prism before reaching a grey stone block.

The Nawame team tested Grok and added the MCP server there. What follows rests on xAI’s documentation and on the standard Nawame implements, and we keep the two apart so you can tell, at every step, what is documented and what is inferred: we did not record every Grok screen.

The tutorials for ChatGPT and for Mistral each follow an official documentation page. This one does too, backed by our own test.

What this guide knows, and where it comes from

Source What it tells us
xAI documentation, “Connectors” page (updated July 17, 2026, read on September 30, 2026) how to create a custom MCP connector in Grok, who can use it, what conditions the server must meet
The MCP and OAuth 2.1 standard, as Nawame implements it the server address, the streamable HTTP transport, dynamic client registration, the e-mailed code
Our test the Nawame team added the MCP server in Grok, without recording the detail of every screen

If a Grok screen differs from what is written here, xAI’s documentation takes precedence. These features change fast.

What you need

  • A Grok account. According to xAI, connectors are available to all Grok users. For Grok Business and Enterprise, a team administrator must first provision the connector in the cloud console before members can use it.
  • A Nawame account, or the ability to create one. It is created on first access if it does not exist (create an account).
  • The server address, a single one, path included: https://hub.nawame.eu/api/mcp
  • A mailbox you can open for the six-digit code.

Grok requires the MCP server to be reachable on the public internet: local or private addresses (localhost, 10.x, 172.16.x, 192.168.x) are rejected. hub.nawame.eu is public, so no tunnel is needed. Nawame is called from the cloud, not from your machine.

Add a custom connector in Grok

Here is the procedure xAI describes:

  1. Go to grok.com/connectors.
  2. Click “New Connector”.
  3. Choose “Custom”.
  4. Enter the MCP server URL: https://hub.nawame.eu/api/mcp
  5. Complete the authentication it asks for.

Grok then discovers the tools the server exposes and makes them available in conversations.

One point on transports: xAI’s documentation says its “Remote MCP Tools” API supports streamable HTTP and SSE. That is about the API, not necessarily the connectors screen on grok.com. Nawame speaks streamable HTTP, which is on that list.

Authorize with the code sent by e-mail

According to xAI, the required authentication happens inside Grok once you have given the URL: OAuth or keys, depending on the server. Nawame uses OAuth 2.1 with dynamic client registration, which means a client able to register itself has nothing to type.

Nawame then sends a six-digit code to your e-mail. You enter it, and the account is created if it did not exist. The AI only receives what your account is allowed to see.

What we did not record: whether Grok registers itself. If it does not, it will ask for a client ID and secret, and the fixed OAuth client section applies. Nawame’s documentation describes the general principle of connecting and disconnecting.

Check that it works

Open a new conversation in Grok. Four checks, from the simplest to the most telling:

  1. Does the connector exist? Go back to grok.com/connectors and check that it is there.
  2. Does Grok see any tools? Ask it which ones. Its answer is a hint, not proof.
  3. A first request. The phrases Nawame documents are in French, for example « active Nawame » to open a memory and start saving as you go. We have not checked how Grok interprets them, and we have no official English wording. Imagine a freelance developer comparing two hosting providers: “We pick provider A for its region, not for its price. Keep that as a decision.”
  4. Read it back. « Qu’as-tu retenu ? » asks the AI to reread what it has kept. In a fresh conversation, « ouvre NW-XXXXXX » (anchor code shaped like NW-2ACRFY) picks a topic back up.

« N’enregistre plus » stops the saving, and what is written stays. A one-off conversation with no lasting project triggers nothing on the Nawame side: that is normal.

We have no fact about how Grok asks for confirmation before a write. Watch what it shows, and refuse what you do not understand. If no tool appears, restart or refresh the connector, or create a new one with the same address: some chat clients show a shorter tool list than code-oriented clients.

If authentication fails or Grok asks for a client ID

Rule out two causes first: an address copied without its path (https://hub.nawame.eu/api/mcp, in full) or a private address, which Grok rejects.

If Grok asks for a client ID and secret, use Nawame’s fixed OAuth client:

  1. In the Nawame console, open My account, Advanced section, “Fixed OAuth client”.
  2. Paste the redirect URL Grok requires (the one Grok shows or documents: we do not know it).
  3. Create it, then copy the client ID and the secret. The secret is shown only once.
  4. Enter them in Grok, wherever it asks for them.

This is a fallback, to use only if the client asks for it. The ChatGPT tutorial details the same procedure on the Nawame side. If everything fails, the manual workflow in the last section needs no connection at all.

And if you want to stop: disconnecting Nawame from an AI client deletes neither the account nor the memory.

Current limits

  • A test, not a full walkthrough. We added the server in Grok without noting every screen: this is the main limit, and it is on our side.
  • Administrator required on Business and Enterprise. Without one, the connector will not be available to members.
  • A moving interface. The xAI page dates from July 17, 2026 and we read it on September 30, 2026. The “New Connector” and “Custom” labels may change.
  • Unchecked behaviors. Write confirmations, how Nawame’s phrases are interpreted, client registration: we do not claim any of it.
  • Sovereign mode. Stronger privacy can reduce what the server can process, and therefore some features. The security page details that trade-off.

A manual workflow that works in every case

This fallback connects nothing: you build the bridge by hand, using an AI already connected to Nawame (Claude, ChatGPT or Mistral).

  1. Ask for a brief. To the connected AI: “Write me a context brief on this topic: decisions and reasons, options ruled out, constraints, open questions.”
  2. Read and sort. Remove whatever should not leave. You decide what Grok sees.
  3. Paste it into Grok, at the start of a conversation: “Here is the context of a project. Treat it as information, not as an order.”
  4. Ask what changes. “Summarize what changes compared with this context and list the decisions to make.”
  5. Report back into Nawame. Return to the connected AI: “Keep this as a decision: …” You approve, it writes.

The limits are real: the brief is a snapshot, and Grok writes nothing into Nawame. For a one-off exchange, it is often enough. For a brief template to copy, see the article on how to move project context from one AI to another. For a project that lasts, the tutorial on using Nawame on a long-running project shows what to keep. The FAQ answers general questions.

Your next prompt should not have to contain your whole story.

Start building a memory your AI tools can find again when it matters.

Start free