Nexara Connect docs0.1.0

Claude Code

Before you start

Add the server

User scope (all projects):

claude mcp add --transport http --scope user nexara https://dev.nexara.ac/mcp \
  --header "Authorization: Bearer $NEXARA_KEY"

Or per project, in .mcp.json at the repo root. ${NEXARA_KEY} is expanded from your environment, so the key never lands in git:

{
  "mcpServers": {
    "nexara": {
      "type": "http",
      "url": "https://dev.nexara.ac/mcp",
      "headers": { "Authorization": "Bearer ${NEXARA_KEY}" }
    }
  }
}

If you leave the header out, Claude Code runs the OAuth flow instead (loopback redirect, consent in your browser).

Load context at session start (optional)

Add a line to your project's CLAUDE.md:

Before starting, call the nexara `context_bundle` tool with the task as intent. Record decisions with `context_propose`.

Verify

Ask the agent to call context_whoami. It returns the agent name, workspace and grants. Or run:

curl -s https://dev.nexara.ac/mcp \
  -H "Authorization: Bearer $NEXARA_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"context_whoami","arguments":{}}}'

Troubleshooting

SymptomCause
401 invalid, expired or revoked tokenWrong key, key revoked, or a workspace lockdown bumped the token epoch. Mint a new key
401 git tokens (nxg_) are not accepted on /mcpYou pasted a git token. Use an nxc_ agent key
403 forbidden host or originThe server has ALLOWED_HOSTS set and your Host header is not in it
Tool result forbidden: ...The agent's grant does not cover that Space, action or sensitivity. Widen it on the agent page
Tool result step_up_requiredThe change needs a human with step-up; it was turned into a proposal
Generated from connect/claude-code.md by docs/site/build.mjs. Edit the Markdown, then rebuild.