Skip to main content
The space’s MCP server requires two headers, Authorization and Niadra-Subject-Token. Claude Desktop’s connector screen takes a URL and OAuth credentials, with no field for a custom header, so the connection goes through the mcp-remote bridge, a local MCP server that forwards each request to the remote address with the headers you configure. Use a key of the sandbox space (nia_sk_test_...), never a live one.

What the connection needs

Connect

In claude_desktop_config.json (Settings > Developer > Edit Config):
The header value goes through an environment variable, with no space in the argument: it is the form mcp-remote documents for Claude Desktop, which splits arguments on spaces. Restart Claude Desktop; the tools show up in the conversation’s tools menu.

Limits

  • The token lasts 15 minutes: once it expires, the customer tools answer unauthenticated. Mint another, replace it in env and restart Claude Desktop. The two agent memory tools work without a token, when the space turns them on.
  • mcp-remote is an npm package maintained outside Niadra; it needs Node installed.
  • The customer is always the token’s. The server answers POST only.
  • Every tool call leaves a receipt in the space.

Next steps

MCP with any LLM

the tools, the token and what each one requires.

Claude Code

the direct connection, without a bridge.