Nexara Connect docs0.1.0

Hermes

Before you start

Configure

Put the key in ~/.hermes/.env:

NEXARA_KEY=nxc_...

and add the server to ~/.hermes/config.yaml:

mcp_servers:
  nexara:
    url: "https://dev.nexara.ac/mcp"
    headers: { Authorization: "Bearer ${NEXARA_KEY}" }
    tools: { exclude: ["context_write", "context_archive"] }

Write tools are excluded by default so Hermes proposes rather than commits. Tools register as mcp_nexara_context_bundle and so on.

Recipe: daily brief

Give a cron job a script that fetches, and let the model only write:

curl -s https://dev.nexara.ac/api/v1/bundle -H "Authorization: Bearer $NEXARA_KEY" \
  -H 'Content-Type: application/json' -H 'Accept: text/markdown' \
  -d '{"intent":"open commitments, deadlines this week, active clients","scope":"hafez","budget_tokens":6000}'

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/hermes.md by docs/site/build.mjs. Edit the Markdown, then rebuild.